basixally on the sign out , I would like a dropdown which it gets from the ‘staffwhosin’ list of staff that have already signed in - then pick the name from the dropdown on the ‘sign out’ screen , they would then press ‘sign out’ button , function would then find the record in the ‘staffwhosin’ then put a date and time in the ‘sign out’ column next to the name selected from the dropdown.
can anyone help plesse with code
Solved! Go to Solution.
Hi @poweractivate , I have tried the code, on signin and sigout button, and i cant get it to work, would you be able to assist?
are we having issues becuse the 'Employee' feild is coming from a lookup on another SP list
The StaffWhosIn list - the 'Employee' this is from a lookup called 'StaffNames' so the staffnames are entered in this list and this is what populates the 'Employee' dropdown on the Staff Sgin Screen.
Would the code still be okay for the signout botton, run checks etc, then populate the 'SignOut' column in the 'Staffwhosin' SP list?
Please can you guide me to fix, as its quite urgent
Thanks
@AndyPowerAppNew You can do that if you want but you can't use User().FullName then and you lose the convenience of not having to implement functionality just for them to type their own name and select it from some list. This is also really prone to user error as they might select someone else's name very easily, and it's not desirable.
It might make more sense if the entries from StaffName matched the value of User().FullName for convenience. If that can't be done, you may have to use the LookUp instead of User() and then implement a whole functionality just so they can type their own name and select it from a list, but it's more difficult to implement, takes unnecessary time, takes unnecessary effort, and introduces a new problem where the user may select a wrong name when signing out. When using User().FullName you avoid this issue.
@AndyPowerAppNew You can check what User().FullName returns in your app. See if it's any different from what's in StaffName. If you know the pattern create a new column in StaffNames list called UserFullName and populate it manually with all the correct values. Then you can just use User().FullName and LookUp(StaffNames,UserFullName= User().FullName) - and you can use a StaffNames record's UserFullName as well as User().FullName interchangeably.
Also check if anything in StaffNames table corresponds with User().Email
Also check if anything in Office 365 connector such as the email address or anything else, even the name, etc.
Then you can use that instead if it matches something in your StaffName List.
It is better to avoid to make a dropdown to select their own name, this introduces a lot of issues and is prone to user error.
@AndyPowerAppNew wrote:
The StaffWhosIn list - the 'Employee' this is from a lookup called 'StaffNames' so the staffnames are entered in this list and this is what populates the 'Employee' dropdown on the Staff Sgin Screen.
Would the code still be okay for the signout botton, run checks etc, then populate the 'SignOut' column in the 'Staffwhosin' SP list?
It's OK but it is prone to user error.
If you want to do it anyway, here's how.
Sign in button OnSelect
With
(
{_myRecord:LookUp
(
StaffWhosIn
,Employee = LookUp(StaffNames, SomeStaffNameColumn = SomeDropDown.Selected.Value)
)
}
,If
(
!IsBlank
(
_myRecord
,If
(
_myRecord.SignedIn
,Notify(_myRecord.Employee & " is already signed in",Error)
,Patch
(
StaffWhosIn
,{
ID: _myRecord.ID
,SignedIn: true
,SignInTimeDate: Now()
}
)
)
,Patch
(
StaffWhosIn
,{
Employee = SomeDropDown.Selected.Value
,SignedIn: true
,SignInTimeDate: Now()
}
)
)
)
)
and then
Sign out button OnSelect
With
(
{_myRecord:LookUp
(
StaffWhosIn
,Employee = LookUp(StaffNames, SomeStaffNameColumn = SomeDropDown.Selected.Value)
)
}
,If
(
!IsBlank
(
_myRecord
,If
(
!_myRecord.SignedIn
,Notify(_myRecord.Employee & " is already signed out",Error)
,Patch
(
StaffWhosIn
,{
ID: _myRecord.ID
,SignedIn: false
,SignOutTimeDate: Now()
}
)
)
,Notify(_myRecord.Employee & " is signed out because they have never signed in",Error)
)
)
)
See if it helps now @AndyPowerAppNew
sorry im not getting this , what do you like me to do here? please may to write the code, and say step by step, do you need anymore info from me, i will be guided by you on this.
@AndyPowerAppNew I gave the formulas above for both the Sign in and Sign out button in most recent response.
Replace any fields or columns that give error with appropriate names.
For example
Employee = LookUp(StaffNames, SomeStaffNameColumn = SomeDropDown.Selected.Value)
SomeStaffNameColumn and SomeDropDown need to be replaced with the appropriate names of the column and dropdown based on your scenario.
Other than this, the formulas I provided should simply work. See if it works @AndyPowerAppNew
Hi @poweractivate , i have replaced all the feilds etc, when i click sign in nothing happens i doesnt get get message etc, nothing in added to the SP lists?
If this way is not good, how would do it?
sent with greatest thanks
Hi @poweractivate , do i need to add any more columns names to my sharepoint list, also if this way isnt ideal how would you suguest, sorry im new to powerapps and the logic
Thanks mate
@AndyPowerAppNew Honestly it's probably easier to just put the Signed In Date Time, Signed Out Date Time, and a new SharePoint column called SignedIn it should be a Yes/No column (with just two options Yes and No, with a default value of false, or No) directly in the StaffNames Table. Since the way you have the data modeled you don't really need a separate List here.
Then rewrite the Patches like this:
Sign in button OnSelect
Set(var_mySelectedValue,EmployeeDropDown.Selected.Value);
If
(
IsBlank(var_mySelectedEmployeeValue)
,Notify("A value for the Employee must be selected from the dropdown",Error)
,With
(
{_myRecord:LookUp(StaffNames,Employee = var_mySelectedEmployeeValue)}
,If
(
!IsBlank(_myRecord)
,If
(
_myRecord.SignedIn
,Notify(_myRecord.Employee & " is already signed in - they must sign out first",Error)
,Patch
(
StaffNames
,{
ID: _myRecord.ID
,SignedIn: true
,SignInTimeDate: Now()
}
)
)
,Notify(var_mySelectedEmployeeValue & " does not exist in StaffNames",Error)
)
)
)
and then
Sign out button OnSelect
If
(
IsBlank(var_mySelectedEmployeeValue)
,Notify("A value for the Employee must be selected from the dropdown",Error)
,With
(
{_myRecord:LookUp(StaffNames,Employee = var_mySelectedEmployeeValue)}
,If
(
!IsBlank(_myRecord)
,If
(
!_myRecord.SignedIn
,Notify(_myRecord.Employee & " is already signed out - they must sign in first",Error)
,Patch
(
StaffNames
,{
ID: _myRecord.ID
,SignedIn: false
,SignOutTimeDate: Now()
}
)
)
,Notify(var_mySelectedEmployeeValue & " does not exist in StaffNames",Error)
)
)
)
See if this works better @AndyPowerAppNew
Hi @poweractivate ,
Sorry im really confused here now,
I would like the staffnames when they signin, to be stored in the 'StaffWhosIn' list, the column are like this:
The 'StaffNames' list would be where i add new staff members, and they will show on the 'signin app' as a dropdown. column format is this:
When they sign in and sign out it would store the dateandtime agaist the name, in the 'StaffWhosin' list.
Im really sorry about this, please can you write for me 🙂 (pray)
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