I have a workers table as part of a workforce project that i have added fields to and i use integromat to update each field following the submisison of a survey123 form as required. I thought it was working fine until i noticed that some of the edits are not sticking despite a successful result being returned. is there a reason that a workers table might not take these edits. i was wondering if it may be something to do with the fact its the workers table and it is constantly updating that perhaps there may be some conflict with any attempts i am making in addition to it. Is the workers table not a reliable table to use for additional information that needs regular updates with this method.
We don't usually hear of users adding extra fields to the Workers layer and updating the fields in this manner. Can you go into some details on the use case and what information you're storing in the fields? I can't recall a scenario like this before, all cases of adding other fields are for the Assignments layer.
Workforce mobile app does update the Workers layer at regular intervals to record the Worker's location changing and their active state.
I have added some additional fields in order to record some items of stock individual workers have on board their vehicles in integer fields. The idea was to reduce the quantity by a certain amount when work was complete and monitor their stock levels. The integromat runs and it appeared to be working however i noticed discrepancies in the values so i went through the integromat history and viewed the results. The scenario shows a successful update where the stock has been reduced by 1 item and the correct values passed through, but in the next scenario it appears as if the value has been reset and the previous scenario did not work as expected. this does not happen every-time it just seems to happen occasionally, most of the time it works.
First Scenario shows item 2 at 21
Integromat shows succesful update with reduction of 21 to 20
Next scenario shows ITEM 2 at 21 again