Forum Discussion
Writing data to a lookup field via alternative keys
Hi Folks, I have 2 table, 1. Contact with a secondary key 2. Policyholder with a lookup field to contact and a column that contain the contact secondary key guid as a string ...
A year later, and I still find no solution to this. If I do it in a data flow, per the article above, I get the following. (FYI, xxx is the first part of the lookuptable@keycolumnvalue as described in the original question)
An undeclared property 'xxx' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties without values.
If I try to do it in a copy data activity, I get the same error as above. I've tried lookuptable/keycolumn, lookuptable@keycolumn, lookuptable/keyname, and lookuptable@keyname, to no avail.
An undeclared property 'xxx' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties without values.
If I try to do it in a copy data activity, I get the same error as above. I've tried lookuptable/keycolumn, lookuptable@keycolumn, lookuptable/keyname, and lookuptable@keyname, to no avail.
Hi Randy
Did you ever manage to get it to work? I'm trying to do the same thing using a copy data activity in Synapse and wondered if anyone had found a solution yet.
