Dear @Federico_Stefanato, thanks a lot picking up my question.
I realize that my chosen wording is not the best, probably because it’s an extract of something bigger.
In the orderDB each row is an item, all have the same style, color only the size differs.
Yes you are right, each item from a same style will get the same components. (from where the item is build up)
The reason I want to execute in steps, has to do with production specifics/dynamics.
When cutting fabrics, the fabric will be put in layers and the fabric has one color, but different dye lots, and as you can imagine, one garment’s components needs to exist from one and the same lot.
The reason it has to go from a orderDB to productionDB is;
- You need to produce more pieces (Items) to be able to deliver
- You need to be able to follow each component individual. Maybe you T-shirt has a print on the front panel and has been outsourced to a printing house and when you get it back it needs to go to the same color lot not to have shading with the other components.
- When all components are stitched, they become an item (garment), so production is a kind of helper table to be able to follow the stages of the production and coordination of it’s logistics.
My aim is to choose from both multi select menus the combination to be generated and with one button to execute the process.
Will that be possible?
This just to avoid having a doc full of single time used buttons as it will never be used afterwards.