Comments
Yes - this is long overdue. Customers complain about the marketed ease of use pf Power BI and then the reality in using it with products like Business Central. Suggestion is to transfer marketing budget to product development with the goal of allowing them some semblance of the marketing presentation. Good place to start is ER-diagrams.
Strongly support this idea for better integrating D365 SCM Inventory Visibility with D365FO Inventory. Real-time synchronization would resolve issues of stock over-promising in high-activity environments, increase operational efficiency, and enhance customer satisfaction. Implementing event-based triggers for transfer, production, and purchase orders would provide a more accurate and timely inventory status, thereby aligning with the overarching goal of improving Supply Chain Management in Dynamics 365
Financial dimension may have to be updated on past transactions for data consistency.
customer adds local Chart of account as dimension due to legal reporting requirement. But some past data do not have this dimension.
Fiscal report may be requested for 3 years back. Then this dimension must be added on all transactions;
This process nonetheless have to be secured and traceable.
Working with a client that is doing a major credit review of all customers and have decided to populate the DUNS field; however, the client is unable to insert this information as the DUNS number field is not part of the entity Customers and will have to do the manually. I would assume any field on any form would be made available on the entity...
Another example just found:
Supose we have Subpage1, that is used as a part in 2 API pages, APIPage1 and APIPage2.
Both APIs are part of the same group of API pages. Both have the same entityName and entitySetName for Subpage1, sharedSubPage.
This results in a runtime error when trying to access either one of the APIs, stating "500 sharedSubPage cannot publish sharedSubPage because a different entity with the same name has already been added.".
The error is not even raised when publishing the extension, only at runtime when trying to access the API.
Also, if we try to change the entityName and entitySetName for Subpage1 so that it is not the same in both APIs, let's say sharedSubPage1 and sharedSubPage2, when trying to access both APIs now we don´t run into an error but we see that both supages in both APIs are called sharedSubPage2.