cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Patching multiple values to SharePoint

Hello PowerApps Community 🙂
I am building an online shopping car. I'm using a Collection to collect the items and then patching them to a SharePoint List.   There is an Inventory number field in SharePoint that I would like reduced by the number of items (Qty) selected inside the Collection.

Collection = colMyOrder
SharePoint List = 'Company Store'
Inventory Column in SharePoint = 'Inventory'
Gallery = galProducts
CurrentInventory_Lbl = a Label that contains the Inventory number from SharePoint
Qty = a variable that has the number of inventory to be checked out from the Collection (which must be subtracted from the CurrentInventory)

Here is my current code:
ForAll(
colMyOrder,
Patch(
'Company Store',
galProducts.Selected,
{'Inventory (Inventory0)': Value(CurrentInventory_Lbl.Text) - Qty}
)
);


The issue:

This code works fine when I only check out 1 item from the Collection. The Inventory field is SharePoint is subtracted correctly. The issue is when I check out multiple items! When I do so, only the last Inventory field is updated whereas the other items stay the same

Example:
If I checked out 5x PENCILS, 2x DESKS, 7 ERASERS, the only Inventory in SharePoint that will be updated is the ERASERS because it is the last one to be added to the collection

If there is a way to make sure all inventory fields in SharePoint are updated, that would be much appreciated!

Thanks much as always and appreciate all the value that this community provides.

Cheers,

Andy

1 ACCEPTED SOLUTION

Accepted Solutions

@axt3641

Your code currently looks like this.

 

ForAll(
    colMyOrder,
    Patch(
        'Company Store',
        galProducts.Selected,
        {'Inventory (Inventory0)': Value(CurrentInventory_Lbl.Text) - Qty}
    )
);

 

The reason your PATCH always updates the same record is because of this code segment in the 2nd argument.  It tells PowerApps which record should be updated in 'Company Store'.

 

galProducts.Selected

 

The selected property will ensure the current selection in a gallery will be the target.  Instead, we want to target the "current" record in the ForAll loop.

 

ForAll(
    colMyOrder,
    Patch(
        'Company Store',
        ID = colMyOrder[@ID],
        {'Inventory (Inventory0)': Value(CurrentInventory_Lbl.Text) - Qty}
    )
);

 

This solution assumes the ID number referencing the item in the company store is contained in colMyOrder.

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

View solution in original post

9 REPLIES 9

@axt3641

Your code currently looks like this.

 

ForAll(
    colMyOrder,
    Patch(
        'Company Store',
        galProducts.Selected,
        {'Inventory (Inventory0)': Value(CurrentInventory_Lbl.Text) - Qty}
    )
);

 

The reason your PATCH always updates the same record is because of this code segment in the 2nd argument.  It tells PowerApps which record should be updated in 'Company Store'.

 

galProducts.Selected

 

The selected property will ensure the current selection in a gallery will be the target.  Instead, we want to target the "current" record in the ForAll loop.

 

ForAll(
    colMyOrder,
    Patch(
        'Company Store',
        ID = colMyOrder[@ID],
        {'Inventory (Inventory0)': Value(CurrentInventory_Lbl.Text) - Qty}
    )
);

 

This solution assumes the ID number referencing the item in the company store is contained in colMyOrder.

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Thanks for the reply, Mr.Devaney.

It makes sense why "galProducts.Selected' would be the issue since it only selects the currently selected value and not all the items in the collection!

I tried the following but it seems not to work. I think the reason is that I'm patching the ID field a bit differently.

ID = colMyOrder[@ID]


I am using the following in my Collection:

UpdateContext(
        {
            ctxPrevcartAdd: LookUp(
                colMyOrder,
                galProducts.Selected.ID = ItemID
            )
        }
    );
    If(
        ctxPrevcartAdd.Qty > 0,
        Patch (
            colMyOrder,
            ctxPrevcartAdd,
            {Qty: Value(Details_QtyTxt.Text) + ctxPrevcartAdd.Qty}
        ),
        Collect(
            colMyOrder,
            {
                ItemID: galProducts.Selected.ID,
                Qty: Value(Details_QtyTxt.Text),
                Title: galProducts.Selected.'Item Name'
            }
        )
    );

 
I looked up the Company Store SharePoint List and the "ID" column name is correct (as seen in the attachment).

I tried the following with your advice but still no dice:

ItemID = colMyOrder[@ItemID]
&
colMyOrder[@ItemID] = galProducts.Selected.ID
&
galProducts.Selected.ID = colMyOrder.ItemID


Any thoughts?
Cheers

I added a Label to the GalProducts Gallery with the Item ID called "Item_ID_Lbl".
I tried doing this and still no dice...

galProducts.Selected.Item_ID_Lbl = colMyOrder[@ItemID]

@axt3641 

Thank you for providing the additional code.  More code is usually helpful but in this case I cannot see how it ties back to the original problem.  🤔

 

Let me make sure I understand the purpose of these things :

  • myOrders -  this Collection holds one record for each Order.  A record may only contain 1 type of product but the quantity can be multiple units. 
  • 'Company Store' - this SharePoint list contains one record for each Product and the quantity remaining.

 

We need some way to link these two tables together so the FORALL + PATCH can update all the products in 'Company Store'.  Is there any "Product ID" stored in myOrders that can be used to reference the ID of the Item in 'Company Store'?  I believe this is what we need to get the app working.

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

 

Absolutely. Please see my text in red:

Let me make sure I understand the purpose of these things :

  • myOrders -  this Collection holds one record for each Order.  A record may only contain 1 type of product but the quantity can be multiple units. 
    Correct. Whenever someone adds something to the Collection, it'll capture the following:
    - Title which is the Item Name
    - Qty which is the Quantity
    - ItemID which is should be the item ID!

    In the Patch, I used this to set the ItemID:
    ItemID: galProducts.Selected.ID
    (this appears to be working. I attached a screenshot of the collection after I added a few images to ItemID)

  • 'Company Store' - this SharePoint list contains one record for each Product and the quantity remaining.
    The Company Store is a SharePoint List that I have that has a list of all the different inventory items. This list has:
    ID
    Item Name
    Inventory number  and a handful of other items

It would seem the ItemID in the colMyOrders should match up exactly with the SharePoint CompanyStore's ID field!
For some reason it doesn't seem to like it when I call the ItemID (maybe because I'm missing something after it)?
I tried adding a label call ItemId_Lbl.Text on the Gallery too but it's still not playing nice hah

@axt3641 

I very much appreciate the screenshots of your collections.  I wish every forum poster was as generous as you!

 

Here's an updated idea from me.  I believe the 2nd argument to PATCH will work.  I also rewrote the 3rd argument to deduct the Qty from the current inventory amount.  Lets see if you can adapt it to your app.

 

ForAll(
    colMyOrder,
    Patch(
        'Company Store',
        ID = colMyOrder[@ItemID],
        {'Inventory': LookUp('Company Store',ID=colMyOrder[@ItemID],'Inventory') - Qty}
    )
);

 

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

You are the man, Mr.Devaney! I'll give it a go and will update you shortly.
Hope you have a great New Year in the interim 🙂

Hey Mr.D,
We should be good to go! I made a few quick modifications from the code that you sent me with some inspiration from IWMentors:

ForAll(
colMyOrder,
Patch(
'Company Store', {ID: ItemID},

{'Inventory (Inventory0)': Value(LookUp('Company Store', ID = ItemID, 'Inventory (Inventory0)')) - Qty}
)
);

We are good to go amigo! Quick question... It seems like the difference changer was a semi colon in the 2nd Patch Condition:
{ID: ItemID}. Any thoughts on why this worked and not our initial "=" code?

@axt3641 

Interesting.  I have not seen that syntax for the 2nd argument before.  You can bet that I am going to look into it though!  If I figure it out I will post back here 🙂

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