Web API function issue on custom tables

(1) Share

Report

Posted on by powerdevkris

159 Season of Giving Solutions 2025

Hi,

I was trying to add records in dataverse using the web api functions. I followed the steps in the MS document that use the account table and manage to make it work. Though when trying to do the same steps for my custom table. Cannot seem to make it work.

Created both site settings.

Webapi/<<table name>>/enabled

Webapi/<<table name>>/fields

for the table name section, i have tried both logical name and plural name as well to see if that is the issue.

Created a table permission with Global access and even enabled all access type. Create and Read. All web roles are added as well.

Doing URL check to see if its working test.powerappsportals.com/_api/<<table plural name>>

Not sure what i am missing to make it work.

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Vahid Ghafarpour 817 on at

Like (2)

Report
Copy link

Link copied!

For the Web API endpoint, make sure you're using the plural name of the custom table (in site settings too), not the logical or schema name. This is case-sensitive and must match exactly what’s defined in Dataverse.

Was this reply helpful? Yes No
Suggested answer

Fubar 8,501 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

It would be more informative if you included the actual values you are using, and also tell us what error message you are receiving.

The Site Settings should be the logical name values (will be all lower case, and as a custom table will also include the prefix e.g. new_mynewtable ),

For your fields list Site Setting, initially set its value to an asterisk * (once working, set it to the specific fields comma separated)

Your API call should use the Set Name (often this is the plural name, but technically can be different)

You can copy the values from Dataverse

https://learn.microsoft.com/en-us/power-pages/configure/web-api-overview

Also note, after making changes to Site Settings you may need to clear/purge the Portals cache for them to take affect (under the 3 dots next to your site in the admin portal)

https://admin.powerplatform.microsoft.com/manage/portals

Was this reply helpful? Yes No

Use Browser Dev Tools

Open the browser’s Network tab and inspect the request/response when calling the API. It often gives clues like:

"Permission denied"
"Entity not found"
"Field not exposed"

Here are common pitfalls to double check:

Symptom	Likely Issue
403 Forbidden	Missing web role or table permission
401 Unauthorized	User not authenticated and anonymous not allowed
404 Not Found	Incorrect plural name or table not exposed
Error message about field	Field not in allowed fields site setting
Silent fail	Browser blocks POST due to missing headers or CSP