Forum Discussion
Mapping a dataverse lookup column in a pipeline data copy activity
Hello everyone
I'm trying to map a dataverse lookup column in a pipeline data copy activity. Kind of like how it is explained in this youtube video:
https://www.youtube.com/watch?v=m24yu-dwK8Q
Except for that I'm trying to use a pipeline data copy activity instead of a power platform dataflow. I've tried it in a dataflow and that seems to work but those can not be integrated with Fabric pipelines. And I need it to be in a pipeline because that one is supported in a Fabric deployment pipeline.
So in my Fabric pipeline activity it looks like:
But then I get this error:
Error
Operation on target Copy_oml_eenheid failed: ErrorCode=DynamicsOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Dynamics operation failed with error code: -2147217149, error message: 'oml_eenheid' entity doesn't contain attribute with Name = 'oml_complex.oml_complexnummer' and NameMapping = 'Logical'..,Source=Microsoft.DataTransfer.ClientLibrary.DynamicsPlugin,''Type=System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]],Message=The creator of this fault did not specify a Reason.,Source=Microsoft.DataTransfer.ClientLibrary.DynamicsPlugin,'
And in my Power Platform dataflow it looks like this:
And that just works. So I'm guessing I need to insert something else than 'oml_complex.oml_complexnummer' but I'm not sure what.
I could use some help so thank you kindly in advance.
Hi dibeau
The internal team replied as follows:
For the pipeline copy - in addition to mapping the related record's guid to the lookup field - also add a second value to the source query that has the lookup field's associated entity name (e.g. 'contact' or 'incident' or 'my_customentity') Map this new entity string to the mapping by adding a custom destination field with the name of the lookup field + '@EntityReference".
In this example I'm passing the parentcustomerid guid to the parentcustomerid in the destination AND I'm also passing 'account' over as the parentcustomerid@EntityReference to identify the related record type.
Hope this helps. Please let me know if you have any further questions.Hi dibeau
You can refer to this video Fabric Pipelines for Dataverse Part 5: Populate the Lookups (youtube.com)
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Otherwise, will respond back with the more details and we will try to help.
Thanks
10 Replies
Hi dibeau
Thanks for using Fabric Community.
At this time, we are reaching out to the internal team to get some help on this. We will update you once we hear back from them.
ThanksHi dibeau
The internal team replied as follows:
For the pipeline copy - in addition to mapping the related record's guid to the lookup field - also add a second value to the source query that has the lookup field's associated entity name (e.g. 'contact' or 'incident' or 'my_customentity') Map this new entity string to the mapping by adding a custom destination field with the name of the lookup field + '@EntityReference".
In this example I'm passing the parentcustomerid guid to the parentcustomerid in the destination AND I'm also passing 'account' over as the parentcustomerid@EntityReference to identify the related record type.
Hope this helps. Please let me know if you have any further questions.Hi Anonymous
I'm not quite sure what this means. My source (Lakehouse delta table) does not have a GUID. Does that mean I need to add a column with GUIDs? If I just try to replicate what the internal team showed I get the following error:
Operation on target Copy_oml_eenheid failed: ErrorCode=ParquetColumnNotFound,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Column complexnummer@EntityReference does not exist in Parquet file.,Source=Microsoft.DataTransfer.Richfile.ParquetTransferPlugin,'
Kind regards
