Dataverse Web API Calls in power apps portals

[IrfanMukhtiar]

Hi,
I am trying to get records from contact table using WEB API in PowerApps Portal. I am able to Call API/get records with liquid, but not able to get records using JavaScript. 

In javascript, My fetch is having 2 entities (contact and one other entity). 

I have added 

1- Table permissions for both entities and added link entity as 'child table permissions'

2- added site settings for both of the entities

While doing APICall, I am using "contacts" as entity name. 

But getting the 404 error:

Any help will be highly appreciated. 

Thanks

@ragavanrajan and all others. 

[ryanspain]

Hey,

I can think of 3 things you could check with your portal setup on this:

1. Do you have a Web Role associated with the Table Permission? Make sure it's a role the logged in user will have when the JavaScript is being invoked. i.e. Authenticated User.
2. Is your portal version 9.4.1.x or higher? This is the version where read operations became generally available I believe.
3. Are you sure you can pass in Fetch XML into the portals Web API? I've not seen that approach as of yet.

As a side note, I'd recommend not having a Global scoped Table Permission on the contact table unless access to that Table Permission was guarded by a Web Role only a few portal users wil have. That is, a few portal users that need access to the entire contact table.

Hope this helped.

[IrfanMukhtiar]

Hi @ryanspain 
Thanks for your feedback. 

1- Yes I have associate Web-Roles (authenticated and administrator) with the table permissions, and I have make sure that login user have these roles (Check contacts against web role as well check website where I am working)

2- Yes my portal version is higher then 9.4.1, meanwhile I have added 'Read permissions too'. 

3- Yes, I am already using Fetch and base on fetch making API-call to retrieve data from fetch. But here in this scenario I am facing issue. 

Thanks. 

[ryanspain]

Hey @IrfanMukhtiar,

According to the documentation, you can expect a 404 response code when the resource doesn't exist. That is,when the table isn't exposed for the Web API.

Based on this, let's check a few things:

1. Are the relevant site settings both Active and associated to the correct Website record?

2. I see you are using "True" in the site settings, could you try "true" instead (long shot!)?

3. I'm extension to the above, check to see there is no white space in the site setting values!

4. Could you try enable inner errors per this doc and check the response from the API for a specific message?

Hope this helps. Let us know.