Troubleshooting
Limitations
- Only Form Filling at a kit level is supported, Kit Parts customisation is not supported.
- This functionality is not compatible with the “Replace field definition” option on the form filling field definition.
- Columns contain only letters (A–Z, a–z), numbers (0–9) and underscores (_) and must not already exist in the database.
- Column headings must match the corresponding form-filling field names exactly (including spacing and capitalization) so columns map to form fields correctly.
- A database must always contain at minimum, one row. The last remaining row in a database cannot be deleted.
Compatibility
- Rich text fields are supported for new line and tab characters, but not styling (e.g. bold, italic, etc…), links or other functionality.
Known Issues
- It is not recommended to include multiple databases on a single template if they share the same column/field names, as it can lead to unwanted behaviour where both dropdowns are competing to update the same field.