Power Pages

Performance issue

(0) Share

Report

Posted on by PPEnthusiast

Hi all,

In power pages, I have 3 tables table a, table b& table c

I need to create few records in these 3 tables:

each A record has 41 B records

each B record has 26 C records

is there any way to create all these records in dataverse using web api with faster performance?

Is there any limit to make certain number of web api calls in power pages?

When using synchronous power pages cloud flow calling child flow to create B & C records, I am getting 504 time out gateway error on power pages end, is there any other alternate way for this?

What is the most feasible approach with good performance to create all A,B,C records or bulk data creation and updation in power pages?

Categories:

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Robert Bailey Upzoids 4 on at

Like (0)

Report
Copy link

Link copied!

hey PPEnthusiast (awesome name),

hitting a 504 from Power Pages/cloud flow is expected because the synchronous request is just doing too much work for a UI call. Don’t do heavy inserts in the page context. that's like over 1000 records unless i'm misunderstanding you? This is for a bulk async job to take care of. like power automate which you can call via API.

For super high throughput, use the bulk operation APIs (CreateMultiple, UpdateMultiple, etc.) — they’re designed for bulk loads and can outperform individual/batch calls. Again, is there a reason this needs to be synchronous??

Useful MS docs to bookmark:

• Batch Web API operations — https://learn.microsoft.com/power-apps/developer/data-platform/webapi/execute-batch-operations-using-web-api

• Bulk operation messages (CreateMultiple, etc.) — https://learn.microsoft.com/power-apps/developer/data-platform/bulk-operations

Was this reply helpful? Yes No
Suggested answer

Fubar 8,487 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

You may need to consider a different approach, why do you need to create so many associated records automatically?

Also you need to consider, once they are created do they need to be available immediately to the portal user, if so you will also need to consider the portals caching (as they would be considered secondary records and not automatically pushed into the portals cache on create).

If not needed immediately, consider writing a dataverse realtime plugin which can make use of dataversese batch operations like createMultiple - however this is still potentially risky as potentially your creation could exceed dataverses timeout limit.

Was this reply helpful? Yes No