Service Engineer Report

[FleetcareAz]

Hi all

I am trying to create an app for our small team (10 users max)   

Basically I want to create a tablet app,  that a field service engineer can fill in, when on site completing service calls.

Simple details -  Location, time, date, work carried out,  a list of parts used, any follow up work required,  customer name and signature sign off.

When this work is done, it needs to be automatically emailed as a PDF sheet (or XML or similar)    to myself, the engineer, and the customer.   It also needs to store somewhere on the dataverse (anything),  so it can be extracted and analysed.
However.....I also need to stop our engineers accessing each others records.

So basically its boiled down to =  a "work/job completed" app to fill in work/site data (example =  attend site, repair plumbing, used part A to fix leaky tap, date/time,  customer signed off) 

There will be 3 super users with access to everything data,  and then 7 service engineers/users who can only see their own data/records completed. 
Then around 50-100 customers who receive email copies of worksheets.

Appreciate this is a lot, and I don't want anyone to do this all for me.....  but any help would be appreciated as I have found creating this using power apps to be difficult, and wondered if anyone could point me in the right direction about what I should be using. 

(I am fairly new to 365/power platform, and the AI assistant doesn't seem to grasp the concept and just keeps creating tables for me!)

How do I create the environment required

Where i am best starting please,  I don't want to go down the wrong road and find out 3 months later I creates an app using the wrong tools/environment!

Thanks all

[NickMerrick]

So what are you using as a backend for your reports? If your using dataverse or sharepoint, you could have emails autogenerate on new record creation trigger in Power Automate, I use it to generate HTML reports then us Encodian HTML to PDF action. As for filtering who can see or edit what, you can setup a Super user list, listing the emails of all those who need access to everything, then setup you app so if anyone logs in with an email on the super user list, they can see and edit everything, otherwise the collection is filtered to whoever is actively logged in, which can be referenced using User().Email 

[FleetcareAz]

Thanks for reply.  At the moment we have been using excel for the data to trial it,  but we plan on using sharepoint, however its not something anyone here is familiar with.
I am no coder per say, however I understand CSS+HTML and some python.  My main issue is deciding how to start this off all together,  start with data/start with template/ start with CoPilot.   What is going to give me the flexibility to design what we need, but also be the easiest learning curve?

[NickMerrick]

If you already have your data columns sorted, it be easiest to setup your SharePoint lists first. I haven't used a lot of the templates myself but those could definitely give you a good jumping off point. As for co-pilot, every time I try it it just makes a data table or says it cant help me.

Sharepoint is really straight forward, and if your unsure of a field type like number or text, if you think your end user might type in anything other than a number, just make it a text field, easier to force format stuff later if need be, and allows for more flexible input. Canvas apps are very forgiving and the learning curve is pretty shallow.