Releases

This update includes a fix for a TEXTJOIN formula that caused the table display to crash when referencing multiple fields.

Bug fixes

• Formulas using TEXTJOIN with multiple-reference fields will now be marked as invalid, as this usage is not currently supported.

This release includes system translation support for additional languages, along with a few bug fixes.

Improvements

We added system translations for the following languages:

• Armenian
• Kurmanji
• Nepali
• Oromo
• Somali
• Sorani
• Tagalog

Bug fixes

• Fixed an issue where calculated fields using TEXTJOIN formulas based on parent fields were not displayed when adding subrecords directly from the subform.
• In data entry, only the first 1,000 subrecords are now shown by default. We added a new “Show more” button that lets you load additional batches of 1,000 subrecords. This change improves performance when loading parent records with a large number of subrecords.
• Fixed an issue that caused an error when exporting forms with subforms that had sorting applied to one of the columns.

• AI-5649 FIXED: Week value is not displayed properly in data entry and record panel

This release adds a new slicer component for reports. It also includes the ability to recover deleted databases through the user interface, along with some bug fixes.

New features

• Interactive slicers for reports: Slicers allow database administrators and report designers to create interactive reports that allow stakeholders to explore the data interactively. Read the tutorial and the reference article for this new feature.
• Recover deleted databases through the user interface. Billing account administrators can now recover deleted databases within 60 days of their date of deletion, through the user interface without having to contact support.

Bug fixes

• Fixed an issue where entering !ISBLANK(field) into the Formula Editor was changed to ISBLANK(field) when saved.
• Added an error message for the required attachment field when users try to submit a record without completing it.

This release contains a new improvement on the Audit log and some bug fixes.

Improvements

• Audit log export: Users can now use the additional setting in the audit log menu to export their logged actions. They can filter by date, action type and resources before exporting.

Bug fixing

• Serial numbers were not duplicated when duplicating a database: Before, when duplicating a database including data, the serial number values were not added automatically and the users had to edit the records in order to populate the serial number values. Now, this is addressed and users can simply duplicate the database and that will duplicate all form settings and serial numbers as well.
• API import failed in certain conditions: This issue was very specific and was blocking the API importer when a null parameter was introduced.
• Single select options translations still displayed even after language was deleted: After a language was deleted, there was an issue affecting single select values/options in table display that would still translate them if the user switched the language. Now, this is addressed and when a language is deleted the values will not be translated anymore.
• Calendar days are shifted in all languages (expect English): After the translations release, there was a small visual bug with date selector where the label for Saturday was missing. This is now fixed.

With this release, we have greatly improved the way we internally handle system translations of the application. This includes labels like “Add Record” or “Please complete the required fields.” As a result, we are now able to add new system translations more quickly.

This release includes new system translations for the following languages:

• Amharic
• Bulgarian
• Danish
• German
• Hausa
• Hindi
• Italian
• Khmer
• Kinyarwanda
• Norwegian
• Swahili
• Swedish
• Thai
• Tigrinya
• Urdu

This release includes some bug fixes and small improvements.

Bug fixes

• A hotfix involving population of default values when relevance rules were set on the section header. Recent improvements introduced a regression related to default values and relevance and hidden fields. We have restored the expected behavior: default values are not populated for irrelevant fields, however default values are populated for hidden fields or fields under reviewer only setting.
• Display all provided columns in the importer review invalid screen. Before, we had a misalignment regarding the provided columns and the columns we showed in the review invalid screen. If the user provided unmatched columns, these were not displayed in the invalid screen. Now, we display all the provided columns.
• Users can no longer view attachments with preview browser extensions. This issue occurred after we made some improvements to the attachments so that user can save them in drafts as well. We mistakenly affected a customer that was relying on the link to read the attachment with an extension. Now, this issue was addressed.

Improvements

• Validation and tooltips in the importer invalid screen: Before, we only had validation and tooltip messages for the review records screen, which makes reviewing invalid records tedious. Now, we allowed the same logic in the review invalid screen which allows users to investigate what went wrong with the entire list of invalid rows.
• Expanded the signature field size
• The Collection links menu now includes QR codes that users can share. Existing collection links will also contain QR Codes.

This release includes improvements for attachments while offline and a bug fix.

Improvements

• App collection links now fully support collecting attachments (photos, signatures, files, etc) while offline
• Users can download attachments from draft and pending records in the web application, mobile application and app collection links prior to submitting them to the server. This allows users to review attachments in draft records prior to submission.

Bug fix

Fixed an issue where the records panel showed incorrect records in shared and default views when users selected multiple records.

• AI-5545 FIXED: Importer is crashing in synched database if there is an unmatched key-required reference
• AI-5560 FIXED: Performance issues in data entry when navigating to subforms due to cancelled chucks

This release contains the following hotfixes:

• Formulas with single select options are not properly handled in reports when switching to a translated language: When the database contained translations and the form a single select field, if the user created pivot report, using the single select field in formulas for the report would not work properly as we were not storing the ID of the option. Now, this issue is addressed, and we always store the ID of the resources in the form so that language changes (renaming the option) do not affect reports.
• Default values are not populated automatically when required columns are ignored or not included: The importer should allow you to ignore a required field if that field has a default value. Previously, if you took advantage and did not match the a column to the required field, the importer would allow you to proceed, but not populate the default value. This is now fixed.
• Clarified the subject line when resending the account activation email

This release contains a hotfix for a performance regression in the data entry view introduced by a recent improvement.

This release contains a few fixes.

• Multi-select reference fields and importing: There were two issues affecting multiple reference when importing; When adding a new multi-reference field in a form, importing over blank values had the consequence of records not being displayed in the table display. And also, sometimes when editing records and adding a new multi reference value had the same effect. Now, both of the cases are covered.
• Multi-reference options in importer: Previously, users could import multiple duplicate options via the importer interface;
• Importer crash: When the reference form had a record label set, and the referrer form had a multi reference field pointing to the reference form, trying to import didn't work because the importer interface would just crash. While fixing this we also found another minor issues that was addressed.

This release includes a major improvement to the importer.

New features

API and form sources import

You can now import records into a form using either another form or an external JSON API as the source. A new set of options is available under the Import menu:

• Paste data: Copy and paste data directly from a spreadsheet.
• From another form: Import records from any form you have access to, across any database.
• From API: Import records from an external API. If the API is authenticated, credentials will be required.

Import filtering

You can now apply filters when importing records, based on fields that have been mapped during import setup. Filtering behaves similarly to table views, except filtering on multiple reference fields isn’t supported yet.

Save and reuse import configurations

When importing from another form or an API, you can save your import setup for future use. Saved configurations are shared across the database and can be reused by other users.

New permission: Manage import configurations

A new permission has been added to the grant-based role system: Manage import configurations. Users with this permission can:

• Save import configurations
• View and reuse all saved configurations for the form
• Edit or delete saved configurations

This permission is not included in any existing roles by default.

Bug fix

We’ve also fixed the issue where legends were not displayed in pie charts. They should now display correctly.

This release includes improvements to the billing account and the following bug fixes:

Improvements

• Added "addons" property to billing accounts, which will show on the billing account detail page.

Bug fixes

• Previously, subform exports included all parent form fields except the reference fields that are not set as key. We have made it more consistent by only including parent fields that are marked as keys. More improvements are planned as part of the upcoming export menu changes.
• Fixed an issue where custom lookup formulas referencing parent forms showed "#ERR" in table views.
• Partial matching on required reference fields is now supported in the importer.
• Fixed an issue where data entry would reload when uploading attachments on lower-spec devices, making it difficult for users working with a large entry form.

This release includes the following fixes:

Reference regressions

• Addressed an issue that was duplicating reference cards in report design when dragging the card from the available list to the measures or rows/columns sections. This was previously affecting any form that contained at least 3 reference fields that were pointing to the same form. Now, the issue was addressed and users should not experience this any longer.
• Fixed an issue where using views to drag reference fields in subforms would point to the incorrect reference field if the parent contained multiple references.

Improvements

• We have also improved the database duplication mechanism, now the database duplication will duplicate the form settings entirely. Meaning that record labels, default values and custom lookups settings will also be transferred accordingly.

This release includes the following fixes:

• Hotfixed a regression that was allowing users to submit subrecords with a duplicate key via a draft parent record. While we do not allow adding duplicate keys to be added via data entry in any situation, in this case the regression caused a gap where users were able to add duplicate subrecords while adding a draft parent record.
• Fixed an issue where after merging records that were referenced via a multi-reference field the values would show up as duplicated in the multi-reference column.
• Addressed an issue where pending records were not pointed accordingly to the new reference after a merge event. If a merge event took place before a user would sync the data any reference pointing to secondary records would show up as #ERR. Now, we correctly handle synchronization and all references to secondary records are be updated to point to the primary record.

Release of version 4.0 build 3288 with the fix for the sync issue which caused the rollback.

• AI-5177 FIXED: Secondary records not updated in multiple reference field after merge
• AI-5397 FIXED: Personal views are unselected after reloading the page
• AI-5401 FIXED: Data entry performance issue when form contains releance rules and validation rules in combination with section headers
• AI-5411 FIXED: Default values are still populated for irelevant fields when adding new records
• AI-5421 FIXED: Sections containing irelevant required subforms are displayed as invalid in certain conditions
• AI-5129 Allow platform support admins to remove users from technical contacts list on a billing account

This release includes bug fixes and improvements to the data entry and subscription detail pages.

• Fixed a crash on the data entry page when a multiple reference form was deleted or inaccessible.
• Fixed incorrect validation of sections containing subforms on the data entry page. Additionally, validation has been improved so that all preceding sections are now checked when users interact with a subsequent section.
• Corrected the logout confirmation dialogue on the mobile interface, which was previously displayed in all caps.
• Added a documentation link to the account credits page, providing information on what they are, how they are used, and how to request a refill.

This release includes improvements to the subscription detail page along with several bug fixes.

Subscription detail page improvements

We've made several improvements to the subscription detail page:

• Added a sidebar with quick links to contact sales and access the Managing Billing documentation page

• Added an overuse banner that appears when the user limit is exceeded

• Added a section displaying the time remaining on the subscription and a direct button for renewal
• Included dedicated sections for open quotas and billing history

Bug Fixes:

• Fixed an issue where the DATE() function could produce invalid dates in certain cases
• Fixed an incorrect warning message that appeared on subform entries when users lacked permission to add records
• Fixed an issue where the table display would crash if a user had add permission without view permission
• Fixed a layout issue where the edit button for subrecords was pushed out of view in data entry due to an overflowing subform field label