cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Siddz
Helper IV
Helper IV

Patching a SharePoint List from a Collection

I have a canvas new-employee on-boarding checklist app connected to three SharePoint lists: Employees, Checklist, and Responses.

 

SharePoint-Lists.jpg

The Process:
1. The supervisor or the on-boarder clicks an employee's name in GalleryEmployees on Screen1 and navigates to Screen2, which displays GalleryChecklist
2. GalleryChecklist is filtered to display the checklist items for the logged-in user
3. The supervisor or the on-boarder chooses "Yes" or "No" in Dropdown1 for each checklist item and clicks the "Save" icon
4. The "Save" icon patches the "Yes/No" values to the Responses SharePoint list for the selected employee

 

 

The Structure:

App > OnStart:

// Store checklist items from Checklist SharePoint list
Set(colChecklistList, Checklist);

Screen1 > GalleryEmployees > Items:

// Display the list of employees from the Employees SharePoint list
Employees

GalleryEmployees > Icon > OnSelect:

// Store the selected employee's record
Set(varEmployee, ThisItem); Navigate(Screen2)

Screen2 > OnVisible:

// Add an "Answer" column to the collection to store the "Yes/No" value from Dropdown1
ClearCollect(colChecklist, AddColumns(ShowColumns(colChecklistList, "ID", "Title", "Category"), "Answer", "No"));

GalleryChecklist > Items:

// Filter gallery to only show checklist items based on the current user's role (either supervisor or on-boarder from Employees list)
If(varEmployee.Supervisor.Email = User().Email, Filter(colChecklist, Category.Value = "Supervisor"),
If(varEmployee.Onboarder.Email = User().Email, Filter(colChecklist, Category.Value = "Onboarder")))

GalleryChecklist > Dropdown1 > OnChange:

// Store "Yes/No" value in the collection based on Dropdown1's selection
Patch(colChecklist, ThisItem, {Answer: Dropdown1.Selected.Value})

GalleryChecklist > Dropdown1 > Default:

ThisItem.Answer

Screen2 > Save Icon > OnSelect:

// Upon saving, patch Responses SharePoint list with "Yes/No" values for selected employee
ForAll(Filter(colChecklist, Category.Value = "Supervisor"), If(Dropdown1.Selected.Value = "Yes",
Patch(Responses, {Title: Answer, ChecklistID: ID, EmployeesID:varEmployee.ID})));

GalleryChecklist.jpg



 

My Questions:

1. Upon saving, how can I patch the "Yes" or "No" values to the Responses list for the selected employee (varEmployee)?

(My current approach adds a new list item (row) each time I click "Save". I'd like to update values if they already exist.)

 

2. If an employee has stored values in the Responses list, how do I retrieve those values and display them in GalleryChecklist?

1 ACCEPTED SOLUTION

Accepted Solutions
EddieE
Super User
Super User

@Siddz 

Firstly, well done for setting out your question with such great detail. This is not often done by those seeking help but it really helps those who wish to help to work out a solution.

 

There's probably a few ways to approach a solution here, but if this was my project I'd do this:

- every time a new Employee is added to the Employees List, I'd run a Flow to grab the CheckList Tasks and create the items needed in the Responses List

- I'd set each of these item responses to 'No' in the above Flow

- then, inside your app, when a person selects an employee from your first gallery the gallery on the next screen could show the responses, ie

With(
   {
     wTasks: Switch( User().Email,
               varEmployee.Supervisor.Email, Filter(Checklist, Category.Value = "Supervisor"), 
               varEmployee.Onboarder.Email, Filter(Checklist, Category.Value = "Onboarder")
             ),
     wResponses: Filter( Responses, EmployeesID = varEmployee.ID )
   },

   Filter(
      wResponses,
      ChecklistID in wTasks.ID
   )
)

 

Then, each time a person selects Yes/No run your OnChange Patch() directly to the Responses List. Also, I cannot fully test the above but I'm pretty sure there won't be any delegation issues use 'in' in that code - could be wrong though ...?

 

To set this up and give it a try, just create all the Responses for a particular person manually then test this code.


If my response solves your question, please accept as a solution.
Thank you!

View solution in original post

10 REPLIES 10
EddieE
Super User
Super User

@Siddz 

Firstly, well done for setting out your question with such great detail. This is not often done by those seeking help but it really helps those who wish to help to work out a solution.

 

There's probably a few ways to approach a solution here, but if this was my project I'd do this:

- every time a new Employee is added to the Employees List, I'd run a Flow to grab the CheckList Tasks and create the items needed in the Responses List

- I'd set each of these item responses to 'No' in the above Flow

- then, inside your app, when a person selects an employee from your first gallery the gallery on the next screen could show the responses, ie

With(
   {
     wTasks: Switch( User().Email,
               varEmployee.Supervisor.Email, Filter(Checklist, Category.Value = "Supervisor"), 
               varEmployee.Onboarder.Email, Filter(Checklist, Category.Value = "Onboarder")
             ),
     wResponses: Filter( Responses, EmployeesID = varEmployee.ID )
   },

   Filter(
      wResponses,
      ChecklistID in wTasks.ID
   )
)

 

Then, each time a person selects Yes/No run your OnChange Patch() directly to the Responses List. Also, I cannot fully test the above but I'm pretty sure there won't be any delegation issues use 'in' in that code - could be wrong though ...?

 

To set this up and give it a try, just create all the Responses for a particular person manually then test this code.


If my response solves your question, please accept as a solution.
Thank you!

Thanks, @EddieE.

 

Using Power Automate and the With() function is an interesting approach I hadn't considered. I may try that route if I can't figure out how to patch properly from a collection to my SharePoint list using ForAll().

 

This method of patching works, but it creates new list items with each patch instead of updating existing items:

// Button > OnSelect
// This works, but it creates new list items with each patch instead of updating existing rows
ForAll(Filter(colChecklist, Category.Value = "Sponsor"),
Patch(Responses, {Completed:Answer, ChecklistID: ID, EmployeesID:varEmployee.ID})) 

However, when I try to update existing values in the "Responses" list, I get the error below ("The requested operation is invalid.")

// Button > OnSelect
// This throws the error below
ForAll(Filter(colChecklist, Category.Value = "Sponsor"),
Patch(Responses, LookUp(Responses, ID = ChecklistID),
{Completed:Answer, ChecklistID: ID, EmployeesID:varEmployee.ID}))

Patch-Error.jpg

 

I'm stuck on how to update existing values when patching from colChecklist to the "Responses" SharePoint list.

@Siddz 

What you can do is add the ID field into your Patch and this will pickup existing records and update them and also add new ones as required, ie

 

// Button > OnSelect
// This works, but it creates new list items with each patch instead of updating existing rows
   ForAll(
      Filter(colChecklist, Category.Value = "Sponsor") As data, 
        Patch(
           Responses,
           {
             ID: data.ID, 
             Completed: data.Answer, 
             ChecklistID: data.ID, 
             EmployeesID: data.varEmployee.ID
           }
        )
) 

 

Note, the structure ForAll( Patch( ... ) ) is slower because it patches one record at a time. The Structure Patch( ForAll( ... ) ) is faster. You won't notice a big difference if your data getting patched is only a few records but for large datasets it can make a difference.

 

I try to use Patch( ForAll( ... )) always now.

 

I've also used 'As' above to ensure there's no confusion (disambiguation) with the ID field, which can sometimes happen when using ForAll().


If my response solves your question, please accept as a solution.
Thank you!

Thanks, @EddieE!

 

I think we're on the right track, but I'm getting an error ("This type of argument does not match...")

 

Argument-Type-Error.jpg

I tried changing "data.varEmployee.ID" to "varEmployee.ID", but that results in this error:

 

Argument-Type-Error-02.jpg

 

I'll keep tinkering with it. Once I get this working, I'll try to implement Patch(ForAll( ... )) to improve efficiency. Thanks for the suggestion!

@Siddz 

Wrap the varEmployee.ID in the Value function, ie

EmployeesID: Value(data.varEmployee.ID)

This is because the ID field from SharePoint looks like a number but really isn't a number ... wrapping it in Value() should convert it for you - hopefully!?

 


If my response solves your question, please accept as a solution.
Thank you!

Thanks, @EddieE.

 

I tried the Value() function earlier, but I got the errors below (different errors depending on where I hovered).

 

I triple-checked the "EmployeesID" and "ChecklistID" columns in the "Responses" list to make sure they were number types, and they are. I even hard-coded the EmployeesID just to test, but "the specified record was not found" (EmployeesID: 16). 

 

Invalid-Error-02.jpgInvalid-Error-01.jpg

@Siddz 

Ah, my bad, I'm trying to do this while distracted ... sorry! varEmployees.ID isn't part of the data table we create, hence the error.

 

Also, I think you'll need to do a Table append to colChecklist as well as a column Renaming to be able to update records. This will be a little more tricky which is why I suggested the Flow + direct access to the Responses, rather than a cobbled together table. It's doable, but I tend to avoid it because it can be problematic


If my response solves your question, please accept as a solution.
Thank you!

Thanks for your help, @EddieE! You gave me a few more ideas to pursue and some great suggestions to improve the app. Much appreciated. 

Thanks, @EddieE!

 

I ended up taking your advice by creating a flow that populates my "Responses" list when a new employee is added to the "Employees" list.

 

The Flow:

  • When an item is created in the "Employees" list
  • Get items from "Checklist" list
  • Create an item in the "Responses" list (this creates an "Apply to each" loop)
  • Map the fields in the "Responses" loop with the corresponding dynamic content fields

 

Back in Power Apps:

Insert a checkbox control in the gallery.

 

Set the OnCheck property to: 

Patch(Responses, ThisItem, {Completed: "Yes"});

Set the OnUnCheck property to: 

Patch(Responses, ThisItem, {Completed: "No"});  

Set the Default property of the checkbox to: 

If(ThisItem.Completed = "Yes", true, false) // Ensures checkbox values are retrieved when returning to the gallery

Thanks again!

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