Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
We are kicking off an integration that will need to write to more than one company.
I have done a few integrations, but it has always been company specific.
Does anyone have some experience with this? A few comments on how the cross-company fact will influence the integration will be invaluable.
My first concern/hurdle is the service account. I assume there will need to be a service account for each company? And as you can't use the ClientId (ApplicationId) twice, there will need to be app registrations for each company as well?
I am planning on using OData, but I am unsure - as far as I know AX OData is not able to write to a company other than the one the service account is in. With service account I mean a record on the "Azure Active Directory Applications" form (SysAADClientTable).
Thanks for reading
As far as I know, with OData you can only write to the default company of the user account that you are using.
I've seen a trick where the default company is changed before the OData call, to direct the call to the correct company, and then switched back. But I don't recommend this for real life scenarios.
If you are willing to use data packages API, you can just set up data management projects for each company, and submit the packages to the corresponding APIs.
Using recurring integration API or data package API is good approach for such a requirement. You just need one client ID for it . Just create single data project and enable recurring integration for that data project . When you go to sys admin workspace and open your data project using data management IT tile , there is a check box called "Use company from message", so you are going to send company when you hit the endpoint. Records are going to be processed in the company you send from your message.
for example -
Refer - docs.microsoft.com/.../recurring-integrations
I am using it and writing data to multiple companies by enabling it with single integration batch job. It will be your best option to write data across companies.
Thank you all.
I have done some research on the Data Packages API. It looks like the way to go!
For interest sake: During my research I have found a decent way to post cross-company using OData.
But you have to create a custom entity.
Then we can patch and post cross company.
Business Applications communities