Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Above is a configuration that I wish to implement. The three companies are legal entities, with company one being a NON-TRADING holding company. Only the other two companies trade and they are completely independent companies.
However, the trading companies have exactly the same clients and more or less the same suppliers. I would like them to access and transact with the same clients database and suppliers database. Will this possible with a single AOS and a single partition?
I am assessing Dynamics AX2012 R3.
I think you can achieve that by using table collection and create virtual company that hold those three companies and assign the table collection that has the CustTable and VendTable to it, for more details please check the link below.
Like Bilal mentioned you can achieve it using the table collection and virtual companies.
Note that there are multiple setup tables like customer group, payment terms etc. So these settings are the same for al legal entities.
Also note that the financial dimensions setup (and account structures) needs to be the same within all these companies as there is only one default dimension per customer of vendor.
Have a look at my blog post for some considerations: www.kaya-consulting.com/to-share-or-not-to-share
In fact there can be a link between all these customers and vendors by using the global address book.
Note that AX 2012 R3 has an option to replicate data using Master Data Services. So you can copy the customers/vendors and have per legal entity own company specific settings for e.g. payment terms, bank accounts etc. etc.
Andre, you raised a very important point that I had not considered. And it turns out that what I really want the companies to share is just demographic data of the customers and suppliers. By this I mean names, IDs, addresses, phone numbers, contacts, etc of the customers and suppliers.
Financial data (transactions and terms) will not be shared by the customers. However, the holding company will want to have consolidated CRM, financial and service information.
What I am not sure of is who will be responsible for creating and maintaining the demographic data, seeing that it belongs to no company.
Will this be possible?
After reading your blog post I got really discouraged. But then I bumped into this technet.microsoft.com/.../jj556270.aspx and to the un-initiated like me, it sounds very feasible. What is your expert opinion. Sharing CRM and Financial information between two legal entities is what we expect Dynamics to do. It's unavailability is a potential deal breaker.
With the menu path Home > Area page > Global address book, you can maintain the demographic data. This has no financial information like bank account numbers or other default values for the purpose of creating customers or vendors.
If you can also share ALL your financial data and settings on the customer or vendor, you can use the guidance of the Virtual company scenarios page. The list of tables shows you which options also needs to be shared. So these values are the same for a shared customer or vendor.
If there are some fields which needs to be setup different per legal entity, you have to decide not to share or create a customization where in a sepate table you can store some values per legal entity. You also have to change some logic in several processes to take the value from the new table in case there is a different setup per company.
Thanks Andre. I will settle for the Global address book for now.
Will the holding company have a consolidated view of CRM information, like pipeline analysis?
Business Applications communities