# Create Entity

A form for creating a new entity record without leaving the portal. The whole form is configured through one modal — pick which fields appear, mark which are required, set widths, decide between inline and modal presentation, and define what happens on save.

## Available in

* Page modules
* Order Form modules
* Catalog modules

## When to use

* Order Form pages where the cashier may need to create a customer on the fly (rare new-walk-in scenario in retail).
* Customer service pages where agents create customers as part of handling a new account.
* B2B portals where a sales rep onboards a new business contact.
* Anywhere "create new" sits naturally next to "search existing".

## Settings

| Setting           | Description                                                                                                                        |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Configuration** | Opens the configuration modal — the only setting on the block surface. All field, layout, and behaviour options live in the modal. |

The configuration modal supports:

* **Display mode** — Inline (form embedded on the page) or Modal (button opens a pop-up form).
* **Main fields** — toggle each main entity field (visibility, required).
* **Address fields** — toggle each address field on the form.
* **Custom fields** — add custom NetSuite fields with order, width, and field type.
* **Contact create / edit** — allow contact records to be added during entity creation.
* **Per-field controls** — required, hidden, width, label override.

## How it works

1. Form renders according to the configured fields and visibility.
2. The user fills in required fields.
3. On save, a NetSuite entity record is created via the SuiteCloud RPC.
4. The new entity is published to session state — downstream blocks can read it immediately.
5. Optional contact creation runs alongside, attaching contacts to the new entity.

In edit mode the block shows a placeholder summary indicating how many fields are configured.

{% hint style="info" %}
Use **Modal** display mode for Order Form contexts where Create Entity isn't the primary action — it stays out of the way until needed. Use **Inline** for dedicated "create new customer" workflows where the form is the page.
{% endhint %}

## Examples

**On-the-fly customer creation in POS.** Entity Search at top, Customer/Vendor Selection below it, Create Entity in Modal mode triggered by an Action Button labelled *New Customer*.

**Dedicated onboarding workflow.** Page module dedicated to new-customer onboarding. Create Entity in Inline mode with all main + address + a few custom fields enabled.

**B2B partner onboarding.** Create Entity configured for Partner entity type, with custom fields for partner program code and tier.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Entity Search</strong></td><td>Pair with Entity Search so users find existing entities before creating new ones.</td><td><a href="/pages/YG0JVvulp0T0QNjVYaQI">/pages/YG0JVvulp0T0QNjVYaQI</a></td></tr><tr><td><strong>Customer/Vendor Selection</strong></td><td>The Order Form picker — pair with Create Entity for create-then-use flows.</td><td><a href="/pages/km19hjFIFOFjRK0yQAJp">/pages/km19hjFIFOFjRK0yQAJp</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/entity-components/create-entity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
