> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/tutorials/building-a-multi-system-integration/2.-field-mapping.md).

# 2. Field Mapping

Consulting the [documentation for the mock core](https://glyue.docs.sandboxbanking.com/~/changes/sRNNcOmmdTZIw2Ha7IFP/miscellaneous/sandbox-mock-core/dna-style-fields), we see there are 5 fields of interest to us:

* `Name.FirstName`
* `Name.LastName`
* `EmailAddresses.EmailAddress[0].ElectronicAddressLines.ElectronicAddressLine[0].AddrLine`
* `Identification.DateOfBirth`
* `PersTyps.PersTyp[0].PersonTypeCode`

Additionally, we'll need to add the `url_path` of the endpoint that we're calling on the Mock Core.

Right-click on the `create_new_customer` Service Request and select *Go To > Field Mapping*. Click *+ Add Row 6* times to create 6 empty field mappings.

<figure><img src="/files/MUv8Vd9F7lip5Xt1mcYP" alt=""><figcaption><p>Five empty Field Mappings</p></figcaption></figure>

Each of the fields required by the core can be populated using data we received from randomuser.me, so we simply need to set up the mapping between the fields across the two systems.

First, we'll populate all the fields that the core expects. In the `field` column, copy in the following JSON paths:

| Field                                                                                     |
| ----------------------------------------------------------------------------------------- |
| `Name.FirstName`                                                                          |
| `Name.LastName`                                                                           |
| `EmailAddresses.EmailAddress[0].ElectronicAddressLines.ElectronicAddressLine[0].AddrLine` |
| `Identification.DateOfBirth`                                                              |
| `PersTyps.PersTyp[0].PersonTypeCode`                                                      |
| `url_path`                                                                                |

Now for each field that the core expects, we'll enter the JSON path to the value as it exists in the response from randomuser.me:

| Field                                                                                     | Value                                                  |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| `Name.FirstName`                                                                          | `request_users.response.payload.results[0].name.first` |
| `Name.LastName`                                                                           | `request_users.response.payload.results[0].name.last`  |
| `EmailAddresses.EmailAddress[0].ElectronicAddressLines.ElectronicAddressLine[0].AddrLine` | `request_users.response.payload.results[0].email`      |
| `Identification.DateOfBirth`                                                              | `request_users.response.payload.results[0].dob.date`   |
| `PersTyps.PersTyp[0].PersonTypeCode`                                                      | `"individual"`                                         |
| `url_path`                                                                                | `"/api/integration/fiservdna/person_maintenance"`      |

Notice that while the first four items are JSON Paths into the object returned by `randomuser.me`, the last item is a static value, as it will always be the same for all users created by this integration.

Finally, fill out `str` for the Value Type column for all rows.

<figure><img src="/files/ycnI2Tvt1ifC6QLWz26F" alt=""><figcaption><p>Five field mappings for the Service Request</p></figcaption></figure>

We have now transformed the data received from `randomuser.me` into the format that the mock banking core expects.

Save your changes.


---

# 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://glyue.docs.sandboxbanking.com/tutorials/building-a-multi-system-integration/2.-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.