# Entity Settings

The prerequisite of any integration is to map the data between the two systems. GUMU™ reads the table schema using the Acumatica Web Service API method and validates mapping details like field name, field label, and data type that you can see under the mapping tab of the Import routine.

Let’s take a look at how entity setting works:

1. Navigate to the “**GUMU Settings**” app from the app launcher to view the “**Entity Setting**” tab, to create a new entity, click on the “**New Entity**” button at the right-end corner as shown in the below image.

<figure><img src="/files/bER0EmgO2cCoXuNSKRPG" alt=""><figcaption></figcaption></figure>

2. Let’s take an example of an already existing (Standard) entity, “Acumatica-Customer”, click on the eye icon to view the entire entity details.

<figure><img src="/files/6WzYZgqcsL7gWkJWZQoA" alt=""><figcaption></figcaption></figure>

3. The Header section has an Entity Name which is used for the GUMU Integration Entity import routine and a corresponding API method present in the Acumatica tables.

<figure><img src="/files/7WXD9uW35JgHjGO4Kcue" alt=""><figcaption></figcaption></figure>

**Field Wise Description:**

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Fields</strong>   </td><td valign="top"><strong>Description</strong>   </td></tr><tr><td valign="top">Entity Name </td><td valign="top">Specify the Entity name as per the requirement. </td></tr><tr><td valign="top">API Method</td><td valign="top">The API method is used to define the table name of SAGE of that particular entity. </td></tr><tr><td valign="top">Group Name   </td><td valign="top">When you require any group specific data then you need to specify it.   </td></tr><tr><td valign="top">Parent Entity   </td><td valign="top">Specify the entity which is parent defined in Web Service.   </td></tr><tr><td valign="top">Master Entity Field for Filter   </td><td valign="top">Specify the master entity field on which parent entity will get filtered. </td></tr></tbody></table>

4. Navigate to the Details section, this section displays fields available in the Acumatica Web-service tables for performing actions in Salesforce.

<figure><img src="/files/D7huTcyXpZ0MJVAe0qMF" alt=""><figcaption></figcaption></figure>

5. Proceed to the "Details" tab, click on “**Edit**” button then click the "**Refresh Fields**" button to retrieve precise fields from the Sage system for executing actions (update) within Salesforce. Lastly, click the "Save" button to preserve the schema information for utilization in the GUMU™ mapping functionality.

<figure><img src="/files/VaN2sVNxfpqy1qvxNrdM" alt=""><figcaption></figcaption></figure>

6. You can also define a primary key for Entity by selecting fields. If you want to assign a composite key (combination of more than one field as the primary key) to the entity, you can add multiple rows under the Primary Key tab.

<figure><img src="/files/52HbRk4N1Anut3P8yzGV" alt=""><figcaption></figcaption></figure>

7. If you happen to add a primary key by mistake, you can simply check the field and hit “Delete Primary Key” button.

<figure><img src="/files/qUQS9C9iUK5Of3pis8k5" alt=""><figcaption></figcaption></figure>

8. Once configuration is done click on the “Save” button to save the entity. And here you have your entity created and ready for integration. This entity can now be used in the Import routine for bringing the records into Salesforce from Acumatica.


---

# 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.greytrix.com/gumu-salesforce-integration/acumatica/gumu-tm-settings/entity-settings.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.
