cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Patch person from SP List back to SP List

Hi all

 

I would like to patch a person back to the same SP List but I always get an error. In the DefaultSelectedItems of the dropdown I took ThisItem.Owner. For the Items I took: Office365Users.SearchUser({searchTerm:DataCardValue3.SearchText,top:10}) and in the OnChange properties I took: 

UpdateContext({locSelectedUserEmail: Lower(First(DataCardValue3.SelectedItems).Mail),
locSelectedUserDisplayName: First(DataCardValue3.SelectedItems).DisplayName})

 

My Patch function it looks like this:

Owner: {

'@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpanderUser",
Claims: "i:0#.f|membership|" & locSelectedUserEmail,
Department: "",
DisplayName: locSelectedUserDisplayName,
Email: locSelectedUserEmail,
JobTitle: ".",
Picture: "."
},

 

I guess it has something to do with my DefaultSelectedItems property of the Dropdown but I'm actually stuck now.

 

Any idea?

Thanks a lot!

Best

Lukas

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

@WarrenBelz 

Thanks again!

But did not work as well.

 

I did a workaround with a toggle switch. When there is a new owner, the user has to toggle the switch and select the new one. If there is no new owner it doesn't patch anything.

 

Best

Lukas

View solution in original post

14 REPLIES 14
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous ,

Firstly get rid of the OnChange as it will not trigger unless something is changed - if the Items is

Office365Users.SearchUser(
    {
        searchTerm: Self.SearchText,
        top: 10
    }
)

the Combo Box is Single select with Searching enabled, the DefaultSelectedItems is

ThisItem.Owner

then a Patch of

Owner: 
{
   '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpanderUser",
   Claims: "i:0#.f|membership|" & Lower(DataCardValue3.Selected.Mail),
   Department: "",
   DisplayName: DataCardValue3.Selected.DisplayName,
   Email: DataCardValue3.Selected.Mail,
   JobTitle: ".",
   Picture: "."
}

should work (and does on a test I did here)

 

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.

MVP (Business Applications)   Visit my blog Practical Power Apps

Anonymous
Not applicable

Hi @WarrenBelz 

 

Thanks for your help! I still get an erorr.

I attached the properties of my ComoBox and the patch function of the owner.

The error I get is: Requested operation is invalid.

 

Thanks again!

Best

Lukas

Hi @Anonymous ,

Firstly, please post all code as Text - saves re-typing - for a test, try this

Patch(
   Assets,
   {ID: Galleryl.Selected.ID},
   {
      Barcode: Label_2.Text,
      Title: TextInput1_1.Text,
      Owner: 
      {
         '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpanderUser",
         Claims: "i:0#.f|membership|" & Lower(DataCardValue3.Selected.Mail),
         Department: "",
         DisplayName: DataCardValue3.Selected.DisplayName,
         Email: DataCardValue3.Selected.Mail,
         JobTitle: "",
         Picture: ""
      }
   }
)

 

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.

MVP (Business Applications)   Visit my blog Practical Power Apps

 

Anonymous
Not applicable

 

Hi @WarrenBelz 

Sorry for sending picture instead of text.

I copied you the whole Patch function. It's not working like this.

// show the spinner
    UpdateContext({locShowSpinner: true});
    Patch(
        Assets,
        //Gallery1.Selected,
        {ID: Gallery1.Selected.ID},
        EditForm1_2.Updates,
        {
            Barcode: Label2_2.Text,
            Title: TextInput1_1.Text,
            Owner: {
                '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpanderUser",
                Claims: "i:0#.f|membership|" & Lower(DataCardValue3.Selected.Mail),
                Department: "",
                DisplayName: DataCardValue3.Selected.DisplayName,
                Email: DataCardValue3.Selected.Mail,
                JobTitle: ".",
                Picture: "."
            },
            Category: {
                '@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
                Value: Dropdown1_1.Selected.Value
            },
            Maintain: DataCardValue1_4.SelectedDate,
            'Additional Info': DataCardValue6.Text,
            Location: {
                '@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
                Value: Dropdown3_1.Selected.Value
            },
            Status: {
                '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
                Id: 1,
                Value: "Available"
            }
        }
    );
    
// hide the spinner
UpdateContext({locShowSpinner: false});
    
//Navigate(ConfirmScreenAdmin);
UpdateContext({ShowPopupReset: false});
    Notify(
        "Changes have been saved successfully",
        Success
    );
    Navigate(BrowseScreen1
)

 

 

Thanks a lot!

Best

Lukas

@Anonymous ,

Did you test what I sent you - I am trying to isolate the issue. The properties of the Combo Box should not affect this as you are patching directly the item selected (I assume you have selected this before you patch).

Anonymous
Not applicable

@WarrenBelz 

 

Yes, I copied your code into mine.

Actually I don't select the User actively, because with "ThisItem.Owner" it's taken directly from the SP list.

 

Best

Lukas

@Anonymous ,

I am talking about the abbreviated code - I am trying to isolate the issue - if you do this, does it work ?

Patch(
   Assets,
   {ID: Galleryl.Selected.ID},
   {
      Owner: 
      {
         '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpanderUser",
         Claims: "i:0#.f|membership|" & Lower(DataCardValue3.Selected.Mail),
         Department: "",
         DisplayName: DataCardValue3.Selected.DisplayName,
         Email: DataCardValue3.Selected.Mail,
         JobTitle: "",
         Picture: ""
      }
   }
)

 

Anonymous
Not applicable

@WarrenBelz 

 

No. I've tried the abbreviated code only but also didn't work. It works if I change the owner in the dropdown, but if I didn't change anything it doesn't work.

@Anonymous ,

Interesting as it works on my test whether you change the value or not - try going the "long way" with the DefaultSelectedItems

{
   '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpanderUser",
   Claims: "i:0#.f|membership|" & Lower(ThisItem.Owner.Email),
   Department: "",
   DisplayName: ThisItem.Owner.DisplayName,
   Email: ThisItem.Owner.Email,
   JobTitle: ".",
   Picture: "."
}

 

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.

MVP (Business Applications)   Visit my blog Practical Power Apps

 

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