Share via

Support OData Enumerator Custom Fields

Brent Reffner 31 Reputation points
2021-07-07T19:55:39.65+00:00

Neither the Dynamics AX nor OData connector can retrieve a custom entity that is defined as an enumerator data type. The preview operation within ADF retrieves other standard fields that are defined as enumerator (it translates those fields automatically) except custom defined entities. Power BI's OData connector oddly enough works. It has no trouble bringing in a custom entity and doing the translation. This tells me that the Power BI team has figured out how to do this but the ADF team has not.

Is there a workaround for this that does not require a redesign of the custom entity?

Azure Data Factory
Azure Data Factory

An Azure service for ingesting, preparing, and transforming data at scale.

{count} votes

2 answers

Sort by: Most helpful
  1. Brent Reffner 31 Reputation points
    2021-07-12T13:19:18.34+00:00

    I did get a response from your Microsoft colleague with steps to remediate the issue. By modifying the JSON, we can get the custom object to come through. This would be a great property to add to the Dynamics AX connector rather than go through JSON but I am pleased the workaround works.

    =================

    In your initial description you have stated you're unable to see the custom enumeration field when you're connecting using ODATA Connector. Can you kindly add this property to your Copy Activity JSON

    1. Add following property to json payload of Dataset / Copy activity.
      retrieveEnumValuesAsString: true

    If you want this feature on Dataset, put the property in Dataset JSON. Path: root.properties.typeProperties

    If you only want this feature in a particular copy activity, put the property in Copy Activity JSON. Path: root.properties.activities.typeProperties

    113884-pic1.png

    Let me know if this is helpful.

    6 people found this answer helpful.

  2. Divya Rai 1 Reputation point
    2023-01-09T05:04:31.04+00:00

    In my case since Dynamics Connector for Odata didn't work for enum fields, so I used RESTService as datasource and it worked. You just need to take care of paging and dynamically creating the urls.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.