> 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-retrieval-api-against-fis-codeconnect/3.-field-mapping-setup.md).
# 3. Field Mapping Setup
**Setting up the Field Mapping Table**\
\
Right click on the service you just created and Go To -> Field Mapping. This page should be blank.\
\
From here, you'll want to add 3 different rows. The number of field mapping rows that are required for a specific service vary, but for this example we will need 3 distinct rows.\
\
Number each Sequence column for each row from 1 to 3. Under the "Field" column for each row, enter the following into each one:\
\
\- `_application_id`\
\- `_path`\
\- `_method`\
\
The "Value" column of each of these rows also needs to be filled in. For each of the Field columns, use the following matrix to determine what should go inside the value column:
| Field | Value |
| ----------------- | ----------------------------- |
| `_application_id` | "CI" |
| `_path` | f"customers/{customerNumber}" |
| `_method` | "GET" |
\
Ensure that the "Value Type" column for each of these rows is set to `str` which stands for the data type "String".\
\
Save the changes that you've added.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://glyue.docs.sandboxbanking.com/tutorials/building-a-retrieval-api-against-fis-codeconnect/3.-field-mapping-setup.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
