So I need to create a flow that will write a timestamp in a column each day when someone comes in to the building. I want it to remember 30 days worth of punch-ins. I'd also like it to include the temperature from the first punch-in of the day, but it may not be entered on subsequent punches that day. I don't want it to create a new row if the person already has put it in once before.
Can I offer three suggestions?:
What's the best way to make that happen?
@TL_Arwen wrote:What's the best way to make that happen?
That's a big bunch of questions wrapped into one, but start with this:
Regards,
Bryan
Thanks for that. I am taking a read. I also only want the one line per person as this will be used for our ERT team. So in an emergency, if they need to see who's currently in the building, it needs to be a fast access kind of thing.
@TL_Arwen wrote:Thanks for that. I am taking a read. I also only want the one line per person as this will be used for our ERT team. So in an emergency, if they need to see who's currently in the building, it needs to be a fast access kind of thing.
It sounds like you're planning to use your data source as the user interface -- can I steer you away from that idea too?
To:
set up a simple, intuitive interface that lets your users see and understand the data in the ways that are most effective for them. Forcing them to find, open, and understand an Excel file with 30+ columns in an urgent situation seems at odds with that.
Instead, Power Apps makes this stuff possible and accessible, or everyone would still be using Excel. You can create a single screen app labelled "Who's in the Office?" that shows a list of names that is accessible with one or two taps on a tablet. The screen can show a table (gallery) summary of a simple query of the Sharepoint list that filters which people have checked into the office but not yet checked out that day.
@BCLS776 wrote:
@TL_Arwen wrote:Thanks for that. I am taking a read. I also only want the one line per person as this will be used for our ERT team. So in an emergency, if they need to see who's currently in the building, it needs to be a fast access kind of thing.
It sounds like you're planning to use your data source as the user interface -- can I steer you away from that idea too?
To:
- keep people using your solution,
- preserve data integrity and avoid accidental edits,
- and save time,
set up a simple, intuitive interface that lets your users see and understand the data in the ways that are most effective for them. Forcing them to find, open, and understand an Excel file with 30+ columns in an urgent situation seems at odds with that.
Instead, Power Apps makes this stuff possible and accessible, or everyone would still be using Excel. You can create a single screen app labelled "Who's in the Office?" that shows a list of names that is accessible with one or two taps on a tablet. The screen can show a table (gallery) summary of a simple query of the Sharepoint list that filters which people have checked into the office but not yet checked out that day.
Yeah, after I sent that, I thought of that. Just make a query that will take the data and tell me who's in the office and display it nicely. And also have something set up so that after 14 days (our current requirement for contact tracing) it will delete entries. That way I can just do single line for each clock in and out.
User | Count |
---|---|
260 | |
109 | |
92 | |
56 | |
41 |