Forum Discussion
Dynamics 365 connector not including column RegardingObjectTypeCode
- 1 year ago
Hi HelgeG ,
Thanks for sharing the screenshot. Based on the your query, try below recommendation steps :
- If you're not seeing the RegardingObjectTypeCode in your query results, it might be due to limitations in how the connector is designed some connectors don’t expose certain fields by default, especially if they're not directly part of the main entity.
- As you noted, applying filters for specific RegardingObjectTypeCode values leads to repetitive logic, which isn’t an efficient or scalable solution. This is a common challenge when working with connectors or APIs that don’t fully expose all required metadata fields.
- If you're considering Azure Synapse Link, it's worth testing first it writes data to your data lake in near real-time and usually includes all fields, including RegardingObjectTypeCode, which the connector currently misses. It could solve your issue without needing complex workarounds.
If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily.
If you continue to face issues, feel free to reach out to us for further assistance!
Hi HelgeG ,
Thanks for sharing the screenshot. Based on the your query, try below recommendation steps :
- If you're not seeing the RegardingObjectTypeCode in your query results, it might be due to limitations in how the connector is designed some connectors don’t expose certain fields by default, especially if they're not directly part of the main entity.
- As you noted, applying filters for specific RegardingObjectTypeCode values leads to repetitive logic, which isn’t an efficient or scalable solution. This is a common challenge when working with connectors or APIs that don’t fully expose all required metadata fields.
- If you're considering Azure Synapse Link, it's worth testing first it writes data to your data lake in near real-time and usually includes all fields, including RegardingObjectTypeCode, which the connector currently misses. It could solve your issue without needing complex workarounds.
If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily.
If you continue to face issues, feel free to reach out to us for further assistance!
I can confirm now that Azure Synapse Link is writing data for RegardingObjectTypeCode. Haven't tested other similar columns, but this seems to be the solution.