The next Kintone update is 9th August 2019. The release also includes the following updates.

Kintone JavaScript API

Spec changes

• The maximum file size of both system-wide and app-level JavaScript and CSS customization files will be increased.
  • Relevant pages and/or APIs:
    • JavaScript and CSS Customization settings page of the Kintone Administration settings
      Reference: System-wide JavaScript and CSS Customization
    • JavaScript and CSS Customization settings page of the App settings
      Reference: App-level JavaScript and CSS Customization
    • Update Customization API
  • Details:
    The maximum JavaScript and CSS file sizes will be increased to 20MB.
    • Before the change:
      • JavaScript files (Desktop and Mobile): 5MB
      • CSS files (Desktop and Mobile): 512KB
    • After the change:
      • JavaScript files (Desktop and Mobile): 20MB
      • CSS files (Desktop and Mobile): 20MB

Bug fixes

• A bug exists where if an App has categories two or more layers deep, trying to set the value of the category to one of the category selections in the second layer or deeper is not possible with the following mobile events and method. This bug will be fixed in the August update.
  • Relevant APIs:
    • Record Create Onload Event (mobile) (mobile.app.record.create.show)
    • Record Create Field Change Event (mobile) (mobile.app.record.create.change.(fieldcode))
    • Record Edit Onload Event (mobile) (mobile.app.record.edit.show)
    • Record Edit Field Change Event (event) (mobile.app.record.edit.change.(fieldcode))
    • Set Record Value (mobile) (kintone.mobile.app.record.set())
  • Details:
    When using one of the above mobile events or method to set a category value that is two or more layers deep:
    • Before the fix:
      • The category is not selected.
    • After the fix:
      • The category is selected.
• A bug exists where if an App has two or more categories with the same name, using one of the following mobile events or method to set one of those categories results in all of the categories with the same name being set. This bug will be fixed in the August update.
  • Relevant APIs:
    • Record Create Onload Event (mobile) (mobile.app.record.create.show)
    • Record Create Field Change Event (mobile) (mobile.app.record.create.change.(fieldcode))
    • Record Edit Onload Event (mobile) (mobile.app.record.edit.show
    • Record Edit Field Change Event (event) (mobile.app.record.edit.change.(fieldcode))
    • Set Record Value (mobile) (kintone.mobile.app.record.set())
  • Details: When using one of the above mobile events or method to set a category value when other categories with the same name exist:
    • Before the fix:
      • All categories with the same name are set.
    • After the fix:
      • Of the categories with the same name, only the very bottom category is set (changed to match the desktop behavior).

Error message changes

• A change will be made to the error message that appears when using the Update Space Body or Update Thread APIs, and a file that has already been deleted from the temporary storage space* is included in the request parameter body.
  • Relevant APIs:
    • Update Space Body (PUT /k/v1/space/body.json)
    • Update Thread (PUT /k/v1/space/thread.json)
  • Details:
    The following change to the error message will be made:
    • Before the fix:
      • Illegal request.
    • After the fix:
      • Attached file not found. The file may have been deleted. * Using the Upload File API uploads a file and saves it to a temporary storage space.
        If the stored file is not added to an attachment field or a space using an API, the file will be deleted from the storage space after 3 days.

User API

Bug fixes

• A change will be made to the HTTP status code and error message that appears when calling the Add Departments or Update Departments API without including the required department code in the organizations property.
  • Relevant APIs:
    • Add Departments (POST /v1/organizations.json)
    • Update Departments (PUT /v1/organizations.json)
  • Details:
    When calling the Add Departments or Update Departments API without the department code in the organizations property:
    • Before the fix:
      • The HTTP status code is 520 and the "Illegal request." error is shown. The department creation or update is not successful.
    • After the fix:
      • The HTTP status code is 400 and the "Missing or invalid input." error is shown. The department creation or update is not successful.