---
id: post/duiliotacconi-com/1894
type: post
title: FlowFields with same filters and table in a single OUTER APPLY
summary: 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.
tier: community
language: en
tags:
  - flowfield optimization
  - sql performance
  - smartsql
  - query optimization
  - aggregation functions
  - outer apply
system: platform
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:56:55.282Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 7e0b458142d63a97f32766dff042c86e2fb97fd5d98c5d9314d6a34fceaa7a39
evidence:
  - kind: blog
    url: https://duiliotacconi.com/2026/02/13/flowfields-with-same-filters-and-table-in-a-single-outer-apply/
    title: FlowFields with same filters and table in a single OUTER APPLY
    date: "2026-02-13"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://duiliotacconi.com/2026/02/13/flowfields-with-same-filters-and-table-in-a-single-outer-apply/
    title: FlowFields with same filters and table in a single OUTER APPLY
    date: "2026-02-13"
    commit: null
    t: null
    quote: A good platform feature, then, that is turned always on by default since 27.0.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "1894"
source_id: duiliotacconi-com
source_name: Duilio Tacconi
url: https://duiliotacconi.com/2026/02/13/flowfields-with-same-filters-and-table-in-a-single-outer-apply/
published_at: "2026-02-13T13:56:26.000Z"
author: Duilio Tacconi
full_text: false
words: 1114
quotes:
  - text: A good platform feature, then, that is turned always on by default since 27.0.
    why_it_matters: Confirms the feature requires no configuration and is automatically active
code_objects_mentioned:
  - table DT Customer Demo
  - table DT Sales Entry
  - enum DT Document Type
systems:
  - platform
  - development
versions_mentioned:
  - "27"
  - 2025 Wave 2
preview:
  embeddable: true
  frame_url: https://duiliotacconi.com/2026/02/13/flowfields-with-same-filters-and-table-in-a-single-outer-apply/embed/
  image: https://i0.wp.com/duiliotacconi.com/wp-content/uploads/2026/02/samriordan.03.jpg?fit=1200%2C531&ssl=1
  image_alt: null
  image_w: 1200
  image_h: 531
  site_name: Dynamics 365 Business Central tales, myths, legends. And something serious.
  favicon: https://duiliotacconi.com/wp-content/uploads/2023/07/cropped-wordpress.png?w=32
  probed_at: "2026-10-07T11:50:34.819Z"
---

# FlowFields with same filters and table in a single OUTER APPLY

[Read the post](https://duiliotacconi.com/2026/02/13/flowfields-with-same-filters-and-table-in-a-single-outer-apply/) · Duilio Tacconi (Duilio Tacconi, MVP) · 2026-02-13 · 1114 words · tier community · reviewed (checked by Opus)

> 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.

## 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.