Look up column saving as blank in Dataverse table

(0) Share

Report

Posted on by CU04121923-1

I am trying to save an entity in Dataverse table that has a look up column in it. All the fields are getting saved except the look up column. Below is the syntax I am using to save it:

"sp_HotelCode@odata.bind": `/sp_hotelses(${formData.hotelId})`

I have already made sure below things:

sp_HotelCode is the schema name for the column in Dataverse and I am aware that this name is case sensitive.
sp_hotelses is the entity set name for the table with which the look up column has relationship with.
formData.hotelId contains the GUID which is the primary key in the Hotels table (sp_hotelses).
Correct relationship is also established between two tables in Dataverse.

Is there sonmething else that I am missing because of which the look up column is saved blank.

Categories:

General Questions

I have the same question (0)

All responses (1)

Answers (0)

Michael E. Gernaey 52,851 Super User 2025 Season 2 on at

Like (0)

Report
Look up column saving as blank in Dataverse table

Hello @CU04121923-1

If its not being set, then verify the GUID you are putting in by looking at your code or the flow.

/sp_hotelses(formData.hotelId)

The above is the correct syntax assuming sp_hotelses is the correct spelling etc and is the pural

And as long as hotelId is a Guid

Then you should grab the guid and then manually go into the Table (sp_hotelses) and verify such a GUID exists.

I am betting it does not, so it makes it blank in your parent table you are inserting into

Was this reply helpful? Yes No