Issue updating multiple SharePoint Lists using multiple patches in PowerApps

[klivingstone]

Hi,

When users select the submit button, there are 7 SharePoint Lists I am trying to update, each with a patch function. For the first few weeks, the app worked as planned. Now, only the data from the first 3 patches are saving correctly in their respective SharePoint Lists. In the other lists, only the default values are saved. If the users reenter all their information, the 4 other patches run correctly, meaning all data is saved in their respective SharePoint Lists. 

I don't think the number of lines in the 'OnSelect' property field could be the source of the issue because the other functions after the patches are working correctly: Set variable functions, Email the submitter the data they reported, Reset all the fields for the next submitter, and Navigate to the Home screen.

I would appreciate any advice on how to correct this issue? 

The SharePoint Lists:

1. Submission Log (14 columns updated)

2. Weekly Report (11 columns updated)

3. Office Staffing Report (5 columns)

4. Plant Staffing Report (5 columns)

5. Management Staffing Report (5 columns)

6. Drivers Staffing Report (5 columns)

7. Other Staffing Report (5 columns)  

Note: I tried to combine the last 5 SharePoint Lists into one list with an additional column to designate which staffing category the data in the row belongs to, but I could not get the patch function to save multiple rows in the same SharePoint List. 

[Kirkby]

Hi @klivingstone 

As you tried, combining the 5 lists into one can help avoid unnecessary transaction time

Please refer to the following link about bulk update

How to bulk update records in PowerApps | Microsoft Power Apps  

Create or update bulk records in Power Apps - Power Apps | Microsoft Learn 

Concurrent function - Power Platform | Microsoft Learn

* Concurrent function increases performance for parallel tasks. It works when tasks are not dependent on each other.  Concurrent function works with multiple patches as well. But It does not work when the result from one patch process is used in another patch because it is not parallel.

when using Concurrent(illustration from a Microsoft webpage)

when not using.

Kirkby.