Data flow generated in PowerApps to Sharepoint list gets interrupted (with error message) when the mobile connection is not active

[MarcB1966]

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 🙂

[BrianS]

Automating this may be an issue-

You can use SaveData and LoadData to hold the info from your  app. You could set up a button that would only be enabled when they have a connection that would push all the waiting data. You may still have an issue depending on how your Flow works (can it handle multiple concurent data, does it know which data it is recieving, etc)

I do not know of a way to automatically push the data when a connection is made. That could also be a poblem if the person is traveling in and out of service, some data may still be "cut off" if service drops right after it connects.

[MarcB1966]

Hi BrianS, 

Thx for the feedback.

Enabling the button once connection is back available looks like solution 1 (see initial message), which I would like to avoid for two reasons :

1. The data is no longer using the correct geo-code and timing (unless this is "registered" with the Save and LoadData functionality). 
2. Additionally, this would imply that the technician can not proceed to the next phase (eg Stop Intervention) and which is not feasible in real life.

You do have a point on the potential issue on how the Flow works (can it handle multiple concurrent data, does it know which data it is receiving, etc ... ?)   That was why I was looking for some guidance/ideas on how to proceed with this (also referring to collections as possible solution).

Valid observation that - when a solution would be found to hold data until connection was restored - if the person is traveling in and out of connection service, some data may still be "cut off" if service drops right after it connects.

Will continue my search for a solution ...

Thx,

Marc

[BrianS]

As far and #1 is concerned, the data collected at the time the button is pressed would be saved with the correct geo stamp and timing. You would need to save this to a collection and then use the SaveData function to save it locally. Once that save is accomplished the tech can then proceed to the next phase. 

I set up a similar thing for techs. They saved data all day and then when they returned to the shop they hit the "End of the Day" button and it loaded all the data to the list. You miss out on the real-time knowledge of what the tech is doing, but maintain data integrity. In the solution I created, the company had GPS units on the vehicles so progress of the day was tracked that way. You rFlow would just have to be able to parse the incomming information to correctly handle writing it the lists.