Creating asset tracker

[Pete_At_Work]

Hi All

I am an absolute beginner in PowerApps. I am trying to create an app for scanning equipment out for colleagues to use and then back when their shift ends. 

What I would like the app to do is when equipment is scanned out using the ID of the equipment and the colleague, then these details along with the date and time of input would be displayed in a lost below. Once the equipment scanned back in it would be identified on the list below and ad a date and time for the scan in column. After this the operator would have the option to select if the equipment is damaged, fill a box with optional details and then mark the entry as complete. At this point the entry would disappear from the list and stored in a scan history list with the same details.

Unfortunately I have no clue how to get started. If someone could point me to the right direction I would greatly appreciate it.

Please see below a plan of how the app would look.

 

Thanks in advance.

[Tony_Bowes_BP]

You would likely want to start small and do simple steps first. Try to break down what is actually required into simple discrete steps that can be tested either in isolation or into a growing app. 

The way you are describing the app it sounds like you will eventually have a single table (Eg: EquipmentScans) that is creates an initial pre-filled record when someone scans piece of equipment out, then when the equipment is later scanned in it searches for a matching unresolved EquipmentScan record, opens the form for editing with most fields pre-filled ready to accept the potential damage / notes. 

Try to first do all the steps manually:

 - Create an EquipmentScan table with a few fields:  EquipmentID, ScanOut, Status (Out,Returned), ScanIn, Notes

 - From the table, make a model-driven app that allows you to see all the records created and manually create a new EquipmentScan and open existing EquipmentScans

 - Use the model-driven app to mimic initial scan by creating a new record and only filling out the EquipmentId, the scanOut and setting the status to "Out"

 - Repeat to simulate a typical equipment scan (or at least a sample)

 - Simulate scanning in by finding in the list the equipment by ID. You might want to either sort / filter the list at this point to see what works best for you (note that later on you're likely wanting to scan the equipment, but at least see what it's like trying to find the right record without the scanner as this will help know how useful the scanning actually is.) 

 - once you have found the right record, edit it and simulate filling out the Status to returned, ScanIn time and any notes. 

 - Repeat with a typical signin process. 

You should now have the entire process working, but just needing some more fields (like the colleague), and some more niceties (like automation or actual scanning). 

Try to assess what is the WORST part of the app. What is the biggest holdup, or the least pleasant, or the worst in terms of useful data capture. Work on those elements first. Either build a new prototype or flesh out the current app with a few more features.  

To get to where you're pitching with the screen mockup you're eventually going to look into a canvas app with a custom gallery, a custom form that is tailor-made to be quick to enter the returns, Additional table to store useful info on colleagues and equipment, and potentially some additional views to help when things go wrong (like scanning out the same equipment twice). 

Doing simple steps means you can figure out what bits are actually important, potentially get it running earlier, and make the whole project a bit easier to tackle.

Hope this helps.