cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Amik
Super User
Super User

Bulk patch creating duplicate records

Hi everyone,

 
 

I am using a method detailed by @mdevaney  to bulk update records using the PATCH function without using ForAll. My requirement does not need to use a traditional checkbox/toggle to identify which records should be updated in bulk. The PowerApp should take the field values from each gallery item and PATCH to their respective IDs in the data source.

 

My data source is PowerBI Integration Data and my update source is a SharePoint list. It is noted in the guidance referenced below that it is important to ensure that the column names from my updates collection matches the column names in my data source. As a result I have ensured my PowerBI fields match up the SharePoint fields.

 

Thus far this is working exceptionally quicker than a ForAll function - from 20 minutes for 40 rows to seconds for 300+ rows. However, I cannot determine why the code is creating new/duplicate items rather than updating existing items.

 

I have included an ID in my updates collection to ensure new rows are not added. I have also ensured the ID column name is the same in both the data source and the update source.

 

I feel that the mistake I am making is obvious. Any ideas?

 

Submit Button On Select:

 

Patch(DB_MarketFeedback, ShowColumns(colPowerBI, "MDStatus", "Title", "Comment"));

 

("MDStatus" is a text field and it is the ID which connects the data source to the updates collection)

 

App On Start

 

ClearCollect(colPowerBI, PowerBIIntegration.Data)

 


References:

https://powerusers.microsoft.com/t5/Building-Power-Apps/Poor-performance-when-patch-whole-collection...

https://matthewdevaney.com/patch-multiple-records-in-power-apps-10x-faster/

 


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


If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.

Imran-Ami Khan

5 REPLIES 5
poweractivate
Most Valuable Professional
Most Valuable Professional

@Amik 

 

From https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-patch

 

PatchDataSourceBaseRecordsTableChangeRecordTable1 )

 

In your example you give this:

 

@Amik wrote:
Patch(DB_MarketFeedback, ShowColumns(colPowerBI, "MDStatus", "Title", "Comment"));

If there are only two arguments you are calling version of Patch which creates a brand new record on the data source DB_MarketFeedback. You must give three arguments. The second argument must be the record you are trying to change, and 3rd argument is what you want to change it to.

 

In that docs link above, it is described somewhat in theoretical way but we noticed. that maybe it has no specific example of the syntax to create. In other words, nowhere does it say in the above docs link under Syntax, that you can do this:

PatchDataSource, NewRecordTable)

 

However the above variant does exist in Power Apps and you might be using it without realizing it. Here is one specific example we can give you that Patch does have the three argument version for editing records, and it does also have the two argument version for creating new records. You can see example of this in our recently tested response and accepted solution here

 

specifically:

 


@poweractivate  wrote:

Patch(TitleColumnPersonList
   ,
   {Title: _BaseRecord.Title, Column1: _BaseRecord.Column1, Person: TextInput1.Text}
)

in that example, notice we call Patch with just two arguments. a SharePoint List Data Source, and a record.

Notice when we use two arguments in that tested solution, it does actually create a BRAND NEW record in the data source. 

 

So your solution is to make sure to use three arguments in Patch. First argument should be the target data source to change the record in. The second argument of Patch should be the actual record you want to change from the data source. If it has to be looked up directly, use Lookup to find it - we happen to have an example of this kind of Lookup in actually that very same link above by the way. Finally, third argument should be a record of what are the columns and new values for those columns. 

 

So now, please check if above helps @Amik 

v-bofeng-msft
Community Support
Community Support

Hi @Amik :

Firstly,let me explain why you encountered this prbolem.

The point is Patch(DataSouce,ChangeRecords) is not a standard syntax.There is no introduction to it in the related documentation of Patch.

Secondly,If you want to update some records in batches with Patch, you should tell it where the table you need to modify is.

I assume I want to update the first and second records in the data source.The formula should be:

Patch(
 DB_MarketFeedback,
 FirstN(DB_MarketFeedback,2),
 ShowColumns(colPowerBI, "MDStatus", "Title", "Comment")
)

Best Regards,

Bof

 

Thanks @v-bofeng-msft  & @poweractivate  for your quick responses.

 

I need to update all records visible in the Gallery . I have taken your example and instead of running on the first or second records, I have revised it to run on all Gallery items.

 

Patch(
 DB_MarketFeedback,
 FirstN(DB_MarketFeedback,CountRows(Gallery1.AllItems)),
 ShowColumns(colPowerBI, "MDStatus", "Title", "Comment")
)

 

 

This seems to work but I am not sure if there is a better way instead of using FirstN? I also need to figure out how to insert new records if they do not exist, either via a separate button or within the same execution (without using ForAll).

@imranamikhan 

Is this

DB_MarketFeedback

 

the data source for the Gallery too?

 

Is that same SharePoint List also the one used in the Power BI report?

 

If so, we are not sure how there can be items in the Gallery that do not exist in DB_MarketFeedback - and same can be said about the Read Only Collection too if they match. 

 

Please indicate about what specific aspect may warrant the need of the batch inserting of new records specifically, or more detail about what specifically may not exist in  

DB_MarketFeedback

 that exists "somewhere else" in the App or the Power BI Report

Hi @poweractivate,

 

DB_MarketFeedback is a SharePoint list and it is not the data source for the Gallery.

 

imranamikhan_0-1608042479550.png


The data source for the Gallery is PowerBI Integration Data. I want to take data from PowerBI Integration Data and either insert records or update records to a SharePoint list (DB_MarketFeedback).

 

I am currently able to do this for individual records using:

 

 

If(CountRows(Filter(DB_MarketFeedback, MDStatus = ThisItem.MDStatus)) > 0,
Patch(
    DB_MarketFeedback,
    LookUp(DB_MarketFeedback,MDStatus=ThisItem.MDStatus),
    {
        Title: Dropdown_Status.SelectedText.Value,
        Comment: TextInput_Comment.Text
        }),
Patch(
    DB_MarketFeedback,
    Defaults(DB_MarketFeedback),
    {
        Title: Dropdown_Status.SelectedText.Value,
        Comment: TextInput_Comment.Text,
        MDStatus: ThisItem.MDStatus
        }))

 

 

I am also able to do this in Bulk using ForAll. However, the performance is too slow so I am trying to apply the method from @mdevaney

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,295)