I'm working on the leave balance template and I have changed the data source to sharepoint. Everything works as expected except when a leave request is approved, the balance does not update to reflect the change, for example I made a request for vacation and had it approved. It is supposed to update the "vacation used" portion when the request is approved.If i enter it manually from the list the change is reflected on the app.
This is the code used on the approver button
Concurrent(
Set(_submittingRequest, true),
//when approving leave, add the respective days used to the respective used days field
Patch(Balance, LookUp(Balance, BalanceID = _requesterBalanceRecord.BalanceID),
If(Upper(GalleryRequests.Selected.LeaveType) = Upper("Vacation"), {VacationUsed: _requesterBalanceRecord.VacationUsed + _requestedDays},
Upper(GalleryRequests.Selected.LeaveType) = Upper("Sick leave"), {SickUsed: _requesterBalanceRecord.SickUsed + _requestedDays},
Upper(GalleryRequests.Selected.LeaveType) = Upper("Floating holiday"), {PersonalUsed: _requesterBalanceRecord.PersonalUsed + _requestedDays},
Upper(GalleryRequests.Selected.LeaveType) = Upper("Jury duty"), {JuryDutyUsed: _requesterBalanceRecord.JuryDutyUsed + _requestedDays},
Upper(GalleryRequests.Selected.LeaveType) = Upper("Bereavement"), {BereavementUsed: _requesterBalanceRecord.BereavementUsed + _requestedDays}
)
),
Set(_managerApprove, true));
Patch(Leave, LookUp(Leave, LeaveID = GalleryRequests.Selected.LeaveID), {Status: "Approved"});
Set(_submittingRequest, false);
Navigate(ManagerChangeRequestScreen, BorderStyle.None);
I made a previous topic on this but I'm not sure I was very clear about the issue I'm having. Previous topic
I'm new here to the forum so I'm not certain how I would go about deleting my old post or updating it, just wanted to clarify the issue.
I attempted adding an altered version of the code: But it did not change. All permissions on sharepoint are set so that a user can edit the form when created by another user so it should be updated. Is there something I'm missing ?
Concurrent(
Set(_submittingRequest, true),
// when approving leave, add the respective days used to the respective used days field
Patch(
Balance,
LookUp(Balance, BalanceID = _requesterBalanceRecord.BalanceID),
{
VacationUsed: If(
Upper(GalleryRequests.Selected.LeaveType) = Upper("Vacation"),
_requesterBalanceRecord.VacationUsed + _requestedDays,
_requesterBalanceRecord.VacationUsed
),
SickUsed: If(
Upper(GalleryRequests.Selected.LeaveType) = Upper("Sick leave"),
_requesterBalanceRecord.SickUsed + _requestedDays,
_requesterBalanceRecord.SickUsed
),
PersonalUsed: If(
Upper(GalleryRequests.Selected.LeaveType) = Upper("Floating holiday"),
_requesterBalanceRecord.PersonalUsed + _requestedDays,
_requesterBalanceRecord.PersonalUsed
),
JuryDutyUsed: If(
Upper(GalleryRequests.Selected.LeaveType) = Upper("Jury duty"),
_requesterBalanceRecord.JuryDutyUsed + _requestedDays,
_requesterBalanceRecord.JuryDutyUsed
),
BereavementUsed: If(
Upper(GalleryRequests.Selected.LeaveType) = Upper("Bereavement"),
_requesterBalanceRecord.BereavementUsed + _requestedDays,
_requesterBalanceRecord.BereavementUsed
)
}
),
Set(_managerApprove, true)
);
Patch(Leave, LookUp(Leave, LeaveID = GalleryRequests.Selected.LeaveID), {Status: "Approved"})
Set(_submittingRequest, false);
Navigate(ManagerChangeRequestScreen, BorderStyle.None);
Solved! Go to Solution.
Hi @Universal_Power ,
It will update whatever record you used in your Lookup
LookUp(
Balance,
BalanceID = _requesterBalanceRecord.BalanceID
)
so which field in Balance matches the field in the gallery to match ?
Hi @Universal_Power ,
Try this format
Set(_submittingRequest, true);
With(
{
_Data:
LookUp(
Balance,
BalanceID = _requesterBalanceRecord.BalanceID
)
},
Patch(
Balance,
{ID: _Data.ID},
Switch(
Upper(GalleryRequests.Selected.LeaveType),
"VACATION",
{VacationUsed: _Data.VacationUsed + _requestedDays},
"SICK LEAVE",
{SickUsed: _Data.SickUsed + _requestedDays},
"FLOATING HOLIDAY",
{PersonalUsed: _Data.PersonalUsed + _requestedDays},
"JURY DUTY",
{JuryUsed: _Data.JuryUsed + _requestedDays},
"BEREAVEMENT",
{BereavementUsed: _Data.BereavementUsed + _requestedDays}
)
)
);
Set(_managerApprove, true)
Patch(
Leave,
LookUp(
Leave,
LeaveID = GalleryRequests.Selected.LeaveID
),
{Status: "Approved"}
)
Set(_submittingRequest, false);
Navigate(
ManagerChangeRequestScreen,
BorderStyle.None
);
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
@WarrenBelz Thanks, I tried it and it updated, but it didn't create a record specific to me (the user).The yellow is the record it created and the blue is where it was supposed to go, to a specific user (the one who sent the request)
Hi @Universal_Power ,
It will update whatever record you used in your Lookup
LookUp(
Balance,
BalanceID = _requesterBalanceRecord.BalanceID
)
so which field in Balance matches the field in the gallery to match ?
@WarrenBelz So I'm fairly new to power apps so bare with me a bit, The BalanceID field in my Balance sheet is automatically pulled from office365 users(which is matched in the gallery), so my BalanceID is my email and the date it was created which was auto generated upon logging into the leave app. What I'm seeing is that it's not pulling my specific balanceID but rather creating a blank balance ID and it's creating a "new" instance of it without the o365 data in the balance sheet.
OK - I will ask the question another way - which field here is a unique record identifier and is present in (I assume a Record Variable) RequestorBalanceRecord
@WarrenBelz Okay I checked the global variables for RequesterBalanceRecord and In home screen on visible there's a lookup function similar to the one you wrote out where it pulls the record from the o365 profile, to me it looks like it's setting the Requesterbalancerecord variable using the _myprofile information ? Or could the unique identifier be employeeEmail? Below is a snippet of it;
Concurrent(
Set(_navMenuSelect, "My Leave Requests"),
//if not manager view, refresh my balance collection when on this screen
If(!_managerView, Set(_requesterBalanceRecord, LookUp(Balance, Year = Text(Year(Now())) && EmployeeEmail = _myProfile.UserPrincipalName));
ClearCollect(RequesterBalanceCollection,
{ type: "Vacation", balance: Value(_requesterBalanceRecord.Vacation) - Value(_requesterBalanceRecord.VacationUsed)},
{type:"Sick Leave", balance:Value(_requesterBalanceRecord.Sick)-Value(_requesterBalanceRecord.SickUsed)},
{type:"Personal", balance:Value(_requesterBalanceRecord.Personal)-Value(_requesterBalanceRecord.PersonalUsed)},
{type:"Jury Duty", balance:Value(_requesterBalanceRecord.JuryDuty)-Value(_requesterBalanceRecord.JuryDutyUsed)},
{type:"Bereavement", balance:Value(_requesterBalanceRecord.Bereavement)-Value(_requesterBalanceRecord.BereavementUsed)},
{type:"Paternity", balance:Value(_requesterBalanceRecord.Paternity)-Value(_requesterBalanceRecord.PaternityUsed)},
{type:"Bereavement", balance:Value(_requesterBalanceRecord.Study)-Value(_requesterBalanceRecord.StudyUsed)}
,
Set(_showDetails, false)
)));
To answer your question directly there is no field on the sharepoint list that directly correlates to requesterbalancerecord. Also all other uses of the global variable requesterbalancerecord only displays there is no "set" function.
The underlying issue is that you cannot update a record in a data source without referring to a field it it to identify which record to update. If it is not a unique identifier (there are other records with the same value in the field), you may update the wrong record, but you can update them all if you want to.
So in short, is the employee email this relevant field and if so, is this value contained in varRequestorRecord or alternatively is there a list somewhere that contains both the email address and also the corresponding BalanceID for that employee ?
If there is no field (as you noted) that correlates, then there is no way to identify which record to update and you need to revise your data structure so that this exists.
@WarrenBelz Sorry for the delayed response, I've been off for a little. I took the time today to try to understand what's going on. I know now that the patch function is updating the balance data source based on the identifier _Data which is the variable that was set using balanceID=_requesterBalanceRecord.BalanceID.
With that being said, to answer your question, the employee email is not the relevant field, there is infact a unique BalanceID field within the data source. I believe that the requesterBalanceRecord is where the issue lies. Is it that this variable was not correctly defined ?
For reference to all of this, I am using this from github where this person created the sharepoint connection to the leave app. https://github.com/powerappstim/leaverequest
That is the first thing that was posted and you said it was not correct. I also cannot see BalanceID in the screenshot of your list below
One of these fields (I suspect EmployeeEmail or EmployeeName ) needs to be used to identify the correct record to Patch (unless there are other fields in the list you have not included above), so you simply need to retrieve that somewhere from the data you are using.
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