I have two temporary collections (not SharePoint Lists):
ColIrrParts is my collection of parts used on a single job.
IrrigationShoppingList is my collection of all parts used on all jobs for the week.
I'm trying to add the items in my ColIrrParts collection to my IrrigationShoppingList collection by looking up each item. If the item from ColIrrParts is not found in IrrigationShoppingList, then add the item information from ColIrrParts to the IrrigationshoppingList collection. If the item is found, add the quantity in ColIrrParts to the existing quantity in IrrigationShoppingList.
I know I'm not even close with my formula, but here is what I have:
Patch(IrrigationShoppingList, Defaults(IrrigationShoppingList), LookUp(ColIrrParts, IrrDesc = IrrigationShoppingList, IrrDesc), {Quantity: TextInputQuantity.Text+TextInputShoppingQuantity.Text})
Solved! Go to Solution.
Hi @Nate0173
One thing I can see is the extra line in the UpdateIf - it should be (also had logic wrong way - now fixed - on original post (dangers of free-typing and not testing)
UpdateIf(
IrrigationShoppingList,
IrrDesc = colrrParts.IrrDesc,
{Quantity: colrrParts.Quantity +
IrrigationShoppingList.Quantity}
)
So you can better understand my logic on this - comments are below
ForAll(
ColrrParts( //loop all items of through collection ColrrParts
If(
IsBlank(
LookUp( // see if the item is already in IrrigationShoppingList
IrrigationShoppingList,
IrrDesc = colrrParts.IrrDesc, //matching records
IrrDesc //select one field - not technically necessary
)
)
),
Patch( //If not there add new record
IrrigationShoppingList,
Defaults(IrrigationShoppingList),
{
IrrDesc: colrrParts.IrrDesc, //item description
Quantity: colrrParts.Quantity //add quantity
}
),
UpdateIf( //If already there update existing record
IrrigationShoppingList,
IrrDesc = colrrParts.IrrDesc, //find the right record to update
{Quantity: colrrParts.Quantity +
IrrigationShoppingList.Quantity} //add quantity to existing quantity
)
)
)
Because I have not been able to isolate the issues, I decided to break the entire code into each function individually (ForAll, Patch, and UpdateIf). With the ForAll function, I changed the code to either navigate to the EditScreen or the HTML_Receipt screen instead of keeping the original code.
ForAll:
ForAll(
ColIrrParts(
If(
IsBlank(
LookUp(
IrrigationShoppingList,
IrrDesc = ColIrrParts.IrrDesc,
IrrDesc
)
),
Navigate(EditScreen),
Navigate(HTML_Receipt)
)
)
)
Error: Invocation of unknown or unsupported function.
Error: Invalid number of arguments: received 1, expected 2.
Patch:
Patch(
IrrigationShoppingList,
Defaults(IrrigationShoppingList),
{
Category: ColIrrParts.Category,
IrrDesc: ColIrrParts.IrrDesc,
Quantity: ColIrrParts.Quantity
}
)
Error: The type of this 'Category' does not match the expected type 'Text'. Found type 'Table'.
Error: The function 'Patch' has some invalid arguments.
UpdateIf:
UpdateIf(
IrrigationShoppingList,
IrrDesc = ColIrrParts.IrrDesc,
{
Quantity: ColIrrParts.Quantity +
IrrigationShoppingList.Quantity
}
)
Error on the "=" symbol: Invalid argument type.
Error on "Quantity" in both "ColIrrParts.Quantity" and "IrrigationShoppingList.Quantity": Invalid argument type. Expecting one of the following: Number, Text, Boolean.
Complete Code:
ForAll(
ColIrrParts(
If(
IsBlank(
LookUp(
IrrigationShoppingList,
IrrDesc = ColIrrParts.IrrDesc,
IrrDesc
)
)
),
Patch(
IrrigationShoppingList,
Defaults(IrrigationShoppingList),
{
Category: ColIrrParts.Category,
IrrDesc: ColIrrParts.IrrDesc,
Quantity: ColIrrParts.Quantity
}
),
UpdateIf(
IrrigationShoppingList,
IrrDesc = ColIrrParts.IrrDesc,
{
Quantity: ColIrrParts.Quantity +
IrrigationShoppingList.Quantity
}
)
)
)
OK @Nate0173 ,
Firstly on this one
ForAll(
ColIrrParts(
If(
IsBlank(
LookUp(
IrrigationShoppingList,
IrrDesc = ColIrrParts.IrrDesc,
IrrDesc
)
),
Navigate(EditScreen),
Navigate(HTML_Receipt)
)
)
)
You cannot have a Navigate with a ForAll - the screens would be flicking all over the place. In your case, the only thing you should be doing in the ForAll is patching.
The next bit
Patch(
IrrigationShoppingList,
Defaults(IrrigationShoppingList),
{
Category: ColIrrParts.Category,
IrrDesc: ColIrrParts.IrrDesc,
Quantity: ColIrrParts.Quantity
}
)
I cannot see your data, but it is saying that colIrrParts.Category is a table - when applying a Patch, the source and destination data must be of the same type and construction. Have a look at this in View > Collections, then if a table, look at the heading that contains the value you are after. If it is (for example) Value, then the Patch is ColIrrParts.Category.Value.
The last one
UpdateIf(
IrrigationShoppingList,
IrrDesc = ColIrrParts.IrrDesc,
{
Quantity: ColIrrParts.Quantity +
IrrigationShoppingList.Quantity
}
)
Both of these need to be numeric fields - it is telling you they are not. You might try
Quantity: Value(ColIrrParts.Quantity) +
Value(IrrigationShoppingList.Quantity)
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
@WarrenBelz it makes sense why navigate will not work on the ForAll function.
For the Patch function, I was able to clear all the errors by referring to the gallery items instead of the collection ColIrrParts. Will this work?
Patch(
IrrigationShoppingList,
Defaults(IrrigationShoppingList),
{
Category: GalleryPartsCart.Selected.Category,
IrrDesc: GalleryPartsCart.Selected.IrrDesc,
Quantity: GalleryPartsCart.Selected.Quantity
}
)
Instead of this:
Patch(
IrrigationShoppingList,
Defaults(IrrigationShoppingList),
{
Category: ColIrrParts.Category,
IrrDesc: ColIrrParts.IrrDesc,
Quantity: ColIrrParts.Quantity
}
)
For UpdateIf, I again referred to the gallery item instead of the ColIrrParts collection item to get rid of some errors. The only error I have now is on "IrrigationShoppingList.Quantity". The error is "Invalid argument type. Expecting one of the following: Number, Text, Boolean." I cannot figure out how to pull the value of the quantity in this collection. It seems like it needs the item in the collection specifically identified. Here is my code:
UpdateIf(
IrrigationShoppingList, GalleryPartsCart.Selected.IrrDesc = IrrDesc,
{
Quantity: GalleryPartsCart.Selected.Quantity +
IrrigationShoppingList.Quantity
}
)
Hi @Nate0173 ,
Maybe for the second one
UpdateIf(
IrrigationShoppingList,
GalleryPartsCart.Selected.IrrDesc = IrrDesc,
{
Quantity: Value(GalleryPartsCart.Selected.Quantity) +
IrrigationShoppingList.Quantity
}
)
But you are back to patching one record at a time - is this what you want to do?
I want to patch all records at one time from the collection (ColIrrParts). Does this mean I cannot use the "GalleryPartsCart.Selected.IrrDesc" because it patches only one item at a time? If that's the case, I'm back to using "ColIrrParts.Quantity" which gives me an error "Invalid argument type. Expecting one of the following: Number, Text, Boolean."
Also, I'm guessing that means under the "Patch" function, I need to be referring to "ColIrrParts" instead of "GalleryPartsCart" or I will have the same issue of patching one item at a time instead of all items at one time. Correct?
That is exactly what I am saying and goes right back to the start of this post.
A Patch is not a difficult process to debug - you just need to ensure that the source and destination data types (text, numeric, boolean etc) and structures (single value, complex/table) are the same. I cannot do this for you as I cannot see any of it.
You have a Collection to test - collect this and go to View > Collections and see what is in the field you are having issues with.
You have a data source - go to the Field definition and make sure this is the same.
In the case of ColIrrParts.Quantity, I think it needs to be numeric on both ends
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
I found the solution. I grouped the items in a new collection and then combined the quantities together in yet another separate collection. This allowed me to combine the items with the same description together and add the quantities of the matching items together so my final collection showed each item only once with the combined total quantity for each item.
First the code on the button that copies the items from Collection1 to Collection2 (note: this button is only available when Collection2 is empty):
Collect(IrrigationShoppingList, ColIrrParts);
ClearCollect(ItemsByDes, GroupBy(IrrigationShoppingList, "IrrDesc", "Category", "Quantity"));
ClearCollect(ItemCount, AddColumns(ItemsByDes, "TotalQuantity", Sum(Quantity, Quantity)))
Here is another way of seeing the same code without my specific collection and column naming conventions:
Collect(Collection2, Collection1);
ClearCollect(Collection3, GroupBy(Collection2, "ColumnNameDescription", "ColumnNameCategory", "ColumnNameQuantity"));
ClearCollect(Collection4, AddColumns(Collection3, "TotalQuantity", Sum(ColumnNameQuantity, ColumnNameQuantity)))
When Collection2 is NOT empty, a different button appears when the user wants to add additional items to Collection2. This is the OnSelect code:
ForAll(
ColIrrParts,
Patch(
IrrigationShoppingList,
Defaults(IrrigationShoppingList),
{
Category: ColIrrParts[@Category],
IrrDesc: ColIrrParts[@IrrDesc],
Quantity: ColIrrParts[@Quantity]
}
)
);
ClearCollect(ItemsByDes, GroupBy(IrrigationShoppingList, "IrrDesc", "Category", "Quantity"));
ClearCollect(ItemCount, AddColumns(ItemsByDes, "TotalQuantity", Sum(Quantity, Quantity)));
Same code without my specific collection and column naming conventions:
ForAll(
Collection1,
Patch(
Collection2,
Defaults(Collection2),
{
Category: Collection1[@ColumnNameCategory],
IrrDesc: Collection1[@ColumnNameIrrDesc],
Quantity: Collection1[@ColumnNameQuantity]
}
)
);
ClearCollect(Collection3, GroupBy(Collection2, "ColumnNameIrrDesc", "ColumnNameCategory", "ColumnNameQuantity"));
ClearCollect(Collection4, AddColumns(Collection3, "TotalQuantity", Sum(ColumnNameQuantity, ColumnNameQuantity)))
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