Comments
Something we're using as a "workaround" is piping API calls you want to see the contents of through Logic Apps on Azure. Allows detailed logging, additional processing and you can have a different authentication scheme and url scheme using APIM.Not a fun sell of course and has its own issues.
Our organization relies heavily on FetchXML-based SSRS paginated reports for Dynamics 365 Customer Engagement. These reports are essential for compliance, operational reporting, and integration with existing workflows.Currently, the Report Authoring Extension only supports Visual Studio 2019 and earlier. Visual Studio 2022 introduced a 64-bit architecture, and the lack of support for this extension creates significant challenges:Increased operational risk from outdated tools.Higher costs for licensing alternatives.Delays in delivering critical reports to business stakeholders.
In additional, I think some cross dimension value settlements won't be important for some financial dimensions, so to refine it further, it would be good in the year end config, to be able to define by financial dimensions, those which you do not want to allow cross dimension value settlement.
This is a real issue when dealing with purchase orders with long lead-times that will have ETAs changed likely more than once due to external factors such as transshipment delays, conflicts impacting regular shipping routes, weather, etc. It shouldn't be a problem to be able to change dates and quantities simply because a Quality Order is still on open status, which by the way is generated once a Receipts List is created. Receipts List can be created well in advance depending on each business particular ways of working and, again, shouldn't be an impediment to enable PO dates to be changed.