question

BrentReffner-2688 avatar image
0 Votes"
BrentReffner-2688 asked DivyaRai-3693 commented

Support OData Enumerator Custom Fields

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
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @BrentReffner-2688 and welcome to Microsoft Q&A.

I am forwarding your ask to the product group.

ADF has internal data type mappings. You mentioned that standard enumerator are translated automatically. I suspect the limititation has to do with knowing how to translate. What makes a custom entity different? Is it not mappable to the standard types?

0 Votes 0 ·

1 Answer

BrentReffner-2688 avatar image
1 Vote"
BrentReffner-2688 answered DivyaRai-3693 commented

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.





pic1.png (62.5 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for sharing the work-around. To help preserve privacy, I will remove the contact information from your post.

0 Votes 0 ·
DivyaRai-3693 avatar image DivyaRai-3693 MartinJaffer-MSFT ·

Does this option work for everyone? I have seen similar forums where it is said that it has to be activated from backend. I am using Dynamics AX Connector to connect with D365FO. And for me the same thing is happening where some of the attributes(enum types) are skipped in ADF Copy, whereas they are available in the ODATA url using postman or browser.

0 Votes 0 ·