Hi, I'm fairly new to the power platform and I have been tasked with creating an inventory catalog that matches up with our back end SQL data. I am creating this catalog using powerapps and I am using sharepoint as a database to connect the two. FYI this would be much easier if our company could afford to give all of our users premium powerapps licenses because then I could just connect it directly to the source data; however, we are a small company and cannot afford 100 or so premium powerapps licenses.
Anyway, so my issue here is how do I keep this information up to date as frequently possible?
-I have been trying to leverage our 1 premium power automate license to workaround this issue, following and recreating the solutions of this post and the template. One solution is an update/insert solution and the other is just deleting all the items in the SP list and reuploading the refreshed data from SQL.
Post 1: https://powerusers.microsoft.com/t5/Building-Flows/SQL-to-Share-Point-Insert-Update/td-p/307864
Both of these either have timeout issues or they just take forever. Does anyone have any ideas to help with this process without paying out more money?
Other info: I have maxed the concurrency control out and the pagnation is on with a 15000 threshold limit
The list contains 14,918 items
So I would suggest opening a new topic as we are kinda drifting here from the original post and tbh I have to get back to work lol. But you may be able to achieve whatever you're trying to do in those nested apply to each actions in a more efficient way that someone more versed at https://powerusers.microsoft.com/t5/Microsoft-Power-Automate/ct-p/MPACommunity could probably take a crack at. But my last suggestion would be for both apply to each actions set the concurrency control to the max -
Now I see another problem. I see that flow is success but the create item did not do anything in my destination Sharepoint list as below. Please help
As you see below, I have set pagination to 100 on get rows and below is the same where it will stay forever.
If your table isn't any larger than 5000 records you're trying to pull set it to that and lmk if it is still getting stuck. If it is then I would first test it in a separate flow that just gets the rows and thats it and see if that works. If that doesn't work then I would remake the connection
No Pagination as below. My rows are hardly 2000 rows total. Do I have to mark pagination of 3000 for 2000 rows?
Just so I'm understanding this right, the action 'Get rows' is where it stalls and gets stuck? If so, how big is the table you are trying to pull? Are you using pagination in the settings of that action? Is there a condition you can use to make the pull smaller? Have you tried remaking the SQL connection? If it gets stuck there, I would even make a brand new flow with a manual button trigger and then a duplicate 'Get rows' action to see if it works there.
@Anonymous @bhanney2323 - Please check below flow which I have built from the template.. Till Get Rows, it works after that it hangs there and does not go any further as it stays grey during running.
Can you post some screenshots of your flow, I'd be happy to take a look
We just have the $15 premium plan so we can use SQL connectors
We had the [Per user plan with attended RPA] which was $40.00 usd, but has limited on the flow process.
Due to a small amount of people knowing how to using power automate and flow being processed.
stampcoin
87
Michael E. Gernaey
70
Super User 2025 Season 1
David_MA
48
Super User 2025 Season 1