Context : Service workers are using a PowerApp to 'register' their activity based on buttons they need to click during the day, when they (example given) arrive at their customer, or when they leave the customer. Pushing the button, results in a flow being populated with data such as Customername, geo-codes, time, etc ....
This works technically fine as long as they have a mobile connection.
When the connection is lost, pushing a button (to generate that flow), results in an error message. Additionally, when the service worker gets back on line, the error flow is not "re-produced" towards sharepoint.
One solution (nr 1) could be to 'disable' the button until connection is back, but this implies that geo-code and timing will no longer be accurate.
The other solution (nr2) - which I prefer - would be to 'store' all relevant data into a collection as long as connection is not available. Each time a new button is pushed, the (additional) relevant data would be stored to the same collection (in a new row) just up to the moment that connection is restored. At that point, all the gathered information would be released into sharepoint, using the flows.
I currently have a component showing if there is a connection or not, which is displayed at each individual screen.
But, looking for some guidance how to setup the "conditional" collection (if no connection), and how to "release" when connection is back available.
Much appreciate any additional insight 🙂