> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/whatsapp4dynamics/features/dynamic-field-mapping.md).

# Dynamic Field Mapping

WhatsApp4Dynamics makes it easy to turn real-time conversations into actionable CRM records. With **Dynamic Field Mapping**, you can auto-populate fields when creating records, whether for standard entities like *Contacts* and *Cases*, or custom ones like *Orders*. This streamlines data entry, reduces errors, and ensures consistency across your CRM.

Imagine you’re chatting with a customer on WhatsApp. With just a few clicks, you can create a new *Order* record directly from the chat, automatically filled in with data from their *Contact* record (like name, email, and phone number).

**Here’s how it works:**

* First, configure field mappings inside Dynamics 365.
* Go to **Advanced Settings.**

<figure><img src="/files/0OVC4WG7IRWlupdSMjNU" alt=""><figcaption></figcaption></figure>

* Click on **Customizations > Customize the System.**

<figure><img src="/files/3g4chizuesH8HtQrQTUo" alt=""><figcaption></figcaption></figure>

* In the left panel, expand **Entities**.

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

* Under the Contact entity, click on **1:N Relationships**.

<figure><img src="/files/3wCr0qynF5byubFS6Zq3" alt=""><figcaption></figcaption></figure>

* Look for the relationship where the **Related Entity** is **Order**.

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

* Click on the **Contact-to-Order** relationship to open it.

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

* Within the relationship editor, look for the Mappings section.

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

* Click New to create a mapping.

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

* Click Mappings to open the field mapping editor. Select the field for mappings and click OK.

<figure><img src="/files/54gfjkCJ5IYqzFhHb6LD" alt=""><figcaption></figcaption></figure>

* For example:

Map Contact Name → Customer Name

Map Email → Email Address

Repeat for each field you want to map between both the entities.

After mapping the fields, click Save and Close in the mapping window.<br>

* Now, when you’re chatting in WhatsApp and click **Create Record**, select **Order** from the dropdown.

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

* The Order form opens with mapped fields already filled in from the Contact.

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

* Just review, complete any remaining details, and hit **Save and Close**.

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

The newly created record will:

* Be linked to the current WhatsApp conversation via the *Regarding* field
* Include all mapped customer data, saving you time and ensuring accuracy

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.inogic.com/whatsapp4dynamics/features/dynamic-field-mapping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
