Hello everyone. First off I’d like to say thank you to the community for already offering me so many valuable answers to questions I’ve had. However, I’ve become stumped on how to structure my data and thought someone more experienced may be able to help. Apologies for being a noob!
I have three main tables in my Field Service app:
Equipment - key: Equip Serial
Components - key: Barcode
Service Report - key: Visit ID
Whereas the Service Report only exists/makes sense with a related piece of Equipment & its corresponding Components. I’d like to have ref rows from the Service Reports appearing under both the related Equipment records as well as the related Components.
I’ve achieved that quite easily, but what I’m struggling with is our workflow. Our techs need to be able to change out certain Components within the Equipment on the fly; a lot of times they don’t know which Component they may need to replace until they’re very far into a detailed Service Report. So the only solution (that I’ve thought of) is to have the Component table as the child to the Service Report table, in order to allow for edits on the fly from within a form. However, if you do that, it doesn’t make sense in the overall data structure described above.
Any advice would be very appreciated! Sorry if I’m missing any key concepts or anything, and please let me know if you need more detailed/specific information on anything. Cheers!
LinkedIn
Twitter
