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?
How to prevent navigation to next screen until patch successfully creates record in SQL table?
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.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.