The next Kintone update is 10th January 2020. The release also includes the following updates.

Kintone JavaScript API

Spec changes

• Promise is now supported for all Kintone events, except for Field Change Events.
  • Relevant APIs:
    • Record List Onload Event (app.record.index.show mobile.app.record.index.show)
    • Record List Inline Edit Event (app.record.index.edit.show)
    • Record Details Onload event (app.record.detail.show mobile.app.record.detail.show)
    • Record Create Onload Event (app.record.create.show mobile.app.record.create.show)
    • Record Edit Onload Event (app.record.edit.show mobile.app.record.edit.show)
    • Record Print Onload Event (app.record.print.show)
    • Graph Display Onload Event (app.report.show mobile.app.report.show)
    • Portal Display Onload Event (portal.show mobile.portal.show)
• Details:
  When a kintone.Promise object is returned inside the event handler:
  • Before the update:
    • Results in an error.
  • After the update:
    • The next process in the code can run after receiving a response from an asynchronous process.

Kintone REST API

Bug fixes

• A bug exists where when the following APIs are used to create or update records of an App, that contains a Lookup field configured to copy content from a Text area field to a Rich text field, the copied text value is missing newline characters, thus having incorrect formatting. This bug will be fixed.
  • Related APIs:
    • Add Record(s) (/k/v1/record.json /k/v1/records.json)
    • Update Record(s) (/k/v1/record.json /k/v1/records.json)
  • Details:
    When adding or updating record(s) with the above APIs in Apps that have Lookup function copying over content from a Text area field to a Rich text field:
    • Before the fix:
      • The newline characters are replaced with space characters instead of creating new lines, thus not having the correct formatting.
    • After the fix:
      • The newline characters would be correctly copied over, thus having the same formatting as the original text.
• A bug exists where when API tokens are used in Get Cursor API requests; records are unable to be retrieved from the Cursor. This bug will be fixed.
  • Related APIs:
    • Get Cursor (/k/v1/records/cursor.json)
  • Details:
    • When using the Cursor APIs to retrieve records from an App with all of the following conditions:
      1. When records are being retrieved from an App that you are not the Administrator of.
      2. When API token is used to authenticate the Get Cursor API request.
    • Before the fix:
      • An empty array is returned and the records cannot be retrieved.
    • After the fix:
      • Records are retrieved.