Dynamics Community Forum Thread Details

Multicompany combined with track-changes

Hi,

For our BI-solution, where using an architecture combination of Azure Data Factory, Azure Databricks and Power BI, to combine data from various sources.

We're running into a paradox in regards to Incremental dataload from Dynamics 365 F&O with multiple companies (dataAreaid's).

Scenario:

Full load is successfull via ADF linked services (oData as well as REST API), with cross-company=true enabled.

However, for some entities (f.e. saleslinebientities) we want to load the data incrementally instead of full load.

For the incremental part the solution we found is odata.track-changes. We use the REST API linked service connector and we're getting a positive response with a deltaLink.

The paradox:

We've got multiple companies (dataAreaid's), so cross-company=true should be enabled to load the data of all our companies. However odata.track-changes is not supported when using cross-company=true. 'Hey then we just put a dynamic dataAreaid's filter and loop through each of our dataAreaid's, issue solved, right?' - No, because $filter is not supported in combination with odata.track-changes.

Anyone having a solution for extracting multicompany data from Dynamics 365 F&O incrementally, keeping our architecture in mind?

Thanks a lot in advance!

Categories:

Dynamics 365 Finance

Hi -- given that the user that is running the query has a default company, I am assuming that when you run with odata.track-changes, you are indeed getting results for that company.

If so, then these might be options:
1. depending on how many companies you have, you could set up multiple users, one for each company, and operate them as service accounts basically.

2. if not, so if you can only have 1 user, then you could use your favorite automation, a flow or logic app, that first sets the default company of the user, and then makes the incremental extractions...rinse and repeat. But caution here would be if that same user account is involved in any other automations, you would want to be careful about any such changes to the default company if that could impact any other batches/automations.

If you are able, you may also be able to leverage virtual entities...if you enable saleslinebientity as a virtual entity, and then access via the dataverse connection and/or dataverse odata endpoint, the I believe it is no longer as bound to company/dataarea when reading. But, virtual entities might have slightly different structure, or the fields might be named with an "mserp_" prefix, so you may have to refine any output you get that way.

good luck

-tim

Quick Links