D365 Understanding limitations

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
  • Sharing can’t be used with dual-write.
  • Deletion of shared records isn’t yet fully supported and shouldn’t be used.
  • Ledger or default dimension can’t be shared
  • Sharing can’t be used in combination with Retail Channel Databases.
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
  • Supports only infinite capacity.
  • Doesn’t support resource load functionality.
  • Doesn’t consider route scrap.
  • Supports Duration only as the primary resource selection.
BYOD scheduled batch jobs
  • There should be no active locks on your database during synchronization. Active locks can cause slow writes or even failure to export data to your Azure SQL database.
  • You can’t export composite entities into your own database. Currently, composite entities aren’t supported. You must export individual entities that make up the composite entity. However, you can export both entities in the same data project.
  • Entities that don’t have unique keys can’t be exported by using incremental push. You might face this limitation especially when you try to incrementally export records from a few ready-made entities. Because these entities were designed to enable the import of data, they don’t have a unique key.
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
  • Company or legal entity fields other than the system dataAreaId field can’t be recognized or treated automatically in the that way dataAreaId can.
  • The cross-company behavior for views is too restricted to the properties of the root data source, even when non-root data sources have a dataAreaId field.
Asynchronous customer creation mode
  • Loyalty cards can’t be issued to async customers unless the new customer account ID has been synced back to the channel.
Dual Write : Sync on-demand with the Supply Chain Management pricing engine
  • The setup of charges and charge allocations in Supply Chain Management isn’t replicated in Sales.
  • Pricing doesn’t consider special retail pricing that is specified in the Retail Channel column on the sales order line page in Supply Chain Management.
  • Discounts that are defined in the Trade Allowance Management section of Supply Chain Management aren’t considered.
  • Pricing doesn’t consider sales agreements.
You can’t add the Price unit field to the Purchase agreement page
  • Some shared fields in the agreement framework can’t be included in personalizations. This limitation occurs because of the data model that is implemented. Therefore, you can’t personalize the Price unit field.
Movement of inventory with associated work in Warehouse management
  • Only the ad hoc movement is currently supported. That means that you will not be able to move reserved inventory through the movement by template mobile device menu items.

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

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.