Checklist variations
I am looking to create a checklist for our Preventative Maintenance. I am hoping that someone can help me think of an elegant solution to creating this. The main issue is that we have many machine...
Forum Discussion
It would be one 'checklist' table. And you would have one "Template Checklist" table.
Each 'Release Type' would have many checklist templates.
You can then make your lists, so for 'x' release type we have these 10 questions, and for 'y' we have these 12 questions.
Each 'Release/Receiving' (or whatever you call the main item) would have many 'Checklists'.
But, instead of picking the the 'type' on the checklist, you would pick the type on the parent (Release/Receiving).
Then you would load (via script) multiple child records or checklist items that match that 'type'.
***I absolutely butchered that explanation. I can always show better then explain***
Or do you get what I was trying to say?
Each 'Release Type' would have many checklist templates.
You can then make your lists, so for 'x' release type we have these 10 questions, and for 'y' we have these 12 questions.
Each 'Release/Receiving' (or whatever you call the main item) would have many 'Checklists'.
But, instead of picking the the 'type' on the checklist, you would pick the type on the parent (Release/Receiving).
Then you would load (via script) multiple child records or checklist items that match that 'type'.
***I absolutely butchered that explanation. I can always show better then explain***
Or do you get what I was trying to say?
Matthew,
This is the part I am confused on "Then you would load (via script) multiple child records or checklist items that match that 'type'."
Can you further explain how I would go about loading the child records to the parent table?
Thanks!
This is the part I am confused on "Then you would load (via script) multiple child records or checklist items that match that 'type'."
Can you further explain how I would go about loading the child records to the parent table?
Thanks!