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:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Michael E. Gernaey 52,906 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
Suggested answer

VGKolar 16 on at

Like (0)

Report

Look up column saving as blank in Dataverse table

When a lookup column in Dataverse saves as blank, it usually means the lookup value was not provided in the exact format Dataverse expects. Dataverse will save all other fields but silently ignore a lookup if the reference is not valid.

You need to verify:
1. Schema name of the Lookup Field:
The left side must use the lookup field’s schema name, and it is case-sensitive:
sp_HotelCode@odata.bind

2. Correct Entity Set Name:
The value must point to the entity set name, not the logical name like "/sp_hotelses(<GUID>)"
Make sure sp_hotelses is the correct entity set name for your hotels table.

3. Valid GUID:
formData.hotelId must contain a valid Dataverse record ID with no braces and if the GUID is null, empty, or malformed, Dataverse will ignore the lookup.

4. proper OData binding format must be there Actually
"sp_HotelCode@odata.bind": "/sp_hotelses(Actual GUID)"

5. The lookup must be configured to point to the same table you are referencing.
6. The user/service principal must have:
7. Read access on the referenced table and create/Write on the target table, otherwise the lookup will save blank.
8. If you are patching from Power Apps, the lookup must be sent as an object:

sp_HotelCode: {
'@odata.type': "#Microsoft.Dynamics.CRM.sp_hotel",
sp_hotelid: formData.hotelId
}

Was this reply helpful? Yes No
CU04121923-1 2 on at

Like (0)

Report

Look up column saving as blank in Dataverse table

Thank you VGKolar & Michael for your responses.

The GUID does exist in the target table and here is what I see at runtime:

sp_HotelCode@odata.bind: "sp_hotelses(beef92ae-49c9-f011-bbd3-000d3a593608)"

I am using below to send my data and don't think the look up column should be passed as an object.

await dataApi.createRow("sp_event_set_up", payload);

Still not sure what's the reason the look up column not being saved.

Was this reply helpful? Yes No