web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Pages / how to associate optio...
Power Pages
Unanswered

how to associate option sets using portal Web AP insert (post)I?

(0) ShareShare
ReportReport
Posted on by 20

Dear experts?

 

I am adding new record using Power App portals Web API post option, does not seem to work and gives error:
Error: Resource not found for the segment br_prance.

I have a field called br_type which is an option set has value as below:
717750000 - Alpha

717750001 - Beta

I need to add a new record via portal web API -
Here is the complete json
{
"br_type": "717750001",
"br_name": "Prev 1",
"br_iscancelled": "TRUE",
"wr_MemberId@odata.bind": "/contacts(6f1a341c-8097-eb11-b1ac-000d3aafa583)",
"wr_CustomerId@odata.bind": "/contacts(6f1a341c-8097-eb11-b1ac-000d3aafa583)"
}

 

Please if someone can help, how you can assign option sets while adding a new record via portal, is this the wrong way?

Categories:
I have the same question (0)
  • jimmymcad Profile Picture
    20 on at

    I managed to fix the first issue - It was something different
    Now I am getting another error - Slowly after removing every field - I found the issue is on this one:
    "wr_CustomerId@odata.bind": "/contacts(6f1a341c-8097-eb11-b1ac-000d3aafa583)"

     

    This time the error is 
    Error: Common Data Service error occurred.

     

    Further digging reveals that this field is locked on CRM forum? Could this be an issue? Can we not add values to a read only field?

    Please confirm, or else how do I add this?

  • Fubar Profile Picture
    8,505 Super User 2026 Season 1 on at

    With some of the Web Api errors I have found more info by F12 the browser and look at the web traffic for the call that gives the error (i.e. the error response from the call sometimes has more info than what you originally see in the JS error or console).

     

    Edit: and the "77..." in the JSON should probably be without quotes

     

    If its a field/relationship issue you can try putting an asterisk * in the field list in your site settings instead of listing the fields (and if that works then you know its an incorrect field name reference).

     

    From memory, if its a customer look up its something like the relationship name e.g. /myfield_contacts(…..)

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Pages

#1
11manish Profile Picture

11manish 50

#2
Valantis Profile Picture

Valantis 26

#3
omkarsupreme Profile Picture

omkarsupreme 24

Last 30 days Overall leaderboard