How to prevent navigation to next screen until patch successfully creates record in SQL table?

(1) Share

Report

Posted on by NMatGWM2

Hi all,

Running into an issue where a patch function intermittently does not go through and does not display an error message. The patch initiates to the SQL table when selecting a button and then navigates to a "end" screen. My theory is that the patch is not completing before the the users reach the end screen and then they exit the app. How can I validate that the record is created in the SQL table prior to the app navigating to the end screen?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

mmbr1606 14,605 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!
hey

did u already try something like this:

IfError( Patch(SQLTable, Defaults(SQLTable), {Column1: Value1, Column2: Value2}), Notify("Error saving record. Please try again.", NotificationType.Error), Navigate(EndScreen) )

you would need to modify the patch to your needs.

if it helps please mark as verified answer

cheers

Was this reply helpful? Yes No
NMatGWM2 22 on at

Like (0)

Report
Copy link

Link copied!

Users are not receiving an error when this occurs, though. They reach the "end" screen without an error, yet the data was not patched.

Was this reply helpful? Yes No
Suggested answer

nvrhughes 115 on at

Like (0)

Report
Copy link

Link copied!

You could always use Power Automate to update the SQL table. Once the SQL step is complete you can add a Respond to Power Apps step in the flow. You can send back any data from the table you want and any steps you have after calling the flow from the canvas app wont run until the flow responds. There is a 120 second timeout between Power Automate and Canvas apps FYI.

Was this reply helpful? Yes No