Power Platform Community Forum Thread Details

All of my apps rely heavily on sql reading and writing and speed for the user is very slow if using offline capabilities is very slow when patching through a gateway.

I'm writing this to give some quick tips on how to handle this and improve (massively) the speed of your apps.

Reading Data:
If you have to perform filters on big tables this can be slow, one of my apps was taking around a minute to load data into collections). Not ideal.
In order to improve this I have created a list within SharePoint with the same columns, made a flow to collect sql rows overnight into this list with any filters that don't need user input. I can then use this list within powerapps which improves speed as it hasn't got to go through the gateway and get restricted by system resources on the onprem server and also the list is smaller as I've already performed some of the filter I need.

Writing
I was getting patch times of over 2 minutes writing back to SQL, especially if there were where clauses on tables of 5k plus rows.
I have now got this down to 10 seconds using this method:
Create a SharePoint list identical to the SQL table you want to patch
Patch everything to this list
Add a flow to do the legwork of updating the on Prem sql table with the SharePoint list data (this takes the load off of powerapps and the user experience)
In the flow Ensure that the list is cleared once the data is uploaded to sql.
You will also have to ensure that the user cannot reload data whilst the flow is running(as there is slight delay), you can get round this in powerapps by checking if the SharePoint list IsEmpty (you could also apply filters if there are writes from multiple people on different data)

I thought this maybe helpful to people as at the end of the day the app has to be quick for the users and no one wants to be waiting.

Categories:

Building Power Apps