Unanswered

Missing destination Field Data Integration

(0) Share

Report

Posted on by Community Power Pla...

I'm trying to load data to a entity with a refrence to another table. Both same datatype, when I want to load the data to the entity I get the next error.

Someone knows the cause of solution of it?

Error:

Load to Common Data Service failed. Details: ID: 4919f9ee-861b-4b29-ba11-6b3696f906b2: Missing destination field cr8ca_table.cr8ca_field in the schema. (Job ID: e33b0952-ede2-4b51-a2b4-8f3f3d70fb34)

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (18)

Answers (2)

v-xida-msft on at

Like (0)

Report

Hi @Anonymous,

How do you load data into a entity within your PowerApps?

Further, could you please share more details about your error message?

The error message seems to tell that there is something wrong within the Field Mapping part when you load data to a entity.

Please check if you have specified proper column of your source data source for the destination fields.

In addition, please also take a try to select "Load to new entity" option within the Load settings part when you load data into a entity, then check if the issue is solved.

If the issue still exists, please take a try to clear cache of your browser, then try it again to check if the issue is solved.

More details about loading data into CDS entity using Power Query, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-cds-newentity-pq

More details about importing data into CDS entity, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-import-export

Best regards,

Kris

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Kris,

I do indeed import the data to a custom entity.
The import has a lookup value to the Sales Invoice Header -> InvoiceID.
There is where the import is stuck.
The ID's are already imported in Sales Invoice Header so I don't know why I get this error.

If I load the data to a new Entity I will lose the link between the entities Sales Invoice Line - Sales Invoice Header.

Regards,

Sven

Was this reply helpful? Yes No
Sara Freitas 70 on at

Like (2)

Report

Hi,

I've this error too. I have created a data migration project and the entity migration fails with the same error.

Thank you

Was this reply helpful? Yes No
Loose Chippings 185 on at

Like (0)

Report

Hi

Has anyone found a solution to the error "missing destination field in the schema" when using data flow to load into lookup fields of custom entities.?

Was this reply helpful? Yes No
Drrickryp Super User 2024 Season 1 on at

Like (0)

Report

Hi @LooseChippings

My suggestion is to use the dynamics data import wizard. I have a post here with how to do it. https://powerusers.microsoft.com/t5/Building-Power-Apps/Update-on-importing-relational-data-into-CDS-entities/td-p/428792 . I have found it to be a much better alternative but it is not as well documented. It is available but you have to know how to find it.

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi @Anonymous,
My recommendation is to review you field data mapping of your Dataflow like @v-xida-msft mentioned.. Open you Dataflows, by clicking the ellipsis button on the right and click Edit

It will take you to the Power Query window, hit Next and make sure your mapping are correct. Click Next and Save (make sure you save!) and rerun your Dataflow but selecting Refresh.
Hope this helps!

Was this reply helpful? Yes No
Loose Chippings 185 on at

Like (0)

Report

Thank you, Drrickryp and Eric. We have used the dynamics import wizard to initially populate the entities. Now we are trying to create a real world business app where an administrator will enter 10-12 records per day. We have no problem entering data using canvas apps, model driven apps and Power Automate but we are trying (unsuccessfully) to create a dataflow with a daily scheduled refresh. Lookup fields are recognised in the OOTB Contact and Account entities but not custom entities.

May I ask if you have actually managed to achieve updating a custom entity lookup field using data flow? I'm beginning to think that it is just not possible at this time.

Was this reply helpful? Yes No
Joel CustomerEffective 3,224 on at

Like (0)

Report

Yes you can update a custom entity lookup field
1. create a flow in a solution
2. use the connector called common data service current environment
3. you need to have the iD of the record to put in the lookup field
4. to populate the lookup field you need to add the plural schema name of the entity and the guid for the record in parenthesis. See https://crmtipoftheday.com/1311/use-entity-name-in-flow-lookups/

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi @LooseChippings, Yes you can map custom lookup. The trick is to create an alternate key containing that lookup and the Field mapping will then recognize it (thanks @HSheild for the tip). If the lookup is not unique within the records, then add more fields to the key that can make it unique. Here's an example where the PreferredSystemUserId is a lookup:

Was this reply helpful? Yes No
Loose Chippings 185 on at

Like (1)

Report

Thank you @EricRegnier , @Drrickryp and @jlindstrom. My problem was not with alternative keys or other settings and I had already seen the @HSheild post. In fact, I do not know why the lookup fields were not recognised but I stumbled across a solution, so for anybody else searching for "missing destination field" error:

In the Power Platform admin center there is a section - Data Integration. We created a new Project, then a new Task. We were then able to map the alternate key in the parent entity (jgb_product_id) to the lookup field in the child entity (jgb_productlookup).
If I ever find out why the lookup fields were not found in the first place I will post the answer but I fear it may remain a mystery.

Was this reply helpful? Yes No