Hello,
I've been having problems regarding the code below.
What the code is supposed to do is look into the SharePoint List 'Service Catalog Customer Data' and check if there is a record in it where it has the same Year, Customer, Country and Question values (acting as a composite key).
If there are no record of that particular combination then it should just create a new record using the values specified.
If there is a record of that particular combination then it should update it with the same values specified.
This is then looped through a number of times depending on how many questions are in a separate list (currently in my test data there are 10 questions).
My code adds all the new records as expected. However it will add a new record, instead of modifying one, if a record with the same composite key exists in the SharePoint List. E.g. if there is one record in the SharePoint after this code runs there will be 11 instead of 10 and the original record will be unchanged
The only thing I can think off is that the If Statement Logical Test is always saying true - so it always uses the Defaults () for the Patch. However I don't know why it would be always true if there is a record that already exists filling those parameters.
All of the fields of the composite key are single line of text in the SharePoint list so it's not an issue of data types (at least I don't think it would be).
Could someone help me and explain what's going wrong in my code?
ForAll(
'Service Catalog Questions',
Patch(
'Service Catalog Customer Data',
If(
IsBlank(
LookUp(
'Service Catalog Customer Data',
Year = Year_Dropdown.SelectedText.Value & Customer = Customer_Dropdown.SelectedText.Value & 'Country (Country0)' = Country_Dropdown.SelectedText.Value & Question = ThisRecord.Question
)
),
Defaults('Service Catalog Customer Data'),
LookUp(
'Service Catalog Customer Data',
Year = Year_Dropdown.SelectedText.Value & Customer = Customer_Dropdown.SelectedText.Value & 'Country (Country0)' = Country_Dropdown.SelectedText.Value & Question = ThisRecord.Question
)
),
{
Year: Year_Dropdown.SelectedText.Value,
Customer: Customer_Dropdown.SelectedText.Value,
'Country (Country0)': Country_Dropdown.SelectedText.Value,
Question: ThisRecord.Question,
'Total Gross Revenue': Int(DataCardValue4.Text),
'Total Net Revenue': Int(DataCardValue5.Text),
'TTL Whs Cost': Int(DataCardValue6.Text),
'TTL Trans Cost': Int(DataCardValue7.Text),
'TTL Other Cost': Int(DataCardValue8.Text),
'TTL Cost of Running Promotions': Int(DataCardValue9.Text),
'TTL In Invoice Discounts': Int(DataCardValue10.Text),
'TTL Off Invoice Discounts': Int(DataCardValue11.Text)
}
)
);
Solved! Go to Solution.
@Anonymous
Quite a few things in your formula:
1) Your ForAll is backward. You are using it as a ForLoop like in development - which PowerApps is not. ForAll is a function that returns a table of records based on your source table and record definition. Your ForAll is STILL going to go through that process and will generate a potentially large table based on the Patch you have in it that will then ultimately be discarded as you are not using it...this is a big hit on performance!
2) You are using the SelectedText property of your controls - this is a Deprecated property that should be avoided. Instead you should be using the .Selected.column (for the sake of the suggested formula below, I will assume Value as the column name)
3) You are specifically converting text numbers into an Integer (no decimal values). You have things like Cost which is commonly currency and commonly would have decimal values, so I would suggest (and have altered in the suggestion below) using the Value function instead of Int.\
4) You are using a single ampersand in your Lookup formula. This will concatenate values together. I am pretty sure you wanted to "AND" the criteria, in which case, you need a double ampersand &&
Please consider changing your Formula to the following:
Patch(
'Service Catalog Customer Data',
ForAll('Service Catalog Questions' As _item,
{
ID: LookUp(
'Service Catalog Customer Data',
Year = Year_Dropdown.Selected.Value &&
Customer = Customer_Dropdown.Selected.Value &&
'Country (Country0)' = Country_Dropdown.Selected.Value &&
Question = _item.Question,
ID
),
Year: Year_Dropdown.Selected.Value,
Customer: Customer_Dropdown.Selected.Value,
'Country (Country0)': Country_Dropdown.Selected.Value,
Question: ThisRecord.Question,
'Total Gross Revenue': Value(DataCardValue4.Text),
'Total Net Revenue': Value(DataCardValue5.Text),
'TTL Whs Cost': Value(DataCardValue6.Text),
'TTL Trans Cost': Value(DataCardValue7.Text),
'TTL Other Cost': Value(DataCardValue8.Text),
'TTL Cost of Running Promotions': Value(DataCardValue9.Text),
'TTL In Invoice Discounts': Value(DataCardValue10.Text),
'TTL Off Invoice Discounts': Value(DataCardValue11.Text)
}
)
);
In the formula above, the ForAll will iterate over the 'Service Catalog Questions' table. For each record in that, it will LookUp the record that matches the dropdowns for Year, Customer and Country and then the Question that is in the current record of the ForAll source - which is now name with the As operator as "_item".
The ONLY thing we care about for that record is the ID. If it is found, then ID will be a valid ID. If it is not found, then the ID will be blank.
The rest of the record definition for the records returned from the ForAll continues as you had before, with the exception of the corrections for the SelecteText and the Int functions.
At the end of the ForAll, there will be a table returned. That entire table will be passed to the Patch function.
Patch is smart!!
It can take an entire table to work on rather than having to instantiate itself over and over (when the ForAll is used wrong).
That table is coming from the ForAll - as that is what a ForAll does!
PLUS, patch is smart enough to look at the primary key value to determine what to do. IN your case, the ID is the primary key, SO, if the ID has a value, then Patch will update the record with that ID and the record provided with the updates.
IF the ID is Blank, then Patch will create a new record with the provided record.
That is all you need.
This will be much more performant and easier to maintain and deal with.
I hope this is helpful for you.
ForAll(
'Service Catalog Questions',
If(
IsBlank(
LookUp(
'Service Catalog Customer Data',
Year = Year_Dropdown.SelectedText.Value & Customer = Customer_Dropdown.SelectedText.Value & 'Country (Country0)' = Country_Dropdown.SelectedText.Value & Question = ThisRecord.Question
)
),
Patch(
'Service Catalog Customer Data',
Defaults('Service Catalog Customer Data'),
{
Year: Year_Dropdown.SelectedText.Value,
Customer: Customer_Dropdown.SelectedText.Value,
'Country (Country0)': Country_Dropdown.SelectedText.Value,
Question: ThisRecord.Question,
'Total Gross Revenue': Int(DataCardValue4.Text),
'Total Net Revenue': Int(DataCardValue5.Text),
'TTL Whs Cost': Int(DataCardValue6.Text),
'TTL Trans Cost': Int(DataCardValue7.Text),
'TTL Other Cost': Int(DataCardValue8.Text),
'TTL Cost of Running Promotions': Int(DataCardValue9.Text),
'TTL In Invoice Discounts': Int(DataCardValue10.Text),
'TTL Off Invoice Discounts': Int(DataCardValue11.Text)
}
),
Patch(
'Service Catalog Customer Data',
LookUp(
'Service Catalog Customer Data',
Year = Year_Dropdown.SelectedText.Value & Customer = Customer_Dropdown.SelectedText.Value & 'Country (Country0)' = Country_Dropdown.SelectedText.Value & Question = ThisRecord.Question
),
{
Year: Year_Dropdown.SelectedText.Value,
Customer: Customer_Dropdown.SelectedText.Value,
'Country (Country0)': Country_Dropdown.SelectedText.Value,
Question: ThisRecord.Question,
'Total Gross Revenue': Int(DataCardValue4.Text),
'Total Net Revenue': Int(DataCardValue5.Text),
'TTL Whs Cost': Int(DataCardValue6.Text),
'TTL Trans Cost': Int(DataCardValue7.Text),
'TTL Other Cost': Int(DataCardValue8.Text),
'TTL Cost of Running Promotions': Int(DataCardValue9.Text),
'TTL In Invoice Discounts': Int(DataCardValue10.Text),
'TTL Off Invoice Discounts': Int(DataCardValue11.Text)
}
)
);
@Anonymous
Quite a few things in your formula:
1) Your ForAll is backward. You are using it as a ForLoop like in development - which PowerApps is not. ForAll is a function that returns a table of records based on your source table and record definition. Your ForAll is STILL going to go through that process and will generate a potentially large table based on the Patch you have in it that will then ultimately be discarded as you are not using it...this is a big hit on performance!
2) You are using the SelectedText property of your controls - this is a Deprecated property that should be avoided. Instead you should be using the .Selected.column (for the sake of the suggested formula below, I will assume Value as the column name)
3) You are specifically converting text numbers into an Integer (no decimal values). You have things like Cost which is commonly currency and commonly would have decimal values, so I would suggest (and have altered in the suggestion below) using the Value function instead of Int.\
4) You are using a single ampersand in your Lookup formula. This will concatenate values together. I am pretty sure you wanted to "AND" the criteria, in which case, you need a double ampersand &&
Please consider changing your Formula to the following:
Patch(
'Service Catalog Customer Data',
ForAll('Service Catalog Questions' As _item,
{
ID: LookUp(
'Service Catalog Customer Data',
Year = Year_Dropdown.Selected.Value &&
Customer = Customer_Dropdown.Selected.Value &&
'Country (Country0)' = Country_Dropdown.Selected.Value &&
Question = _item.Question,
ID
),
Year: Year_Dropdown.Selected.Value,
Customer: Customer_Dropdown.Selected.Value,
'Country (Country0)': Country_Dropdown.Selected.Value,
Question: ThisRecord.Question,
'Total Gross Revenue': Value(DataCardValue4.Text),
'Total Net Revenue': Value(DataCardValue5.Text),
'TTL Whs Cost': Value(DataCardValue6.Text),
'TTL Trans Cost': Value(DataCardValue7.Text),
'TTL Other Cost': Value(DataCardValue8.Text),
'TTL Cost of Running Promotions': Value(DataCardValue9.Text),
'TTL In Invoice Discounts': Value(DataCardValue10.Text),
'TTL Off Invoice Discounts': Value(DataCardValue11.Text)
}
)
);
In the formula above, the ForAll will iterate over the 'Service Catalog Questions' table. For each record in that, it will LookUp the record that matches the dropdowns for Year, Customer and Country and then the Question that is in the current record of the ForAll source - which is now name with the As operator as "_item".
The ONLY thing we care about for that record is the ID. If it is found, then ID will be a valid ID. If it is not found, then the ID will be blank.
The rest of the record definition for the records returned from the ForAll continues as you had before, with the exception of the corrections for the SelecteText and the Int functions.
At the end of the ForAll, there will be a table returned. That entire table will be passed to the Patch function.
Patch is smart!!
It can take an entire table to work on rather than having to instantiate itself over and over (when the ForAll is used wrong).
That table is coming from the ForAll - as that is what a ForAll does!
PLUS, patch is smart enough to look at the primary key value to determine what to do. IN your case, the ID is the primary key, SO, if the ID has a value, then Patch will update the record with that ID and the record provided with the updates.
IF the ID is Blank, then Patch will create a new record with the provided record.
That is all you need.
This will be much more performant and easier to maintain and deal with.
I hope this is helpful for you.
Thank you so much!
Aside from a couple minor changes like datatypes and the selected columns which you mentioned it worked perfectly 🙂
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