Associating entities using Web API fails in portal

(0) Share

Report

Posted on by Abhishek0672

Hi,

I am trying to associate two items using Web API call, an N to N relationship exists between the tables.

The 1st entity has unique identifier as entity1id and entity2 has one as entity2id. Both these fields are text type.

The entity permissions are in place and site setting is also set for both the entities.

Still the API call fails with a 404 Not Found status code.

The ajax call I am using is:-

webapi.safeAjax({

type: 'POST',

url: '/_api/entity1('+entity1id +')/<relationshipname>/$ref',

contentType: 'application/json',

data: JSON.stringify({

'@odata.entity2id': '/entity2(' + entity2id + ')'

}),

success: function () {

console.log('success');

error: function () {

console.error('Error associating');

}

Categories:

Power Apps portals

I have the same question (0)

All responses (5)

Answers (0)

Sort by

oliver.rodrigues 9,455 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!
Hi

a few things to check:
have you double checked your Portals version? has to be 9.2.6.41 or higher
is your "entity1" the entity set instead of entity name.. for example contacts instead of contact ?

------------
If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Was this reply helpful? Yes No
Abhishek0672 2 on at

Like (0)

Report
Copy link

Link copied!

Hi Oliver,
Thank you for your response. My portal version is higher than required.
I was missing the entity set name on one of the entities. But now after correcting that, I'm getting a different error: "Attribute <relationship name> cannot be found for entity entity1"

Was this reply helpful? Yes No
Ulrikke Akerbaek 101 on at

Like (0)

Report
Copy link

Link copied!

I am attempting to do the same, and having trouble finding the correct entity set name. How would I go about finding it without writing code?

Have you made sure to add Site Settings "Webapi/[entity]/fields" to "*" or including the missing field in the list?

I wonder, @Abhishek0672, have you added webapi site settings for the N:N entity?

Was this reply helpful? Yes No
oliver.rodrigues 9,455 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@Abhishek0672

were you able to get this working? have you tried @UlrikkeAkerbæk suggestion on adding the * for all attributes

also make sure you have both site settings and entity permissions for every entity you are performing operations with the API

Was this reply helpful? Yes No
Ulrikke Akerbaek 101 on at

Like (0)

Report
Copy link

Link copied!

@OliverRodrigues can you please elaborate a bit more around the Entity Permissions needed for API to work? Does it have to be global permissions? Do I need only "Write" to "POST", "Update" to "PATCH" and "PUT" and "Delete" to "DELETE"?
And is it important that the function calling the API is located at home "/" page - or can this be triggered from any page in the site map?
I am new to working with API's and don't get it quite yet. So - of course I started with N:N relationship deep in my entity permission structure. *Rolling my eyes to myself*
Thank you for helping me out.

Was this reply helpful? Yes No