Currently, DataItemTableFilter applies after joining two different data items. The work around is to make your filters occur upstream from your joins; however, queries do not support multiple data items in parallel levels. This means there is a functional gap if you have several data items with table filters involved.

I propose one of three solutions:

  1. [Recommended] Add a Data Item attribute that dictates if the DataItemTableFilter applies before or after the join.
  2. Default the DataItemTableFilter to occur before the SQL joining behavior.
  3. [Less recommended] Allow for multiple data items in the same tier.

Until one of these solutions is implemented, I have to run separate queries on similar data sets or scrap queries altogether.

Category: Development
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team



FYI here is an article from MS communities that provides more detail on the undesirable interaction between joins and filters.

Category: Development