This is causing you to have dis-joint data entry points for a driver as they have to go to different locations in the app to enter the stop info for that location. Your app is starting with a list of locations and then you’re trying to “retro-fit” drivers shifts into that model. I do have a timestamp column in my app, maybe that would facilitate a solution? I also have a ChangeTimeStamp column that I set not to show.įrom the front-end perspective, it’s not even intuitive that the driver should overwrite the data I am expecting the drivers to open this row and enter new information because they visit the same locations over and over on different days during different shifts. When the driver logs on again, I don’t want the strikethrough to be there and I don’t want the questions populated anymore. So for example in the below picture, the location with a green dot and a strikethrough has been visited. But when the shift is over, all the locations should ideally revert to normal. Then the driver logs on for their next shift, answers the questions a second time (because they’re visiting the same locations for a different shift) and the data gets overwritten in the spreadsheet.įrom the front-end perspective, it’s not even intuitive that the driver should overwrite the data because I have a setting that “highlights” the text with a strikethrough when a location has been visited. So from the back-end perspective, the driver’s answers to the questions are recorded the first time. At the start of a new shift, tap the “+” for a new/reset Form.ĭoes this make sense and does it help you at all?.Tap that newly added row in the Table/Deck view to EDIT it for additional information for THAT shift.Enter data and Save to create a NEW row.Tap the “+” button to launch the Form for a new shift.Set the starting view as a Table View or a Deck view.The normal usage for what you are trying to achieve would be: I feel this is creating confusion between what you are seeing and what is being recommended. In your use case, that would not be the recommended approach. It hasn’t been covered here, but my guess based on your comments, is that you have a Form view as the starting view in the application. I think maybe there is a disconnect in understanding where you are starting within the application. If your end goal is to save the data for each driver from each shift, then creating two tables and copying/transcribing rows and performing a reset, is a LOT of extra work you don’t have to do. I believe what you are wanting to do is most certainly available through AppSheets common usage.
0 Comments
Leave a Reply. |