Complex fields — references, embedded data, queries, locations, attachments — have always been the ones that send you somewhere else to finish the job. In ’26 they are configured where you are already working.
What it means
You can add and configure all complex Field Types directly in the View Rule form, without navigating to separate supporting Views. The View Rule becomes a unified authoring interface rather than a starting point that hands off.
Bundled with it is a second, less obvious improvement: query list fields and reverse reference fields now support a full, consistent set of read-only table features in the full object display of Case and Data objects.
What it does
-
All complex Field Types in one form. References, Embedded Data, queries, locations, and attachments are configured in place.
-
Live preview. You see the result of the configuration as you build it.
-
Local actions in read-only tables. Actions such as Create are available from query list and reverse reference tables.
-
Automatic context passing. Reverse reference fields pre-populate the correct field using context obtained from the field Rule, so the user is not asked to re-state something the system already knows.
How it works
The enhancements are enabled by default and require no configuration after you update. Open a View Rule and the complex Field Types are available to add and configure there.
What to remember
-
Automatic context passing is the detail that changes user experience. A reverse reference field that pre-fills the linking field removes a step where users previously made mistakes. It is worth checking this behaves as you expect in your own model.
-
Consistency is the real deliverable. Query list and reverse reference tables now behave like other tables. Users stop having to learn per-table exceptions.
-
No configuration, no update impact. On by default, existing Views unaffected.
Technical documentation: Configuring fields in the UI