Suggested Mon, 15 May 2017 19:30:19 GMT by Karina Normann JakobsenUnder Review
Category: Accounts Receivable

With the removal of the concept of virtual companies, the only - however poor - real out of the box option to share master-data across legal entities was lost. This feature was widely used by many customers.

The new cross-company data sharing accepts group and reference data only, but it is not possible to share for example Customers and Vendors across multiple legal entities.

In the industry, where my customers operate it is not uncommon to have +100 legal entities, some will have +1000 and this is real legal entities, not just a dummy division of a legal entity.

Therefore it is common to share customers and vendors between companies. But it is not a all or nothing approach. Companies are grouped and data is shared between a group of companies. Which leads me to my second suggestion. Please allow us to group companies into company groups and then configure the sharing of data per group of companies instead of individual companies.


So 2 suggestions here.

1. Ensure master data can be shared between a group of companies. 

2. Allow grouping of companies into company groups.



Status Details

Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.


Shivam Pandey


Comments (18)
  • Adding my voice to the request to share partial master data. I know that some master data scenarios are being considered (Customers, Vendors), but subsets of these entities make sense. The records just need to be marked in some way to match filter criteria. Allow the table/field definition to include a filter criteria.

    For group codes like Sales Modes of Delivery, it is likely that some modes will be available in all entities (like UPS) but some modes are specific to an entity and should not be visible in other entities to avoid accidental selection on an order.

    I am working on our implementation and I need to share six fields on the Released Products table between entities (e.g. item group) but only for the items that have been released into that entity. My understanding is that Cross-company data sharing will require releasing all products into all entities which will not make sense for cases where the product is used internally in one entity for manufacturing, but does not need to be visible in the other entities. I now have to try to find alternative methods to keep these six fields in sync between entities - I had to do a big customization in an older version of AX, but I now have to avoid the overlay methods previously used.
  • Great Idea
  • For example my customer is importing customer data from CRM. It does not make sense to integrate this same customer data into 10x companies since the data should not be any different.

  • The loss of this function is unthinkable as the loss of sharing InventTable since AX 2012 is a real failing against competitors.
    I have met many times the need to share this table in full or in part.

    Indeed, some tables like VendTable or InventTable, some data must be managed partly in the local entity and the rest is common to all legal entities.

    A function to share the master data tables and select the fields to be shared in a table would be a real bonus in industrial projects with many production subsidiaries but a parent entity managing most administration parts and global master data.

  •  I would add to this that it would be best if criteria could be set up on the master data sharing. For instance, one of my customers wants to share vendors but only a specific subset of vendors.

  • This functionality is very important because it allows to share the catalogs of master accounts between the companies of the same corporate. If you do not have it, you will have to repeat the same account in each company, with the risk of losing the integrity and consistency of the information.

  • This functionality is very important for all multi-company maintenance and sharing for consolidation purposes would be impossible without this functionality

  • We have may customers in the previous versions of AX that share, within companies of the same group, customers and vendors, and this si not available in D365 and it is a must have functionality, some of the installed based customers that we are trying to move into D365, are not willing to make the switch if this si not available and unfortunately this leaves the door open for competitors to approach customer that want to move to the cloud.

  • We are starting an huge upgrade project (high customized AX4 solution, 3000+users in 11 countries). Loosing the feature in D365 is definitly a 'No Go' regarding the effort of implementation of  'workaround's and coming problems during sync scenarios of shared data without this feature.     

  • Big concern for our ISV solution which offered a strong feature based on virtualisation. Have several customers sharing data, and not only master data, but also transaction data. Huge USP which made them select AX instead of other competitors! - Loosing this feature in D365 is a killer and we would need to do something by our own.

    Been in contact with MS product team about this for a while and got the reply that a "true data sharing" feature is on its way, but unfortunately only for master data. Will that be possible to enhance for us towards transaction data?