Well, unless you have more fields in the ORDER-TABLE the two tables are basically the same.
the first repeating group / table would be:
do search for BAGS.
it will show you all bags with all printed status.
The second table / repeating group you can make has a data source:
do search for BAGS but it has a constraint:
isBagPrinted = yes
it will then only list the printed bags.
If you need an order table / data type because you have a lot more fields that you need in that particular table you can create a field in ORDER_TABLE called BAGS. This is not a text field but a field of type BAGS.
This way you link BAGS to ORDER-TABLE.
But I do not think this will get you where you need to go. I would stick to as little data types as you can and it seems you can manage with just the BAGS table looking at your example.
Both tables have around 12 fields each! I’ve just simplified this here.
The second table ORDER-TABLE has order number, customer name, customer address etc, so I need to create a repeating group that shows only the customer orders that have printed bags on order so that I can pass it to the right person in the factory.
I simplify things and if I have an order with two bags or more I create a new record with same order number, so one record per bag but two records can have the same order reference, to keep things simple. Not Ideal but when I get better with bubble will upgrade!..sorry this is me too( various2 )