Forum Discussion
Populate lookup column in dynamics 365 ce
Hi,
I am using copy activity in fabrics pipeline . My source is fabrics warehouse , destination is dataverse . I am trying to populate column called fm_transaction in Transaction Line Item , which is related to Transaction table .
My query is :
Hi Shaxa ,
Thank you for reaching out to the Microsoft Fabric Community Forum.
We really apologies for the inconvenience, after reviewing the issue of the pipeline runs successfully but the lookup column in Dataverse is still empty, here are a few things worth double-checking:
In your mapping, there’s a small typo, it looks like you wrote fm_transction@EntityReference instead of fm_transaction@EntityReference. Just adding that missing “a” can make a difference, so be sure to correct it.In the reference string you’re building (e.g., /fm_transactions(GUID)), make sure the table name matches the actual plural name of the Dataverse table ,exactly as it appears in Dataverse, including casing.
Since you're already using the @EntityReference format, make sure the original fm_transaction GUID column isn’t included in the mapping. Having both can confuse Dataverse and prevent the lookup from being set.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
4 Replies
- v-menakakota
Community Support
Hi Shaxa ,
Thank you for reaching out to the Microsoft Fabric Community Forum.
We really apologies for the inconvenience, after reviewing the issue of the pipeline runs successfully but the lookup column in Dataverse is still empty, here are a few things worth double-checking:
In your mapping, there’s a small typo, it looks like you wrote fm_transction@EntityReference instead of fm_transaction@EntityReference. Just adding that missing “a” can make a difference, so be sure to correct it.In the reference string you’re building (e.g., /fm_transactions(GUID)), make sure the table name matches the actual plural name of the Dataverse table ,exactly as it appears in Dataverse, including casing.
Since you're already using the @EntityReference format, make sure the original fm_transaction GUID column isn’t included in the mapping. Having both can confuse Dataverse and prevent the lookup from being set.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.- v-menakakota
Community Support
Hi Shaxa ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you- v-menakakota
Community Support
Hi Shaxa ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.