Forum Discussion
Dynamics 365 connector not including column RegardingObjectTypeCode
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 ,
Thank you for the update,Please do keep us posted once you’ve had a chance to test with the appropriate permissions. We’d appreciate hearing if Synapse Link resolves the problem or if further assistance is needed.
Hi HelgeG ,
we wanted to follow up regarding your testing of Azure Synapse Link. Have you had a chance to set up the necessary permissions and conduct your tests?
We’re eager to hear if Synapse Link has resolved the issue you were facing or if you require any further assistance from our side.
Thank you, and we look forward to your update!
Hi HelgeG ,
Just following up on your testing of Azure Synapse Link. Were you able to set up the necessary permissions and complete your tests? We’d love to know if Synapse Link helped resolve the issue, or if there's anything else we can assist with.
If the provided solution worked for you, kindly consider marking it as the Accepted Answer. It not only closes the loop but also helps others in the community facing similar scenarios.
If you're still experiencing issues or need additional guidance, feel free to share more details we're here to help!
Please note, if we don’t hear back soon, we may close this thread in line with our community guidelines. But you're always welcome to post a new query anytime.
Thank you for being part of the Microsoft Fabric Community!
no, still waiting for IT to set up the permissions required.
Hi HelgeG
Thanks for the update, and no worries completely understand that internal setup processes can take some time.
Once you have the necessary permissions in place and get a chance to test Azure Synapse Link, feel free to share your findings here. We’ll be happy to assist further if any issues come up or if you need help interpreting the results.
In the meantime, if you have any other questions I can assist you with or if you have further questions.
Thanks again for being part of the Microsoft Fabric Community!
