FlowFields with same filters and table in a single OUTER APPLY
Starting with Business Central 27.0 (2025 Wave 2), SmartSQL puts all FlowFields that use the same table and the same filters into one OUTER APPLY, instead of one OUTER APPLY per FlowField. This removes duplicate data retrieval and changes the execution plan. It is always on by default.
post Dynamics 365 Business Central tales, myths, legends. And something serious.
"A good platform feature, then, that is turned always on by default since 27.0."
Key points
- Before v27, SmartSQL sent one SQL statement per record set, with one OUTER APPLY for each FlowField
- In v27, FlowFields with the same source table and the same filters share one OUTER APPLY
- Aggregations that can be grouped: SUM, AVERAGE and COUNT; MIN and MAX (with COUNT too if indexed); EXISTS and LOOKUP
- Maintained indexed views (V-SIFTs) are not grouped with non-indexed FlowFields
- The post suggests checking pageViews (CL0001) and long running SQL query (RT0005) telemetry after upgrading to see the effect
Quotes
- “A good platform feature, then, that is turned always on by default since 27.0.” (Confirms the feature requires no configuration and is automatically active)
AL objects mentioned
As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.
- table “DT Customer Demo”
- table “DT Sales Entry”
- enum “DT Document Type”
Not found in BC28-30: table “DT Customer Demo”, table “DT Sales Entry”, enum “DT Document Type”.
Context
- Features: SmartSQL optimization, FlowField consolidation, OUTER APPLY grouping, Aggregation packing, SQL query reduction, Indexed view handling
- Versions: 27, 2025 Wave 2
Source: Duilio Tacconi, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.