Issue while inserting Contact lookup value (server-side logic create record)

(0) Share

Report

Posted on by CU16041033-0

I have created a custom table named dev_application, which includes a Contact lookup field (dev_applicationcreatedby).

When I try to create a record using server-side logic and include a value for this Contact lookup field, the request fails with an error from Dataverse. However, the record is created successfully when I exclude the lookup field. If I remove the lookup field from the payload, everything works as expected. I have verified that the current user ID exists in the Contact table. I have also assigned all required table permissions to the authenticated user web role.

Could someone please help me understand what might be wrong with the lookup configuration or payload format? Any guidance would be greatly appreciated.

function post() {
    try {
        Server.Logger.Log("POST called");
        const data = JSON.parse(Server.Context.Body);
        const entitySetName = Server.Context.QueryParameters["entitySetName"];
        var userid = Server.User.contactid;
        data["dev_applicationcreatedby@odata.bind"] =  `/contacts(${userid})`
        return Server.Connector.Dataverse.CreateRecord(entitySetName, JSON.stringify(data));       
    } catch (err) {
        Server.Logger.Error("POST failed: " + err.message);
        return JSON.stringify({ status: "error", method: "POST", message: err });
    }
}

Categories:

Power Apps portals

Design & build

Security

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Assisted by AI

Vish WR 1,045 on at

Like (0)

Report
Copy link

Link copied!

@CU16041033-0

Your issue is most likely caused by how the Contact lookup is being referenced in the Dataverse payload.

Key points:

* Ensure the lookup format is correct: /contacts(GUID) with no braces.

* Verify dev_applicationcreatedby is the correct lookup schema (navigation property), not just the display or column name.

* Confirm table permissions for Contact include at least Read access for the portal user.

* Ensure entitySetName is the correct Dataverse entity set name

Most common root cause: incorrect user/contact ID or wrong lookup binding format.

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
Suggested answer

rezarizvii 333 on at

Like (0)

Report
Copy link

Link copied!
Hi @Vish WR, if you are going to post generic AI-generated answers, please ensure to tag your messages as "AI-assisted" properly to ensure clarity in the forum. OP could easily ask any LLM to get the same generic and vague response.

Hi @CU16041033-0, hope you are doing well.

If you have verified the table permissions, assigned them to the authenticated users web role, and ensured the GUID exists in the contact table, it seems the error is caused by the syntax of your OData bind. According to Microsoft, the name of the field that should appear before the '@odata.bind' is supposed to be the Navigation Property Name, NOT the field's logical name [Reference from MS Learn]. It seems you are using the logical name of the lookup field to make the OData bind.

Here's how to confirm the navigation property name of the lookup field:

Go to this URL: https://[your-org-URL]/api/data/v9.2/$metadata
You can also find this URL by going to Settings and then Developer resources. Just make sure to append /$metadata at the end of the Web API endpoint.

Use "Ctrl + F" on Windows (or the equivalent shortcut to search in the page on Mac) and look for the lookup column you wish to bind. In your case: dev_applicationcreatedby

Use the Navigation Property Name you find there as is in your code. Remember, it is case sensitive, so you should copy it as you see on the /$metadata page.
It should be in this format: data["<Case-Sensitive-Navigation-Property-Name>@odata.bind"] = `/contacts(${userid})`

Here is the reference to the guide you can follow: Set Lookup field using Xrm.Web API JavaScript in dataverse power apps | Softchief Learn

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like! 🩷

_______________________________

Reza M. Rizvi
LinkedIn | Email

Was this reply helpful? Yes No
Suggested answer

11manish 1,381 on at

Like (0)

Report
Copy link

Link copied!
The issue is most likely caused by either incorrect navigation property name or missing table permissions on the Contact table. Even though the record exists, Dataverse (especially via Power Pages) requires proper read access and correct relationship binding for lookup fields to work.

try below code :

function post() { try { Server.Logger.Log("POST called"); const data = JSON.parse(Server.Context.Body); const entitySetName = Server.Context.QueryParameters["entitySetName"]; var userid = Server.User.contactid?.replace(/[{}]/g, ""); if (userid) { data["dev_applicationcreatedby@odata.bind"] = `/contacts(${userid})`; } return Server.Connector.Dataverse.CreateRecord(entitySetName, JSON.stringify(data)); } catch (err) { Server.Logger.Error("POST failed: " + err.message); return JSON.stringify({ status: "error", method: "POST", message: err }); } }

Was this reply helpful? Yes No