Patching collection to sharepoint list, rows saved "scrambled"

[aktuzad]

Hi

Ive made a powerapp with galleries containing a bunch of fields. The fields saves to a collection with "OnChange" and the collection gets patched to a sharepoint list with a button. When using the "save" button, all new records gets created in the sharepoint list, but the order of which the items gets created seems to be totally random. I want to add that my approach to achieve this has been using this excellent guide by Reza https://www.youtube.com/watch?v=wI6SHGQ9ATg , which has been very useful!

Anyone know why or how i can force it to be saved in the same order as in the collection it is patched from? 

----------------------------------------------------------------------------------------------------------

To better explain my issue:

1. The + icon collects a new row to my collection with this code which seems to work fine.

Set(
        tempID;
        tempID+ 1
    );;
    Collect(
        myCollection;
        Patch(
            varDefaults;
            {
                ID: tempID;
                'Type activity': "Lecture";
                Name: ActiveUser.Name
            }
        )
    ) 

 2. With "OnChange" of each of the inputs (combobox, dropdown and textboxes) i patch to "myCollection" using patch. Example code from the combobox below

Patch(
    myCollection;
    ThisItem;
    {Subject: Self.Selected.SubjectCode}
)

3. With the save button i patch my sharepoint list "Activities" with new and edited records with "myCollection".  By using "ID: Blank()", the records gets the next available IDs in the list. The code looks like this:

Patch(
    Activities;
    UpdateIf(
        myCollection;
        Created = Blank();
        {ID: Blank()}
    )
);;

ClearCollect(myCollection;Filter(Activities; Name= ActiveUser.Name));;

When using the save button, the records and edits gets saved/created in the sharepoint list, but the order of new items gets scrambled and does not match the order they were created/patched to "myCollection". I can see it happen in real time in the app when the patch is complete, ClearCollect(myCollection;Filter(Activities; Name = ActiveUser.Name));; runs and the gallery gets populated again. 

Any ideas? is this "just how it works" with patching a collection with new records to a sharepoint list?

[aktuzad]

I got an answer from Reza Dorrani on one of his videos where I asked about this... This method of bulk patching records from collection to sharepoint will create the new records without maintaining the order from the collection.

Anyone got any ideas on how I can achieve maintaining the order when patching from collection to sharepoint list without giving each of the records a specific ID as I dont want to have conflicting IDs if two or more users patch at the same time? 

[WiZey]

Hello @aktuzad ,

Just like Reza said, your records are patched in a bulk. The server on Microsoft's side execute your "Patch()" in one go and it's basically « First Done First Out ».

You could indeed specify an ID to give some order in your "Patch()" to solve your issue, if you absolutely need your records to be ordered.

[aktuzad]

Thanks for your reply

I think I got somewhat of a solution, but ill have to do some more testing.

For patching multiple new records to a Sharepoint list, ill use something like:

ForAll(
    Filter(
        tempCollection; 
        Created = Blank()
    );
    Patch(
        SP-list;
        varDefaults;
        ThisRecord;
        {ID:Blank()}
    )
);;

 Which at least looks like it creates the records in the same order as they are in tempCollection.

Then, for bulk updates ill use:

Patch(
    SP-list;
    Filter(
        tempCollection;
        Created <> Blank()
    )
);;

There are probably better ways to solve this and I really want this to be done correct, and not just work by lots of hacks..

That's why I'm leaving this post open a bit longer in case anyone wants to bless me with their wisdom.😁

(fingers crossed)