Forum Discussion
Re: Creating a form and/or power app timesheet
RShehan through list permissions you could allow the end user to see only the entries they created and not the others.
"I am thinking some kind of power BI output for the end user view." No, I recommend you use Power Apps for the front end with the SharePoint list as the backend.
"Would each login be an individual list?" No, but each user would save the data to a new item in the list.
"Is there some kind of offline capability with SharePoint on a local device? The end users are mostly using a mobile device/cell phone." No, but there is with Power Apps, so if a user loses connection it would save the data to the local device and upload it when the connection is restored.
It shouldn't take too long to build if you have someone in your organisation who know Power Apps. If not there is naturally a learning curve, but as I said in my previous post there are many Power Apps timesheet how-to videos on YouTube. But I can build a quick app for you that will demonstrate what I'v been talking about.
Rob
Los Gallardos
Microsoft Power Automate Community Super User.
Principal Consultant, SharePoint and Power Platform WSP Global (and classic 1967 Morris Traveller driver)
3 Replies
Another update from this morning:
I have the structure, but now need to address some functions in the app itself. The app is limited to the prebuilt one from PowerApps itself, as follows:
And I am hoping to change the date and time selectors to a button that does a time stamp for the start and stop functions of the work and break times. Also, to be able to have an in app image panel to sign a name, like you would do for a post delivery etc.
RShehan it will be a couple of days until I can show you my solution as I've caught COVID and can only work for a few minutes at a time
Rob
Los Gallardos
Microsoft Power Automate Community Super User.
Principal Consultant, SharePoint and Power Platform WSP Global (and classic 1967 Morris Traveller driver)
I found a YouTube channel video that shows a time tracking app that could form the basis of my idea. It is here https://www.youtube.com/watch?v=-crjkn3fxz4
The concept would be to have multiple instances of a start time and stop time to complete rows in a SharePoint list up to 5 or more instances in one shift. So, one row per shift per login, that captures the entire shift work and break times. Ideally there would also be a signature box, checkboxes for various things, possibly a location via GPS.
"It shouldn't take too long to build if you have someone in your organisation who know Power Apps. If not there is naturally a learning curve, but as I said in my previous post there are many Power Apps timesheet how-to videos on YouTube. But I can build a quick app for you that will demonstrate what I'v been talking about."
I am the company developer, but have no experience with PowerApps etc, my history is with Excel and Access etc, old school stuff. I recently completed a sophisticated integrated rostering/time tracking/pay hours/auto overtime spreadsheet for our company. I understand the concepts of objects and coding, but not the PowerApp system.
The timesheet needs to be live / concurrent in terms of time, including if the user goes offline for some reason. It needs one row as a shift in Lists, which is something I am not fully understanding. I see that this is similar to a database design for Access, where the underlying design is important when it comes to the front-end development.
Where should I start the design aspect? With the SharePoint list headers, or the App? On some other projects, I have done both concurrently as I made sense of it.
At this point, I see multiple headers using a slightly different name to correlate with the PowerApp data outputs, such as "WorkTime1", "WorkTime2", "Break1", "Break2", and the corresponding data output from the PowerApp with these as the end reference?
