I have 2 weeks trying to figure out what is happening with my Patch statement. I am pretty close but my knowledge is limited in such way I am almost giving up. Already read hundred of pages between google sources and this forum trying to sort it out. Let's see if you can help me.
I am trying to patch a collection that contains all my updates back to my datasource in dataverse.
First, I use this statement to populate the collection with my DS fields
ClearCollect(CPOItemsChanges,Defaults('T-Purchase Order Items'));
Clear(CPOItemsChanges)
Then On my gallery I am able to capture all the changes into this collection by using the update or collect functions to change only these fields on the collection.
{
crcbb_tpurchaseorderitemsid:ThisItem.'T-Purchase Order Items',
crcbb_description: tdescription.Text,
crcbb_item: Value(titem.Text),
crcbb_part: tpart.Text,
crcbb_qty: Value(tqty.Text),
crcbb_taccountid: taccount.Selected,
crcbb_total: Value(ttotal.Text),
crcbb_tpurchaseorderid: GalPurchaseOrders.Selected,
crcbb_tvesselid: tvessel.Selected,
crcbb_unitvalue: Value(tunitvalue.Text)
}.
Now comes the issue. I am trying to patch this collection back to the same datasource by using this function:
Patch( 'T-Purchase Order Items', CPOItemsChanges )
and I get the error:
Now, if I drop the 3 lookup columns (
crcbb_taccountid and crcbb_tvesselid and crcbb_tpurchaseorderid ) the patch function works and all the remaining fields are updated accordingly.
Patch(
'T-Purchase Order Items',
DropColumns(CPOItemsChanges,"crcbb_tvesselid","crcbb_taccountid","crcbb_tpurchaseorderid")
);
Any idea of what is this error about?
BTW, this is the collection showing one of this lookup fields. All those 3 fields are listed as Record.
Even knowing that I can use forall as well (with loss in performance) I tried, but got the same error.
Then, at this stage, I think the important here is to know why that is happening.
:
Thanks,
Leo
Solved! Go to Solution.
Could you please tell me that how you write the formula into the Items property of taccount, GalPurchaseOrders, tvessel ? (Important!)
Lookup field in Dataverse is a complex field type, so if you have this field type in a collection, it is hard for you to patch.
I have a test on my side, please take a try as below:
Set Items property of the Combo Box as:
Choices([@QiTests].crba2_Testlookup)
Set OnSelect property of the Button:
Patch(QiTests,Defaults(QiTests),{Testlookup:DataCardValue5.Selected})
Note: Testlookup is my Lookup field in my table named 'QiTests'.
Regards,
Qi
Could you please tell me that what is the column type of these three fields, are all of them Lookup type or Choices type and If they are Choices, are they allow multi select?
Also I want to confirm with you that if you want to update an existing record?
I think there is something syntax wrong with your formula. You have a nested collection where has a table inside a collection.
I don't think you could patch the collection directly to the Dataverse, please modify your formula as below:
Patch(
'T-Purchase Order Items',
Lookup('T-Purchase Order Items',ID=xxx), // This determines which record you want to update
{
crcbb_tpurchaseorderitemsid:ThisItem.'T-Purchase Order Items',
crcbb_description: tdescription.Text,
crcbb_item: Value(titem.Text),
crcbb_part: tpart.Text,
crcbb_qty: Value(tqty.Text),
crcbb_taccountid: taccount.Selected.Value,
crcbb_total: Value(ttotal.Text),
crcbb_tpurchaseorderid: GalPurchaseOrders.Selected.Value,
crcbb_tvesselid: tvessel.Selected.Value,
crcbb_unitvalue: Value(tunitvalue.Text)
}
)
Note: I assume that all the field name in your collection are the same as those in your Dataverse Table.
Hope it could help you.
Regards,
Qi
Hi Qi,
Thanks for your response.
All those 3 columns are lookup (records from other tables).
What do you mean with table inside my collection? the error mention exactly about this table. But I can't figure out where this comes from. I was assuming these lookup columns are stored as a record. How can I check?
Regarding the changes , when I use .selected.value I get this error:
Also, I tried to use the GUID of the reference table , but also got an error:
The reference below is where I realized that I can patch the collection straight to the datasource. (The only difference is that on this example I didn't see he using lookup fields on it). And as I mentioned, it is working fine when I remove these columns from my collection.
https://matthewdevaney.com/patch-multiple-records-in-power-apps-10x-faster/
Thanks again,
Leo
Could you please tell me that how you write the formula into the Items property of taccount, GalPurchaseOrders, tvessel ? (Important!)
Lookup field in Dataverse is a complex field type, so if you have this field type in a collection, it is hard for you to patch.
I have a test on my side, please take a try as below:
Set Items property of the Combo Box as:
Choices([@QiTests].crba2_Testlookup)
Set OnSelect property of the Button:
Patch(QiTests,Defaults(QiTests),{Testlookup:DataCardValue5.Selected})
Note: Testlookup is my Lookup field in my table named 'QiTests'.
Regards,
Qi
Hi Qi,
I think you pointed my error, the item property on those lookup columns. It was pointing to the same table instead to point to the lookup table.
But now, when I point to the proper lookup table, its not allowing me to use that same formula. Should I point to the guid column of the lookup table, right?
Thanks again, mate.
Leo
Hi Qi @v-qiaqi-msft, Would you be able to help me with a similar issue - Not being able to Patch to Lookup fields
I had great success using UpdateIf and Patch to bulk update a number of records in PowerApps.
I am now attempting to use the same solutions for a Power App embedded into a Power BI report as follows: -
1. Select Records in PowerBI
2. Show Records in PowerBI Gallery using PowerBIIntegration
3. I create a collection "KYCxCLCollection" from the gallery
ClearCollect(KYCxCLCollection, GalleryPowerBIKYC.AllItems)
4. I use a checkbox within the NewForm to indicate where a user can update individual fields with a different value before patching if they need to. (They are all Lookup fields apart from 'Applies To')
If(CheckboxKycPackage.Value = true, UpdateIf(KYCxCLCollection, true, {'KYC Package Name': LookupKYCPackage_1.Selected.kycPackage}));
If(CheckboxAppliesTo.Value = true, UpdateIf(KYCxCLCollection, true, {'Applies To': ChoiceAppliesTo_1.Selected.Value}));
If(CheckboxRelatedParty.Value = true, UpdateIf(KYCxCLCollection, true, {'Related Party Name': LookupRelatedParty_1.Selected.kycPackage}));
If(CheckboxClause.Value = true, UpdateIf(KYCxCLCollection, true, {'Clause Name': LookupClause_1.Selected.clause}));
If(CheckboxListOfValues.Value = true, UpdateIf(KYCxCLCollection, true, {crb8f_kycpackagexclause_listofvaluesname: LookupListofValues_1.Selected.listOfValues}));
5. I create another collection from the initial collection but drop the IDs to ensure power Apps creates new records rather than updating existing records
ClearCollect(CopyMultipleKYCPackagesCollection, DropColumns(KYCxCLCollection, "crb8f_kycpackagexclauseid", "crb8f_kycpackagexclauseuid"));
6. But the final Patch statement, recognises the source being my inital CDS table "kycPackageXclause" does not seem to like this new Collection I have just created "CopyMultipleKYCPackagesCollection".
Patch(kycPackageXclause, CopyMultipleKYCPackagesCollection)
I can't understand why this works in a straightforward PowerApp, but doesnt work for a PowerApp reading from PowerBI. Any insight MOST HELPFUL, if you can understand everything I have written above!
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!
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
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.
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