# Registration of input results

<div align="left"><figure><img src="/files/ejBZZeDrq5sOKCU38C1E" alt=""><figcaption></figcaption></figure></div>

The image used in the following description is an image of PostgreSQL linkage. \
Other database linkage has the same screen configuration.

## Function overview

* **Registration of input results** links i-Reporter to database.&#x20;

<table><thead><tr><th width="267.3333333333333">Cooperation direction</th><th width="243">Function description</th><th>Execution timing</th></tr></thead><tbody><tr><td>i-Reporter→Database linkage</td><td>Register the report data entered in i-Reporter as a new record in the database.</td><td>Webhook notification of i-Reporter</td></tr></tbody></table>

## Steps for mapping settings

Follow the steps below to set the mapping.

### 1. Selecting a connection pattern with database

* Click the **Registration of input results** menu to add a new mapping.

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

### 2. Mapping code/name setting

* Set the **mapping code** and **mapping name**.
* A mapping code is the **key that uniquely identifies all mapping configurations within the i-Repo Link environment**.

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

### 3. Select the forms as the source of linkage

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

### 4. Select the data sources and tables/views to link&#x20;

* Select the database **data source** and **table** as linkage destination.
* **To select a table**, click **the icon in the title part of the field column in the grid**.
* You can specify up to 8 tables for PostgreSQL and up to 3 tables for Oracle, but you cannot specify different tables for a database.\
  **All specified tables are processed in one transaction.**

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

* Refer to the following page to add and configure data sources.

{% content-ref url="/pages/Mr8iIh9WBLvgsGDHpX6I" %}
[Data source management](/i-repo-link-manual/english/system/2/1.md)
{% endcontent-ref %}

### 5. Map clusters of i-Reporter form and database fields

* The form information of i-Reporter is displayed on the left side of the screen, and the database information is displayed on the right side of the screen.
* If the fields in the database are light gray are fields not subject to linkage.&#x20;
* If it cannot be mapped, an error message is displayed.
* You can mapping with cluster, table, and remark of i-Reporter forms. \
  On the left side of the screen, switch between clusters, tables, and remarks.

<figure><img src="/files/1yL5Rhepd6z2LEbhP3tf" alt=""><figcaption></figcaption></figure>

Linkage destination database information grid item description

<table><thead><tr><th width="284">Item</th><th>Description</th></tr></thead><tbody><tr><td>Mapping</td><td>Displays mapped a cluster of i-Reporter form.</td></tr><tr><td>Field</td><td>Display the fields in the database of the linkage destination.</td></tr><tr><td>Fixed value</td><td><p>Use when you have mapped a fixed value that can be selected in the i-Reporter form information remarks.</p><p>Enter the fixed value you want to set.</p></td></tr><tr><td>Required field</td><td>Use when you have mapped a table of i-Reporter form information.<br>Determine the required field as a valid integration target record.</td></tr><tr><td>Field type</td><td>Explicitly specify the type of field to linkage destination.<br>Converts the format to the specified type.<br><br>* Currently, you can specify the date type.<br>If the value can be recognized as a date, convert it to YYYYMMDD format. (set to 0 if it cannot be converted.)</td></tr></tbody></table>

* See the following pages for combinations of fields and clusters that you can map.

{% content-ref url="/pages/Y7Ft3ZPcBcLr747MD2oo" %}
[PostgreSQL and i-Reporter linkage item mapping table](/i-repo-link-manual/english/data-source-linkage-all-databases-common/common/postgresql-and-i-reporter-linkage-item-mapping-table.md)
{% endcontent-ref %}

{% content-ref url="/pages/R6QkYEWr5ZY8AS7lg1yN" %}
[Oracle and i-Reporter linkage item mapping table](/i-repo-link-manual/english/data-source-linkage-all-databases-common/common/oracle-and-i-reporter-linkage-item-mapping-table.md)
{% endcontent-ref %}

### 6. Setting Webhook URL

#### Webhook URL for i-Reporter setting

* Set the Webhook URL for i-Reporter setting in the i-Reporter Webhook notification.&#x20;
* The URL used for the Webhook notification from i-Reporter to i-Repo Link is displayed. \
  Add records to the database via i-Repo Link.
* You can use edit save notification, completion notification, change notification, etc. in i-Reporter Webhook notification Settings. \
  Configure the Webhook notification to be used for the target form.&#x20;
* Please refer to the following page for i-Reporter Webhook notification Settings.

{% content-ref url="/pages/yr3Dpb5eC5N0GTxKzFq5" %}
[i-Reporter Webhook Notice Settings](/i-repo-link-manual/english/kintone/1/3.md)
{% endcontent-ref %}


---

# 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://cimtops.gitbook.io/i-repo-link-manual/english/menu/registration-of-input-results.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.