Comments
I would like to emphasize while this is an important improvement from a performance perspective Currently filtering for AL query objects is done by either the DataItemTableFilter or filter columns property. Both of these properties are executed in the background as SQL “WHERE” clauses meaning filtering to happen after the join. This changes the outcome of queries when LeftOuterJoin is used. For example when I need a query that selects Customer Ledger Entries and corresponding detail Ledger Entries with a filter on type “Application”, when there are no applications I still want the Customer Ledger Entry information. When there are no detailed ledger entries the ON clause will give me the Customer Ledger Entry with an empty column for the detailed Ledger Entry. A WHERE clause returns 0 rows. This also applies to aggregates like SUM or COUNTThis quickly becomes a problem for more complex queries where we want to aggregate data from multiple sources that may or may have records. The workaround is to retrieve this data in separate queries but this is inefficient as some data needs to be retrieved twice.Therefore I strongly support suggestion 1 of adding a Data Item attribute that sets the filter order.Proposed parameter:DataItemJoinOrder Permitted values: “WHERE”, “ON”Default value: “WHERE”
A specific case of this is the flow event table. We want to exclude this from the audit log as it does not need to be retained for any compliance or regulatory purpose. Having the ability to do a bulk delete on this table in the audit logs would be useful. Even better would be to eliminate it from the audit log all together.
This is a very important need and one of the few drawbacks of the changes from planning optimization versus legacy MRP that have not been fixed. The documentation here https://learn.microsoft.com/en-us/dynamics365/supply-chain/master-planning/supply-chain-calendars-master-planning implies that the vendor calendar would be respected over the coverage group, but that is NOT what happens, even if the parameters to respect the vendor shipping dates is enabled. Below is the verbiage from MS Learn dated from 2026, however that is NOT what planning optimization is doing. The coverage group is overriding the vendor calendar.Delivery date of a planned purchase orderThe receipt date of a purchase indicates the date when you'll receive the goods. It will be an open date in the calendar. To determine which days the purchase orders can be received on, the system considers the following calendars, in order from highest to lowest priority:Vendor's calendarCoverage group calendarWarehouse calendar for the receiving warehouse