I'm importing data from an on-premise SQL Server database into CDS via the on-premise gateway. I have already set up my CDS entities with alternate keys to allow relationships (lookups) to be maintained between the source and CDS when synchronizing. I seem to have a bug in my dataflow where it is trying to import to a destination field (alternate key on a related entity) that doesn't exist in the related entity. The error message in my dataflow refresh history detail is: "Missing destination field cr423_gradergrower.cr423_grader in the schema".
The destination field is automatically set to "cr423_GraderGrower.cr423_Grader" but I think it should be "cr423_GraderGrower.cr423_Grader.cr423_SerialNumber" because the "cr423_Grader" related entity has a key "cr423_SerialNumber". Is Dataflow able to use cascading (multi-level) alternate keys in this way, or should I try another way to ensure relational integrity?
Dataflows doesn't support multi-level alt keys and I don't even think it supports alt keys defined with >1 fields. Any chance you can modify your entity model to have a direct link to Grader? Another option is to have a new "staging" entity and use that as your destination entity, then with the help of Power Automate (or another preferred method), create the "real" entities. You can also leverage Power Automate as an alternative to Dataflows if Dataflows doesn't satisfy your requirements.
Hello, Ran into the same problem here with the following error:
Missing destination field cr915_category.cr915_name in the schema
The solution for us was as follows:
I have not seen this documented or answered anywhere online. Hope it helps
Greetings all. I was running into exactly this problem as well with a CDS custom table (Case) related to a CDS delivered table (Contacts) and HarryJohn's solution resolved it for me (thank you!). Now, however, when trying to import Note/Annotations associated with the Case, I get a similar error:
Missing destination field objectid.crf8b_legacycase in the schema
Below are screen shots of my data flow field mapping and the Connection Set Import Key pages respectively.
Any ideas? Thanks much!
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!