Share
Report
5Hello community!
I have what I would have thought would be a very simple challenge that maybe someone can help me with.
In a recent integration with a 3rd party tool we needed to provide WorkerContact->cdmemailaddress1 as part of a scheduled exported data set.
It turns out that by design (ticket 120031222001136||Powerapps) this field is not synchronised to CDS and MS have no plans to do so.
Seems surprising for such a basic field (and there are more), there does not seem to be an easy way to get this data into a PowerBI Data Flow, PowerQuery, ADF or CDS?
So then today I watch the wonderful presentation by Harsh Srivastava and Jared Hall https://mymbas.microsoft.com/sessions/6d9cd389-2809-4bc4-bf82-27cec8d7583b?source=sessions and I wonder exactly what I am missing in the roadmap? Should connecting this data to the CDS platform not be on the roadmap? Perhaps Virtual Entities solve our problem somehow, cannot see it.
I have reviewed the Dynamics Integration documentation https://docs.microsoft.com/en-us/dynamics365/human-resources/hr-admin-integration-choose-technology it is pretty vague but it looks like I have to build an Azure SQL Database (BYOD) at a substantial cost to the business in order to simply get 1 or 2 fields out of DMF Entities?
So my question is
1. Is there a recommended way to get cdm_emailaddress1 into CDS other than buy a SQL Database / BYOD?
2. Can this entity/field be retrieved via the OData REST API https://docs.microsoft.com/en-gb/dynamics365/fin-ops-core/dev-itpro/data-entities/odata
3. Is there a list of Entities that can be accessed by the OData REST API
4. Will custom added fields be exposed in the REST API JSON object?
5. In the MBAS2020 presentation a move away from BYOD to Azure Data Lake is suggested, will this let me extract fields and entities (like Benefits) that are not synchronised to CDS/CDM?
Ideally we want to pull all data out using ADF (& CDS PowerBI)
Thanks,
Tom Deloford
All responses (
Answers (
