The next Kintone update is 6th December 2019. The release also includes the following updates.

A number of spec changes will be introduced, due to a Kintone Product feature update related to being able to select Multi-choice and Check box fields in the Lookup field's Field Mapping settings.

With the addition of being able to select Multi-choice and Check box fields in the Lookup field Field Mapping settings, the following specs will be changed:

• When using the following APIs to automatically run or clear a Lookup field, the values of any Multi-choice field or Check box field specified in the Field Mapping settings will be automatically retrieved or cleared.
  • Relevant APIs:
    • Events that can Run Lookup fields
    • Events that can Clear copied Lookup field values
    • Set Record Value (kintone.app.record.set() and kintone.mobile.app.record.set())
  • Details:
    • When a Lookup field is automatically run or fields mapped by a Lookup field are cleared using the above APIs, any values in Multi-choice and/or Check box fields set in the Field Mapping settings of the Lookup field will be also retrieved or cleared.

• A bug exists where when using the following field change events on desktop under the following conditions, the browser console shows an error and the program fails. This bug will be fixed.
  • Relevant APIs:
    • Record Create Field Change event (app.record.create.change.(fieldcode))
    • Record Edit Field Change event (app.record.edit.change.(fieldcode))
  • Details:
    • When using Kintone on the desktop and the field change event is fired in an App with all of the following conditions:
      1. The Field Change event is set to a field that is also set as a field mapped from a Lookup field.
      2. Table rows are deleted (or the field values in the Table row are all cleared) when the event is triggered.
    • Before the fix:
      • An error message is displayed in the browser console and any fields mapped in the Lookup field settings that exist below the Table with rows being deleted, do not have their values copied and inputted.
    • After the fix:
      • No errors occur and values are copied and inputted as expected.
• A bug exists where when a record is created by an action button on mobile, the Show or Hide a Field API and Open Field Group API do not run. This bug will be fixed.
  • Relevant APIs:
    • Record Create Field Change event (mobile.app.record.create.change.(fieldcode))
    • Show or Hide a Field API (kintone.mobile.app.record.setFieldShown())
    • Open Field Group API (kintone.mobile.app.record.setGroupFieldOpen())
  • Details:
    • When a record is created with an action button on mobile, and the Record Create Field Change event is triggered in the destination App's record create screen:
      • Before the fix:
        • Neither the Show or Hide a Field API or the Open Field Group API are run
      • After the fix:
        • Both the Show or Hide a Field API and the Open Field Group API are run

With the addition of being able to select Multi-choice and Check box fields in the Lookup field Field Mapping settings, the following specs will be changed:

• When adding or updating a Lookup field value, it will be possible to automatically retrieve or clear values of Multi-choice fields and Check box fields set in the Field Mapping settings of the Lookup field.
  • Relevant APIs:
    • Add Record(s) (/k/v1/record.json and /k/v1/records.json)
    • Update Record(s) (/k/v1/record.json and /k/v1/records.json)
  • Details:
    • When adding or updating a Lookup field value with the above APIs, the values of any Multi-choice fields and/or Check box fields set in the Field Mapping settings of the Lookup field will be automatically retrieved or cleared.
• The field settings of any Multi-choice fields and/or Check box fields included in the Field Mapping settings of a Lookup field will be included in the Lookup field properties of the following form settings APIs.
  • Relevant APIs:
    • Get Form Fields API (/k/v1/app/form/fields.json and/k/v1/preview/app/form/fields.json)
    • Add Form Fields API (/k/v1/preview/app/form/fields.json)
    • Update Form Fields API (/k/v1/preview/app/form/fields.json)
  • Details:
    • Using the Get Form Fields API , it will be possible to retrieve the field settings of any Multi-choice and/or Check box fields from the applicable Lookup field's Field Mapping settings array*.
    • Using the Add Form Fields API or the Update Form Fields API , it will be possible to retrieve the field settings of any Multi-choice and/or Check box fields from the applicable Lookup field's Field Mapping settings array*.
      *properties.<field code>.lookup.fieldMappings
• The in operator will be available to use when filtering records by Text and Link field values.
  • Relevant APIs:
    • Add Cursor (/k/v1/records/cursor.json)
    • Update Record Permissions (/k/v1/record/acl.json and /k/v1/preview/record/acl.json)
    • Add Form Fields (/k/v1/preview/app/form/fields.json)
    • Update Form Fields (/k/v1/preview/app/form/fields.json)
    • Update Views (/k/v1/preview/app/views.json)
    • Update Process Management Settings (/k/v1/preview/app/status.json)
  • Details:
    • The in operator will be available to use when filtering records by Text and Link field values. Note that this feature is not available for Text and Link fields inside of Tables and Related records.
• It will be possible to get, add, or update records in multiple Apps by setting multiple API tokens in the request header.
  • Relevant APIs:
    • Get Record(s) (/k/v1/record.json and /k/v1/records.json)
    • Add Record(s) (/k/v1/record.json and /k/v1/records.json)
    • Update Record(s) (/k/v1/record.json and /k/v1/records.json)
  • Details:
    • It will be possible to get, add, or update records in multiple Apps by setting multiple API tokens in the request header. For example, Lookup field values can be retrieved, added, and updated, and the records that are filtered for in a Related Records field can be retrieved with API token authentication.

• A bug exists where when the following APIs are used to update a record containing a table, even if fields inside of the table are not updated, the update history shows information related to the table. This bug will be fixed.
  • Related APIs:
    • Update Record (/k/v1/record.json)
    • Update Records (/k/v1/records.json)
  • Details:
    • When all of the following conditions are present:
      1. A record that contains a table is being updated, but the fields within the Table are not being updated.
      2. The row ids of the table are not specified in the object containing the record information in the request parameter.
    • Before the fix:
      • Information related to the Table (specifically, that all the rows in the table were deleted and then added) is included in the update history.
    • After the fix:
      • The update history includes only information of the fields actually changed.