2023.10.0

Release date: 3 November 2023

Unique record values

Introducing the Unique value only feature: Ensure the uniqueness of all text and number records in a field, eliminating the need for complex identification methods of duplicates.

To spot uniquely constrained fields within an entity, refer to the Is Unique column.

Be aware that values in uniquely constrained text fields are case-insensitive, treating "unique_value" and "UNIQUE_value" as duplicates.

If needed, you can easily revert by clearing the Unique values only checkbox, allowing duplicates once again.

Bulk addition of records

Spare yourself from manual entity data entry: Instantly add records using the Import data feature.

Just create a CSV file mirroring the target entity structure, ensuring columns match field names and data types. Import the file to witness your entity grow.

For import success and failure outcomes, check our documentation.

Known issue

When saving CSV files in UTF-8 format using Microsoft Excel, be aware that the default CSV UTF-8 format includes a Byte Order Mark (BOM), which causes importing failures due to lack of support.

To avoid this, consider using alternative methods to save CSV files without the BOM:

1. Open your CSV UTF-8 Microsoft Excel file in a text editor (for example, Notepad).

2. Go to File > Save as. At the bottom of the Save as window, notice that the UTF-8 with BOM option is selected in the Encoding dropdown. This is what we need to change.

3. Click on the Encoding dropdown and select UTF-8.

4. Save your file and retry importing your data.

5. Voila!

Increased character limit for entity and field names

The maximum character limit for entity and fied names was increased from 20 to 30 characters.

This change prevents import failures of schemas containing entities or fields with name lengths over 20 characters. If you still have entity or field names exceeding 30 characters, make sure to shorten the name, then retry the import.

Updates to the OpenAPI file

We have updated the OpenAPI file to use lowerCamelCase for property names. This change was needed to resolve several naming inconsistencies.

We recommend using the updated OpenAPI file and changing the property names in your application to the new naming convention. Continuing to use the previous OpenAPI file can break the functionality of your application.