Save the records whose field values have been updated by other actions to the original Kintone app. At that time, save to Kintone for each record.
In Customine Job Runner, if you perform an Action on a field value in a record, such as Set Field Value, the field values are not immediately saved in Kintone, but are saved together after saving the changes.
This save action is usually automatic, but Save Updated Records One by One allows you to do this with an action.
A similar Do is Save Updated Records, Save Updated Records saves all records with changed values together, while Save Updated Records One by One saves them one at a time in sequence. Note that when saving automatically, it will be saved together.
Save Updated Records One by One has the advantage of saving one record at a time, so that if the target app has a webhook configured for editing record, that webhook will be notified. Save Updated Records or autosave does not trigger a webhook notification. On the other hand, having a large number of targeted records to store has the disadvantage of taking longer to process. Save Updated Records or autosave is recommended if webhooks are not required.
Specify API Token.
Specify the API Token for accessing the Kintone app to save the changed fields. Choose from the actions to Set Kintone API Token.
If you are making field value changes for multiple apps in your customization, you must specify the API Token for all of those apps. If you change the value but do not specify an API Token for the app, Kintone returns an error at runtime.
| Criteria | Occurrence |
|---|---|
| When Record Is Ready It doesn’t happen. | |
| When All Records Are Ready It doesn’t happen. |
If the destination app is configured to provide webhook notification with the edit record criteria, this notification occurs when you run the this Do.