I have created a PowerApp to run our Service Desk Tickets through a Teams PowerApp. Everything is working as expected at the moment except for adding a user to an incident as an "Assigned To" field.
In SharePoint the Data Type is User or Group and I have the drop down looking up the "Technology Team" Security Group to give a list of available users. It is when patching the user to the record in SharePoint that doesn't seem to be working. The patch script is below. Can anyone point me in the right direction to get this to patch as a user account against the SP List please?
Patch(
Incidents,
varListItem,
{
Comments: newComments.Text,
AssignedTo: {'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
ODataType: Blank(),
Claims:Concatenate("i:0#.f|membership|",User().Email),
DisplayName:User().FullName,
Email:User().Email,
Department:"",
JobTitle:"",
Picture:""
},,
Status: IncidentStatus.Selected.Value
}
);
Reset(newComments);
Reset(incAssignedTo);
Reset(IncidentStatus);
Navigate(scrListView,ScreenTransition.CoverRight);
Solved! Go to Solution.
I have managed to resolve the problem by changing how to select the User to assign to the incident. The drop down box needed to be changed to a Combo Box and then lookup the field in SharePoint (where I created a new User Group in the Site for Service Desk Admins to be able to select the correct users).
When changing the Patch Command to "assignedTo: AssignedToCombo.Selected" it then showed no further errors and allowed the patching to the SharePoint Library.
Thank you @WarrenBelz and @Jon_Unzueta for your help in this,
Hi @PeterMurphy ,
Please start with this standard structure
Patch(
Incidents,
{ID: varListItem.ID},
{
Comments: newComments.Text,
AssignedTo:
{
'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Claims: "i:0#.f|membership|" & Lower(User().Email),
DisplayName: User().FullName,
Email: User().Email,
Department: "",
JobTitle: "",
Picture: ""
},
Status: IncidentStatus.Selected.Value
}
);
Reset(newComments);
Reset(incAssignedTo);
Reset(IncidentStatus);
Navigate(scrListView,ScreenTransition.CoverRight);
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
Thanks for your help in this, truly appreciated,
On updating the patch script I get the error of "Invalid Argument Type: Expecting a record value, but of a different schema"
This one is definitely stumping me and searching 4th Line Support (Google) shows a million different ways to do the same thing and it's tough to work out the right way on this one.
Hello @PeterMurphy
I don't understand you well, the problem is that you can't save the assigned user?
the drop down menu filter, do you do it in the app or in SPO?
Apologies, On the form I am using the Office365Groups Connector to Filter to the Technology Team Group to give me a list of users available to be assigned to the Incident in SharePoint. I am then trying to use the Office365Users connector to patch this into SharePoint as the selected user.
There are only 3 fields to patch information to in this form, which is a notes field, assigned user field and status field.
Hi @PeterMurphy ,
There are two possibilities here that I see - assuming your 'Assigned to' field is a Person column, you have set it to allow multiple selections or Status is a Choice column. If the second you need
Status: {Value: IncidentStatus.Selected.Value}
or simply
Status: IncidentStatus.Selected
Hi,
It is from a Drop Down Box and I am using this in the Items entry:
Office365Groups.ListGroupMembers("45e09b0e-9fa7-4719-906c-7d2e45889699").value
This pulls the members from the Office365Group and displays the displayName field in the drop down list.
Would this need to be changed to a Combo Box?
Hi @PeterMurphy ,
The Items of the Combo Box is totally irrelevant here as you are not using it in the Patch - you are using the current logged in user's credentials. The issue is the field type you are patching it to - can you please confirm that 'Assigned To' is a single select Person column in your SharePoint list.
Hi @WarrenBelz
The field settings are set to "Person or Group" and Allow Multiple Selections is switched off against this.
Hi @PeterMurphy ,
Some debugging required here as the below is the "out of the book" structure for patching a Person field
Patch(
Incidents,
{ID: varListItem.ID},
{
AssignedTo:
{
'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Claims: "i:0#.f|membership|" & Lower(User().Email),
Department: "",
DisplayName: "User().FullName,
Email: User().Email,
JobTitle: "",
Picture: ""
}
}
);
Please indulge me in a suspicion here - remove the other two fields and see if AssignedTo patches on its own as above
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