API Updates for February 2019

The next Kintone update is 8th February 2019. The release also includes the following updates.

Kintone REST API

Bug fixes

1. Fields without access permission will no longer be included in the API response:

  • Relevant APIs:

  • Bug fix details:

    • In the Field permission settings, if all of the following conditions are present:

      • A User Selection field (or Group Selection field, Department Selection field, Created By field, Updated By field, or Assignee) is used to give view and/or edit permissions to a target field
      • Everyone has neither view nor edit permissions (view and edit are both unchecked)

    • The following occurs when a user that is not set in the User Selection field (or Group Selection field, Department Selection field, Created By field, Updated By field, or as the Assignee) runs one of the relevant APIs:

      • Before the fix: Even without access permission, the field is included in the response
      • After the fix: The field is not included in the response

2. Fields included in Localization settings will be copied over correctly when set in the Field Mappings settings of the Lookup field:

  • Relevant APIs:

  • Bug fix details:

    • If all of the following conditions are present:

      • A Lookup field has a Radio Button field or Drop-down field set in its Field Mappings settings
      • The Radio Button field or Drop-down field in both the source App and destination App is included in the Localization settings in the same language

    • The following occurs when one of the relevant APIs is run:

      • Before the fix: Even if the Localization settings of the field in the source App is the same as the field in the destination App, the field value is not copied over.
      • After the fix: The record is added or updated, and the field value is copied over.

Other updates

The User API can now be run with kintone.api()

  • Relevant API:

  • Details:

    • It is now possible to run any User API with kintone.api().

Kintone JavaScript API

Bug Fixes

An error will appear when attempting to change the value of a field with no edit permissions during the Process Proceed Event:

  • Relevant API:

  • Bug fix details:

    • In the Field permission settings, if all of the following conditions are present:

      • A User Selection field (or Group Selection field, Department Selection field, Created By field, Updated By field, or Assignee) is used to prevent users (or departments or groups) from editing a target field (editing permission has been removed)
      • A customization has been added to the App where the target field is edited when the Process Proceed Event occurs

    • The following occurs when a user without permission to edit the target field triggers the Process Proceed Event:

      • Before the fix: There is no error and the status changes
      • After the fix: There is an error and the status does not change
Was this article helpful?
0 out of 0 found this helpful
Do you have any questions or issues related to this article?
Please share your views with us in the Community forums!