5.0 Build 3648!

General
1

This release includes improvements to the form designer that allow you to set conditional required fields based on formulas, custom translatable validation error messages, and several bug fixes.

Improvements

  • Added required rules, allowing fields to be required only when a specified condition is met (formula-based required fields).

  • Form designers can now define translated error messages for validation rules, which are used across data entry, table view, and import/export.

  • Cells hidden by relevance rules are now grayed out and cannot be edited in the interactive table.

Bug fixes

  • Fixed an issue that could cause some valid records to incorrectly appear as invalid in the table view.

  • Fixed PIVOTLONGER to preserve the original option order for select field values instead of sorting them alphabetically.

  • Fixed missing totals in the pivot table when a row dimension with Totals is placed above measures.

  • Fixed an issue that allowed users to configure forms with both a serial number field and another field marked as the key.

  • Fixed a visual issue in the date pickers in the validation and relevance rule editors.

  • Fixed an issue where adding a calculated column would deselect previously selected columns the table view editor.

  • Fixed an issue where reference fields could be reset to blank when editing a record in the interactive table if the referenced form contained a record with a blank key.

  • Fixed an issue where locked records could still be edited in the interactive table view.

4 Likes
2

sorry, but why is this considered a bug?

3

Hi Luigi,

If you add a serial number field to your form it automatically becomes the key field, and you cannot have an additional key in the same form.

Normally, if your form already contains one or more key fields and you try to add a serial number field, the form designer displays a warning that the existing key fields will no longer be marked as Key. We identified a bug that allowed this validation to be bypassed in one specific scenario, which could result in both a serial number field and other key fields existing in the same form. This was the issue we fixed.