Should I be Creating a Collection

[Phineas]

I have the need to allow a user to item multiple choice to
an order form in Power Apps. I've created a Power Apps form
that replicates the below table and other needs.

I have created a SP List and the below app based on that List.
Currently the list only has one column for each product need.
The client should be able to add up to '10' size options (or items)
per order form that is associate with that singular client.

I'm thinking I should be creating a collection of items based on
the items at the bottom, saving the each item to the collection,
then Patch the collection to the List?

If this is true can you provide insight into how to best achieve?

[RandyHayes]

@Phineas 

Are the items list that you are showing child records to the parent form record?  Or are all of these columns in your list?

[Phineas]

Currently the blank SP List has a one to many relationship.

If the user has more than one product choice the user's name will appear multiple times in the SP List.

I believe this was your question.

I have created a 'UniqueID' column (content yet to be determined) in the SP List.

I have created a button and a collection that is currently populating all data from the form using the following.

Collect( ProductOrder,

{ FullName: DataCardValue10.Text,
LastName: DataCardValue11.Text,
FirstName: DataCardValue12.Text,
BuildingTye: DataCardValue17.SelectedText.Value,
PrimaryNoise: DataCardValue18.SelectedText.Value,
Address: DataCardValue13.Text,
SuiteApt: DataCardValue14.Text,
State: DataCardValue15.SelectedText.Value,
ZipCode: DataCardValue16.Text,
WindowNumber: DataCardValue25.Text,
WindowWidth: DataCardValue19.SelectedText.Value,
WindowHeight: DataCardValue20.SelectedText.Value,
WindowQuantity: DataCardValue21.SelectedText.Value,
WindowCovering: DataCardValue22.SelectedText.Value,
WindowFrequencyOrUse: DataCardValue23.SelectedText.Value,
WindowShape: DataCardValue24.SelectedText.Value,
OrderComments: DataCardValue26.Text});

[RandyHayes]

@Phineas 

Yeah...you don't need to do all of that.  In fact, typing all that in is a waste of your time!

Your gallery already has the information you need.  You only need a base collection to provide the rows for your gallery.

Your Unique ID already exists in your SharePoint list...it is ID

So I assume that your red-circled item in your picture is the gallery?  Please confirm.

Also, is your solution to only create new records or to edit existing records?

[Phineas]

Actually everything is in a 'Form' (DisplayMode.New), created with the 'Integrate Power App' link from SP after I finished making the List.

[RandyHayes]

@Phineas 

You will need to put the gallery outside of the form.  It provides no advantage to have it in the form, but yet it has a long known bug when used in a form.

While we're at it...what is the Item property of your form?

[Phineas]

SP autogenerated a multiple component app from the List with BrowseScreen, EditScreen (the form I've edited), and DetailScreen.

The Items property of the Edit Form was by default 'BrowseGallery1.Selected'.

[RandyHayes]

@Phineas 

Okay...that is all fine, there will be a couple of changes to that.

But still, you will not want the Gallery to be in the form in a datacard.  That should be outside of the form.

In re-looking at your formula you provided for the collect function (which again...you don't need), I notice you do not have a master ID column in the list.  Perhaps this is what you meant by UniqueID column!?  But, at any rate, your child list (many) should have a column to identify the parent record ID (one).  

Now, what I am not seeing is "gallery control" in your screenshots.  

Your original mockup shows rows of Size 1 to Size 10.  

Your screenshot of the gallery shows nothing for adding or removing rows to your child list.

What is your thought there?  Have you just not added it yet?

Will you be providing not only the ability to add rows, but also to remove rows?

[Phineas]

Currently there is no Gallery in the fillable form (shown below).

All fields in the form are datacards.

Everything above the red circle should be reflect across every line item on the SP List related the all the items from the fields in the red circle (which will remove and add back as a Gallery).

I changed the SP List 'Title' column to 'UniqueID' I just need to develop content the loads with the form/gallery data. 

Yes, it would be most appropriate to have a single new item line with the ability for the user to add lines items, up to 10.

[RandyHayes]

@Phineas 

You are stating that your controls in red circle are all in datacards in the form.  Are you stating that your Parent list has columns for those items (i.e.  Height, Width, Qty, etc.)??  I though you said you had a one-to-many relationship (Parent - Child)?

If so, then all of those should be in your child list.

Having the UniqueID in your parent record is not relevant.  It already has a unique ID - the ID column.

It is the child list that needs to have a column to hold the ID column value of the Parent record.  Title is a Text column.  I would advise having a number column in your list to hold the Parent ID...as it is a number.

You mention that you "develop content the loads with the form/gallery data" - but yet you also said - "there is no Gallery"

So, the point I am making is that the red-circled items are all for your Child list...not the Parent list.  So, all of that should be done in a Gallery that is outside of your form.

Getting data in and out of the gallery is very easy - don't worry about that at the moment.  First get your "foundation" in place.  

1. Numeric Parent ID column in Child List

2. Gallery outside of your form

3. All of the controls you have in the red-circle into your gallery template

4. An "Add" Icon or button to add new rows to your child list

5. An optional delete/trash icon in the gallery if you want to also be able to remove rows from the child list

Once you have that all in place, then the formulas will be very simple.  I will give you those as well once you are ready.