Updates

We’ve made several improvements to Subforms to enhance flexibility, performance, and data control.

What’s new:

• Support for filtering connected values
• Dependent dropdowns within subforms
• Validation requirements to define how many rows must be added
• Improved equation performance for faster updates

We’ve also introduced grouping capabilities, allowing subforms to be organized in a more structured format, with optional subtotals for improved visibility and reporting.

Subform Validation Options
You can now customize validation rules for subform items, including required fields, minimum or maximum rows, and other conditions to help ensure data consistency.

⚠️ Note
We’re currently working through a few final issues to ensure Subforms are fully stable for release.

Example Video
Check out the latest walkthrough showcasing these features in action.

You can now apply display rules directly to field options.

This allows you to show or hide specific choices within fields like Radio, Select, and Multi Select based on values from other fields.

This makes forms more dynamic and ensures users only see options that are relevant to their input.

We’re rolling out Subforms, allowing you to create multiple child records directly within a parent form.

For example, when creating an Invoice, you can add all related Line Items within the same form, without needing to navigate away or create records separately.

Rollup fields in the parent table can be displayed with real time calculations, and any equation or formula fields in the child table will automatically update as new records are added.

This allows totals, counts, and calculated values to update instantly as users enter data, creating a more seamless and dynamic form experience.

We’ve introduced Import Templates for API based imports to streamline working with external data sources.

Previously, imports from outside Tadabase required manual setup and mapping each time. You can now save your import configuration and reuse it as needed.

This makes external data imports faster, more consistent, and easier to manage.

Enterprise Search can now display table names when searching via connected fields.

This provides additional context for search results and makes it easier to understand where data is coming from when working with related records.

We’ve enhanced the Display Rules interface in Universal Components to make it easier to manage, especially when working with multiple conditions and actions.

We’ve expanded redirect rules in forms to provide more flexibility in where users are directed after submitting or editing a record.

Previously, redirects were limited to the detail page of the same record type. Now, you can define more dynamic destinations based on your data.

Redirect to Connected Pages
You can now redirect users to connected records. For example, if a Project has an Assigned User, you can redirect to that user’s detail page anywhere in the app.

Redirect to URL
You can now redirect users to a custom URL, including support for dynamic field values to personalize the destination based on record data.

Match All and Match Any (Validation Rules)
You can now define validation rules using Match All or Match Any logic, giving you more control over how multiple conditions are evaluated.

Temporary Fields (AI Prompts)
AI Prompts now support temporary fields, allowing you to store and use intermediate values within a prompt.

This provides more flexibility when building more advanced AI driven workflows.

Search by Connected Fields
The Enterprise Search Component now supports searching using connected fields.

For example, you can filter a Jobs table based on fields from connected tables such as Users, allowing you to dynamically refine results using related data.

This makes advanced filtering more flexible and accessible directly within Enterprise Search.

We’ve added advanced display rules to Universal Components, bringing similar functionality previously available in Tables and Lists.

You can now define rules at the component level, allowing greater flexibility in how conditions and actions are applied. Within each rule, you can target specific fields or apply changes across the entire component.

This makes it easier to manage styling and logic in a more centralized and scalable way.

We’ve also introduced support for rules based on logged in user conditions. For example, you can define rules based on whether a user is logged in, not logged in, or belongs to specific roles.

These rules are designed for front end control and do not replace existing security settings at the layout, page, or row level.