As we know, the Dynamics 365 portfolio of apps and functionally is extremely rich and have vertical features for most industries. We also know that driving the Microsoft R&D with a tight coordination between the apps is difficult, and I also understand Microsoft want to provide new highly requested features and innovation quickly to the market. In the highly agile and innovative domain we are in, this can be seen as an accelerated delivery of MVP’s (Minimum Viable Products). The nature of MVP is more quickly get feedback from the marked to better understanding on where the next innovation cycle/wave should take the feature.
Understandable this can result in release of features that have limitations and workarounds. Microsoft is quite good in documenting limitations, but I would say we see an increase in limitations where apps and feature combinations that are not supported, colliding or limiting each other. I did a small search in learn.microsoft.com, and there are more than 186 documentation pages describing limitations that you should be aware out. Click
here for the a list of limitations. Also be aware that there are also many undocumented limitations when you try to combine features from different areas like SCM, Commerce, Process industry, Dual Write++.
Understanding limitations can save you for a lot of time in project and prevent implementing scenarios that is not working or supported. My recommendation is to search for limitations as an important step in any implementation, to ensure that you don’t hit into a hard documented limitation. Very often you realized the consequences of the limitations until you actual test.
Here is just a very small example subset of some limitations Microsoft have described to give you an idea:
|Demand forecasting||Demand forecasting might not be the best fit for customers in industries such as commerce, wholesale, warehousing, transportation, or other professional services.|
|Cross-company data sharing||
|Cross-company product sharing||Not released yet, but it is very restricted to what can be shared. Do not assume anything, and keep in mind that it is very painful to reverse after you have enabled it. READ THE DOCUMENTATION!|
|Infinite capacity scheduling for Planning Optimization||
|BYOD scheduled batch jobs||
|Data import/export||String sizes are limited to 32,768 characters.|
|Product change management||If you have a distinct product, you can change it only to an engineering product that doesn’t track the product dimension in transactions|
|Active Directory security groups||Several of the limitations affect internal control and auditing|
|Cross-company behavior of data entities||
|Asynchronous customer creation mode||
|Dual Write : Sync on-demand with the Supply Chain Management pricing engine||
|You can’t add the Price unit field to the Purchase agreement page||
|Movement of inventory with associated work in Warehouse management||
If I’m not limited on time, I can try to add more limitations later. Take care, and remember the future have no limitations
One thought on “D365 Understanding limitations”
Good to know – very interesting Jan. Thanks.