An undeclared property '{attribute name}' which only has property annotations in the payload but no property value was found in the payload.

[zdeneksrejber]

Im having trouble with my CDS environment. We are using liquid maps and integration to populate attributes of an entity Waste Report Entry. The integration returns error that the field talxis_siteid doesnt exist for the entity in target environment.

message": "An error occurred while validating input parameters: Microsoft.OData.ODataException: An undeclared property 'talxis_siteid' 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.

When I check make.powerapps I actually cant see the attribute there, however when I try to create new one, I get notified that the logical name of the field already exists. When I call API for attributes of said entity I can see the talxis_siteid there. But integration doesnt see it.

mapping in liquid file:

"[email protected]": "{% cdslookup WZP_ContactAltAddress,talxis_sites %} {'Code' : '{{ Partner_Task_Site }}','Contact_No' : '{{ Partner_Reg_No }}'} {% endcdslookup %}",

screenshot result of api

I have the feeling of a broken environemnt...
Any ideas what to check or how to fix

[honzakostejn]

Hi, if you're using OData web api, be sure to send _talxis_siteid_value instead. That could solve your issue.

[hajekj]

Right now, we are aligning EDS with CDS Current Environment connector, so unless there is anything else specifically preventing us from using [email protected] notation, I would stick to it.

[TomProkop]

"only declared navigation properties can be represented as properties without values" sounds like it is not considered a navigation property and that is wrong

can be checked using /api/data/v9.2/$metadata if it is present there as a navigation property

[zdeneksrejber]

it is available through API call. I also tried to send there different data , eg. only guid and got different error
"CRM do not support direct update of Entity Reference properties, Use Navigation properties instead."
I think we should stick to odata bind

[TomProkop]

exactly I think your method doesn't work @honzakostejn I also had troubles with sending guids directly

[zdeneksrejber]

Whatever random characters I type instead of talxis_siteid, Im still getting the same error. So, I believe it really cant find the attribute in CDS. There is either something wrong with how I declared the attribute in the map or there is something wrong in the CDS

[TomProkop]

@zdeneksrejber can you please post entity.xml attribute?

[TomProkop]

the relationship was present in the solution.zip @honzakostejn

[zdeneksrejber]

we tried to change behaviour entity in solution.xml to 0, but it didnt help
I would love to set a deploy pipeline a deploy to new clean env, however there are open pull request and I need them merged first

[TomProkop]

@zdeneksrejber is there anything new?

[zdeneksrejber]

Resolved, plain and simple broken CDS environment. I am not sure why it broke, but the environemnt was used multiple people for dev purposed. After few days of making everything deployable through pipeline I finally managed to get everything on fresh environemnt with only managed components and now it works like a charm

Still not sure why the relationship was missing in the old environemnt though

[MaceWindu1]

I have the same issue again :(