Comments
I would also like to add that this request, concerning the lack of granularity in the management of tracking options, goes beyond company-specific constraints or business requirements.As we operate in France, the CNIL has recently issued new regulations regarding the collection and use of email open data through pixel tracking. At present, we do not have the ability to disable this data tracking feature in Customer Insights Journeys (datas that we do not use furthermore), and this places us in a position of non-compliance.More granular control over tracking settings is therefore necessary.Kind regards,Nicolas
Until NAV2018, this was standard functionality. Even today, a large part of the program code is still there, and only pieces of code are missing.Microsoft described this as a bug, referring to better pricing conditions if all items are combined into a single order. (TrackingID#2604290050002740)
While this approach has merit, it may not work well for countries or deployments spanning multiple timezones. A more robust solution could be to leverage an OData timezone property to pass a timezone context with each API request, applying it for the entire session. This would allow external systems to manage timezone handling independently, while ensuring that datetime functions in Business Central — such as Today() or Time() — operate correctly throughout the session. Indirectly triggered objects like the Service Document Log would also benefit from the correct timezone context without requiring any additional adjustments.
Same here, both in Formula and/or BOM we set up priorities as mentioned here: https://learn.microsoft.com/en-us/dynamics365/supply-chain/master-planning/item-substitution#plan-groupsIt keeps planning purchase orders and trying to pick for PO items with no stock although the next in priority has enough stock for manufacturing requirements.It would be nice to have this for a couple of projects we are delivering.