Thanks for your response. Interesting, I didn’t think about using slices.
I wonder if your solution would work for what I have in mind? I oversimplified by quite a bit when I said “checklists” and “to dos”.
The table actually has many more columns. For example, one employee might have pants (this column doesn’t show in the image I attached) but no shirts. Another may have shirts, pants, long sleeved shirts. Another may have customization options that require a lot of additional details to be filled out.
The to-dos/checklists involve making sure if additional (for example) shirts were added, that the quantity required, matched the quantity ordered (at which point status changes to “ordered”), was received in the entire quantity, customized (if needed), then invoiced. Finally, when everything was complete, our process was to record the shirt quantity change manually into a separate “master” sheet. The checklist records were then disregarded and deleted.
The most important purpose of the app is to monitor when changes are made to employees’ apparel and when those changes are made, to be able to track where each piece of apparel is in the “checklist” process. For example, are they still waiting to be received, are they only partially received, have they been invoiced?
Yet, to make a simple change such as when a pair of pants needs to be decreased, not nearly so many details/checklists are needed. It would be an extremely lengthy process to answer every checklist for only a simple change.
For now, I have a separate app that asks what kind of change is needed and based on that answer, shows only certain kinds of “checklists”. However, this app doesn’t reference the master list in any way-- we input company, employee, current shirt model, size and any other details manually as needed. I would love to reference back to the master sheet.
Sorry for the lengthy response.
Thanks again for your time.