Table A: Library of data that should not be changed
Table B: is the table in question
I would like to have users select as many items as they would like from Table A and those items be copy and pasted into table b as new rows. (when the data is copied it brings the entire row from Table A). I allow the user to edit the data in table B (there are 5 columns and they have the ability to edit the data in all 5 columns). once the user is done editing, I would like to group all these items so that I can display it in a collection while still giving the user the ability to go back and edit those items at any time.
are there any suggestions on how to approach this?
But the table B won’t have those specific items grouped together right? For more context, Table A is a food Library. Table B is intended to be a recipe table. I would like users to choose as many food items from the food library, change the serving size for each food item, and then once they have completed adding all the food items and changing serving sizes, they can save that to a single recipe. When they go and view the recipe they can see all the food items and still have the ability to edit the servings on each food item.
OK… I guess that depends a lot on your app flow. How do you specify a new recipe? I would think you could write that recipe name or ID into it’s own column at the same time that you are creating the new rows.
yes, I would put the recipe name in it’s own column but I am not sure how to display these grouped items to the user since they are all in different rows
You can use a collection to display multiple rows. That collection can be sourced from a relation, or a query, or can simply be filtered based on the Recipe Name or ID. It’s really hard to give specific details without knowing much about your app, what the desired flow is, and what the desired outcome is. All I can say is that it’s 100% possible.