Update the data in an existing record of the specified app by providing the key to search for the record with the value.
Search the specified app using the field value of the specified record as key and updates the record found according to the mapping.
Place the action Kintone connection settings before the action Update or Add Record Providing the Another Record Field.
Gets the record for the mapping. For example, you can use Get Records by Providing Query. Designate these records as the source records.
When you perform Update or Add Record Providing the Another Record Fields, it looks for a record in the app that matches key value field on record of the record with the field key field on target app, and if found, update the contents of that record based on mapping. If not found, add records based on mappings.
The result of the action is a set of records that you updated or added. However, the information in the additional record can only refer to fields set in the mapping.
You can do more field value changes by passing the Update or Add Record Providing the Another Record Field as the record parameter to a type of Do that changes the field value, such as Set Field Value. However, it is not efficient because it will be saved to Kintone twice. It is recommended that you complete only the Update or Add Record Providing the Another Record Field.
Set Target app, API Token, Kye field, Record, Key Value Field on record, and Mapping.
Select the app with the record you want to update.
Specify the API Token to access the destination app. Choose from the Set Kintone API Token action.
The API Token must have view and ddit record privileges.
Select the key field from the target app.
This parameter does not accept fields that are inside tables.
This parameter accepts the following field types:
Select the Action you used to retrieve the target records.
There are no specific restrictions on the record app. It can be the same as the app you are customizing or the app you are destination app to, or vice versa.
This record can contain multiple lines. If multiple rows are included, the process repeats the process of finding and updating the record matching the key for each row sequentially. Conversely, if the record count is zero, no action is taken.
Specify the record field that you want to compare to the updated record as a key.
The records in the destination app whose values in the key field to be updated match the values in the field in the source record that will become the key will be the target of the update process.
If you select a field in the table, processing is performed on each row in the table.
This parameter accepts the following field types:
Enter the information you want to register in the record.
See Field Mapping Description for detailed descriptions of this parameter.
If you specify a field code in the expression for this mapping, the field becomes the field of the record.
You can use @out for this Mapping. If there is a record matching the Key, @out refers to that record. If no record matches the Key, @out is empty.
| Criteria | Occurrence |
|---|---|
| When Record Is Ready It doesn’t happen. | |
| When All Records Are Ready It doesn’t happen. |
If a record exists that matches the key, an attempt is made to save over the record, but an update conflict is checked.
Similar to this Do Update Records from Other Records, allows you to choose whether to Check Conflicts in the settings, but this Update or Add Record Providing the Another Record Field does not prevent you from checking for conflicts.
On the other hand, if no record matches the Key, i.e. a when a new record is created, the conflict is not checked.
So, if two people execute an action at the same time, you could end up with two new records with the same content. If you want to avoid this, it is highly recommended to set Prevent Duplicate Values on the key fields in the Kintone app settings.
If the destination app is configured to provide a webhook notification with the Add record criteria, this notification occurs when the record is added as a result of running this Do.
If the Do result is an update of an existing record, webhook notification will not fire.
Starting with version 1.130 (released April 22, 2021), the behavior is changed when a new record is created without a record matching the Key.
For jobs generated using version 1.129 (released April 15, 2021) or earlier, if a new record is created with no record matching the Key, the record addition will not be reflected in Kintone when the action is completed. It will accumulate to some extent and then be reflected later.
Version 1.130 (released April 22, 2021) and later will reflect the record addition in the Kintone app when the action is complete.