Connector Improvement: Microsoft Dynamics 365 CRM - Include Formatted Values
AnsweredInstead of depending on StringMap and intense transformation logic to surface the useful values for the large amount of option sets and status fields across entities, please provide the formatted values for included columns. This doesn't require transformations in the Fivetran pipeline. Instead, it can request the values be explicitly included in response to the calls to the Dynamics REST API that Fivetran is already making. You just need to include the below or something similar in the calls. We've long used this in our on-prem sync from Dynamics CRM, and it works very well.
Prefer: odata.include-annotations="OData.Community.Display.V1.FormattedValue"
https://learn.microsoft.com/en-us/odata/webapi/include-annotations
-
Official comment
Hi Jeff,
Thanks for submitting this request. The reason we don't pull the formatted values (human-readable labels) directly is that we are not able to capture incremental updates when they change. Applying transformations allows us to guarantee data integrity of those formatted values. However, we're aware that our current suggestion of applying these transformations yourself is a lot of overhead, so we're developing a solution that uses our Quickstart models to do these transformations for you - and they can be set up with just the click of a button. We're in Beta with the models now, so we only have several available (listed in our Quickstart documentation here), but we're working on getting a solution out that will create these models for every entity you're using Fivetran to sync.
Would love to hear your thoughts/feedback on this and I'd encourage you to try the models out! Feel free to reach out to your account team or to me here with questions.
Best,
Sadie
-
For reference, this is the exact header parameter we're using.
'Prefer': 'odata.maxpagesize=500, odata.include-annotations="OData.Community.Display.V1.FormattedValue,Microsoft.Dynamics.CRM.associatednavigationproperty,Microsoft.Dynamics.CRM.lookuplogicalname"'
Please sign in to leave a comment.
Comments
2 comments