This release is packed with improvements that make working with large datasets faster and smarter.
Highlights:
→ Field indexes – Speed up filters by up to 10x on large tables
→ Field value constraints – Enforce uniqueness and improve data quality
→ Multi-row selection – Perform batch actions with ease
→ Custom CSS/JS – Style your App Builder projects your way
→ Send Email action: Trigger emails from your app using any SMTP server
→ Application debugging — See misconfigurations directly in the editor
Thanks for launching field constraints! My quick question is how does this work with the API? Specifically, if we try to enter a value into a unique field via the API that is already in use, does the API simply return back an error?
For now this is the only available constraint and it is compatible with: single line, long text, number, date, duration, rating, single select
Now:
if field is compatible and there are no duplicates - constraint will be applied and from now on you won’t be able to add non-empty duplicates (you will get ERROR_FIELD_DATA_CONSTRAINT in such case)
If there are duplicates (excluding empty fields) - modifying field will return ERROR_FIELD_CONSTRAINT error
if you try to apply incompatible constraint you will get ERROR_INVALID_FIELD_CONSTRAINT
Highlights:
Want your Baserow solution featured? Submit it here
Thanks for all your feedback—many of these features were inspired directly by you!