Hi, @Anonymous, I feel like perhaps a simpler approach would be to maybe have a 'feeder list' in a more public area of SharePoint to trigger your flow upon new entries, then update the true timeclock list (perhaps in a more restricted area?) with the data from that.
This would just allow you to separate out each instance more easily in your head, and build your logic so that you (and others that may interact with the literal flow) can easily see where everything is coming from and going to.
---
Equally, you can run a trigger on new items only ¹ and run two parrallel flow branches.
- Keeps the first entered name, and updates the item with that value
- The other runs an apply to each on the rest of the entries and makes a new item based on the new one but with their name.
---
My final suggestion would be to do away with the manual logging in, and have a check done on a specific activity each day from the Microsoft stack somewhere.
One thing that I know for sure that you can do is use Geopositioning with flow to identify when they are within a certain area (down to 5m, I think) which could track their phone to a desk or building.
But let's pretend the horizon is limitless, and think elsewhere, eh? It could be:
- When they log into their Outlook instance.
- When they set a specific status on Teams.
- When a Power Automate Desktop Flow runs upon login and sends an update to your list.
- When they log into their IP phone and make themselves ready.
My preference would be the latter, which likely has an API or subsystem that you can hook into relatively easily, or program to ping alerts out.
This would eliminate the need for any manual work at all, here, and would speed you along to dealing with a lot less headaches in the area in general. 👍
_______________________________
¹ Not modified, because then you need to handle looping since you are modifying!
