Hi,
I've been stuck on this for quite some time and almost got it working, but am slightly off. Can someone please help.
I'm currently experiencing an issue when patching into my SharePoint list. It's patching incorrectly and only performing 5 patches (assuming due to my if statement causing this issue).
Currently my app operates like so:
1. You select a staff member from a gallery to provide feedback on the screen "SelectGroupMember". The arrow in the gallery sets a variable here too, so that on the following screen ("FeedbackForm"), that staff member who is being evaluated is carried over. (Refer to PatchIssue1 image/attachment for code and reference of the screen).
2. The arrow on the "SelectGroupMember" screen navigates to the screen"FeedbackForm". This screen allows the staff member to choose an option for feedback on the radio buttons (Refer to PatchIssue2 image/attachment for code and reference of the screen). The code for the patch when clicking the "Submit Form" button is like so:
If(
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit1 = User().Email
)
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
{ID: varGroupMemEd.ID}
),
{
Q1a: Q1Radio.Selected.Value,
UserSubmit1: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit2 = User().Email
)
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
{ID: varGroupMemEd.ID}
),
{
Q1b: Q1Radio.Selected.Value,
UserSubmit2: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit3 = User().Email
)
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
{ID: varGroupMemEd.ID}
),
{
Q1c: Q1Radio.Selected.Value,
UserSubmit3: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit4 = User().Email
)
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
{ID: varGroupMemEd.ID}
),
{
Q1d: Q1Radio.Selected.Value,
UserSubmit4: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit5 = User().Email
)
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
{ID: varGroupMemEd.ID}
),
{
Q1e: Q1Radio.Selected.Value,
UserSubmit5: User().Email
}
)
);
The code patches into the SharePoint list but the issue unfortunately is that the patch occurs ascending across the columns. (Refer to PatchIssue3 image/attachment for SharePoint patching). In the image (PatchIssue3) I've highlighted the errors with red boxes and used arrows to indicate where they should have patched. You can see based on the patching, I patched the users in this order (John Doe -> Susan Young -> Nicola Johnson -> Scott Parker -> James Freeman) and it won't let me do a sixth patch (due to the code - but I think this issue will be mitigated if I can fix the location of the patches).
John Doe's patch entered correctly, however, the following patches should only ever patch in the following columns if the previous columns have been populated with data. Meaning the patches for Susan, Nicola, Scott & James are incorrect and need to go in the same 2 columns where John's patch occurred as these columns are blank (where the arrows are indicating).
Essentially, the patch needs to check if that column for that user is blank, if not patch in the next column (so it should check in order like so: if Q1a&Usersubmit1 is blank, then if Q1b&Usersubmit2 is blank, then if Q1c&Usersubmit3 is blank, then if Q1d&Usersubmit4 is blank, then if Q1e&Usersubmit5 is blank, and only patch on the first encountered blank column). So for example, for John's case, let's say I've provided feedback and then Nicola went to provide feedback to John after me, her patch should go into Q1b & UserSubmit2 as data already exists for Q1a & UserSubmit1 from my patch.
I believe this information is concise and covers all that is needed to know, but I'm happy to edit this post and provide any additional information if it isn't 100% clear.
Solved! Go to Solution.
ok, try this - we were checking for firstname blank before, but what we really should have been checking for was whether the usersubmit1/2/3/4/5 was blank so that it skips to the next one.
I still feel like we could do away with the check for blank on varGroupMemEd.ID as it would then patch a new blank row that wouldn't have an email/firstname/lastname, but let's leave that in there for now and assume you will always have a varGroupMemEd.ID
If(
IsBlank(
//we want to check if the usersubmit1 is blank
//and patch it if it is
LookUp(
CharterProjectSP,
//we want it to patch the column for that selected email address row
// that also matches our groupMemEd ID field
ID= varGroupMemEd.ID
&&
EmailAddress=GalleryName.Selected.Email
).UserSubmit1
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
)
),
{
Q1a: Q1Radio.Selected.Value,
UserSubmit1: User().Email
}
),
IsBlank(
//we want to check if the usersubmit2 is blank
//and patch it if it is
LookUp(
CharterProjectSP,
//we want it to patch the column for that selected email address row
// that also matches our groupMemEd ID field
ID= varGroupMemEd.ID
&&
EmailAddress=GalleryName.Selected.Email
).UserSubmit2
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
)
),
{
Q1b: Q1Radio.Selected.Value,
UserSubmit2: User().Email
}
),
IsBlank(
//we want to check if the usersubmit3 is blank for that email address row
//and patch it if it is
LookUp(
CharterProjectSP,
//we want it to patch the column for that selected email address row
// that also matches our groupMemEd ID field
ID= varGroupMemEd.ID
&&
EmailAddress=GalleryName.Selected.Email
).UserSubmit3
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
)
),
{
Q1c: Q1Radio.Selected.Value,
UserSubmit3: User().Email
}
),
IsBlank(
//we want to check if the usersubmit4 is blank for that email address row
//and patch it if it is
LookUp(
CharterProjectSP,
//we want it to patch the column for that selected email address row
// that also matches our groupMemEd ID field
ID= varGroupMemEd.ID
&&
EmailAddress=GalleryName.Selected.Email
).UserSubmit4
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
)
),
{
Q1d: Q1Radio.Selected.Value,
UserSubmit4: User().Email
}
),
IsBlank(
//we want to check if the usersubmit5 is blank for that email address row
//and patch it if it is
LookUp(
CharterProjectSP,
//we want it to patch the column for that selected email address row
// that also matches our groupMemEd ID field
ID= varGroupMemEd.ID
&&
EmailAddress=GalleryName.Selected.Email
).UserSubmit5
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&&
EmailAddress=GalleryName.Selected.Email
)
),
{
Q1e: Q1Radio.Selected.Value,
UserSubmit5: User().Email
}
)
);
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Hey @DarkShadows117
Could you try using this - we replace the ID section with an actual lookup to a record, and then we do the IsBlank checks against an actual specified column value (this prevents Power Apps guessing which column in the lookup it should be checking for a blank, as a record can have multiple columns)
If(
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit1 = User().Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
)
),
{
Q1a: Q1Radio.Selected.Value,
UserSubmit1: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit2 = User().Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
)
),
{
Q1b: Q1Radio.Selected.Value,
UserSubmit2: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit3 = User().Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
)
),
{
Q1c: Q1Radio.Selected.Value,
UserSubmit3: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit4 = User().Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
)
),
{
Q1d: Q1Radio.Selected.Value,
UserSubmit4: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit5 = User().Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
)
),
{
Q1e: Q1Radio.Selected.Value,
UserSubmit5: User().Email
}
)
);
Cheers,
Sancho
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Hey @iAm_ManCat,
I really appreciate the response. But, I just tried out the provided code and it unfortunately patches the same as before encountering the same issues. Any other ideas?
Based on your code, this should only happen if
varGroupMemEd.ID
is blank
what is the value for varGroupMemEd.ID?
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
@iAm_ManCat, so in the SharePoint list all the data for First Name, Last Name & email are prefilled. However, the 10 columns, being Q1x and UserSubmitx, are blank.
varGroupMemEd.ID is used to the patch the selected user from the previous screen.
Does this make sense and/or are there any issues with this?
Sorry I meant what is the value for varGroupMemEd.ID at the point that you are patching? because it looks like its trying to patch all different rows, instead of one singular row where ID = varGroupMemEd.ID
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
@iAm_ManCat Ahh right, my apologies. I hope this makes sense. So, the value for the patch is one of the 4 options in the radio button (refer to PatchIssue2). It is technically patching different rows, as each user is a different row in the SP list.
To provide some insight into the process:
Let's say I am the user providing feedback to the 6 different people in my team, I run through that same form 6 times executing the same patch function for each different user. So I would choose the 1st person and provide feedback (patch the selected radio button), then it reverts back to the previous screen where I choose the next person and do the same thing, until each person has been been provided with feedback.
Ok, so we don't have anywhere in our patch that defines what the row is when we are checking so it will jump to the next column for each as its looking at the first row it find with a value in the first then assuming we now must be dealing with the second question Q1b etc etc
If(
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit1 = User().Email
//we want it to patch the column for that selected email address
&&
EmailAddress=GalleryName.Selected.Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
)
),
{
Q1a: Q1Radio.Selected.Value,
UserSubmit1: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit2 = User().Email
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
)
),
{
Q1b: Q1Radio.Selected.Value,
UserSubmit2: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit3 = User().Email
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
)
),
{
Q1c: Q1Radio.Selected.Value,
UserSubmit3: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit4 = User().Email
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&& EmailAddress=GalleryName.Selected.Email
)
),
{
Q1d: Q1Radio.Selected.Value,
UserSubmit4: User().Email
}
),
IsBlank(
LookUp(
CharterProjectSP,
UserSubmit5 = User().Email
//we want it to patch the column for that selected email address
&&
EmailAddress=GalleryName.Selected.Email
).FirstName
),
Patch(
CharterProjectSP,
If(
IsBlank(varGroupMemEd.ID),
Defaults(CharterProjectSP),
LookUp(
CharterProjectSP,
ID= varGroupMemEd.ID
//we want it to patch the column for that selected email address
&&
EmailAddress=GalleryName.Selected.Email
)
),
{
Q1e: Q1Radio.Selected.Value,
UserSubmit5: User().Email
}
)
);
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
@iAm_ManCat you bloody legend! You've done it!
Thank you so very much man. I really appreciate all the time and effort you put into helping me with this conundrum. Wish I could do more than kudos and accept as solution. Seriously, thanks again!! 😁
Sorry to be the bearer of bad news. But there actually is still one issue. The patch is overriding data.
For example, I patched Q1a and UserSubmit1 with my email. Then tested it with a second email and it patched straight over my submission from my primary email overwriting Q1a and UserSubmit1 (when it should patch to Q1b and UserSubmit 2). Do you know why this would be happening @iAm_ManCat??
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