Hi,
I have a form with some data that I want to be shared with other companies..do I need to change the property save data per company for all the tables used in the form or jus change the cross company auto query on one of the datasources in the from?
And what's the difference between the two properties?
Also if I have other tables that are joind with these tabels but are not inside the form..do I need to change the save data per company as well even if I don't want them to be shared?
Do you consider the OOB feature to setup the cross company data for sharing?
The SaveDataPerCompany property is for table,and when you have other tables that are joind with these tabels but are not inside the form and do not want to share,you can consider to swap the table position to be Non-root data source.
The AllowCrossCompany property is for view.The detailed comparison between them you may refer to the blow link:
Cross-company behavior of data entities - Finance & Operations | Dynamics 365 | Microsoft Docs
There is a huge difference. You need to decide whether you want to have a separate configuration in each company, or you want to a single setup shared by all companies.
Hi Martin,
I want a single setup for all companies so can you please help
Hi Judy,
I'm dealing with forms and tables and not views.
And the form doesn't contain tables that I don't want to share. But I mean in general there are other tables that have relations with these tables that I want to share so I'm asking if this is ok.
If you want a single shared setup, than you need a table shared across companies, i.e. with Save Data Per Company = No.
You can have other tables with reference to shared tables. But shared tables can't simply refer to tables that saves data per company. If such a reference is needed, the shared table must store not just a reference to a key, but the data area ID where this key can be found.
If I make them shared..does that mean I'm forced to delete the data in live in these tables and insert them again? Because in my dev machine I had to delete old data in order to sync properly
Yes, you would have to. A better approach to such a significant change in your data model may be creating a new table, deploying it to production and copy data from one table to another. You may also need a process for dealing with data conflicts. You'd delete the old table in the next deployment.
Hi Martin.. but I made another two tables shared(not related to those) and I didn't have to delete the data inside... It was a parent table and a child table...Is deleting data related to if the table has multiple relations or not?.
Imagine that you have data in company ABC. Then you make the table shared, which means that all data is stored in company DAT. I believe that the data with DataAreaId = ABC will stay there, but won't be accessible, because such records makes no sense for shared tables.
Try it and see what happens with DataAreaId.
I know that the data area id field is deleted from all tables so I think it's not in DAT either and the data can be seen from any legal entity...but I don't get it why I had to delete the data in some cases and when I made other tables shared I didn't face the issue
Ah, sorry, ignore me. I was thinking about virtual companies...
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
CA Neeraj Kumar 1,841
André Arnaud de Cal... 783 Super User 2025 Season 2
Sohaib Cheema 490 User Group Leader
