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.
@poweractivate, what do i replace Title= the name from sharepoint list (StaffWhosIn) where do i store the email address for users, i stillcant get it working , and i also need staff out function too.
what am not doing here?
@poweractivate, this is what my feilds look like in my SP list?
So the code should work? what feilds do my form need to have on the form ?
Thanks
//OnVisible SigninScreen
Set(var_myEmpName,User().Email);
//OnSelect Sign In Button
With
(
{_myRecord:LookUp(StaffWhosIn,Title=var_myEmpName)
,If
(
!IsBlank(_myRecord)
,If
(
_myRecord.SignedIn
,Notify(_myRecord.Name & " is already signed in - they must sign out first",Error);
Navigate(SignOutScreen)
,Patch //change the existing record to signed in
(
StaffWhosIn
,{
ID: _myRecord.ID
,SignedIn: true
,SignInTimeDate: Now()
}
);Notify(var_myEmpName & " has signed in!",Success);Navigate(SignOutScreen)
)
,Patch //create new record if not existing yet and set it to signed in
(
StaffWhosIn
,{
Name=var_myEmpName
,SignedIn: true
,SignInTimeDate: Now()
}
);Notify(var_myEmpName & " has signed in for the first time!",Success);Navigate(SignOutScreen)
)
)
//OnSelect Sign Out Button
With
(
{_myRecord:LookUp(StaffWhosIn,Title=var_myEmpName)
,If
(
!IsBlank(_myRecord)
,If
(
!_myRecord.SignedIn
,Notify(_myRecord.Name & " is already signed out - they must sign in first",Error);
Navigate(SignInScreen)
,Patch //change the existing record to not signed in
(
StaffWhosIn
,{
ID: _myRecord.ID
,SignedIn: false
,SignOutTimeDate: Now()
}
);Notify(var_myEmpName & " has signed out!",Success);Navigate(SignInScreen)
)
,Notify(var_myEmpName & " does not exist in the table / is not signed in",Error);
Navigate(SignInScreen)
)
)
The formulas above may need to be adjusted.
It is also possible to make improvements on the above.
I'm not available for the moment any further @AndyPowerAppNew , if any one wants such as @iAm_ManCat @BCBuizer @WarrenBelz or any one else they could continue it, but in case you still have any issue @AndyPowerAppNew you should figure it out for yourself, or maybe someone else could help you if they are available.
Hi @poweractivate , this is what sign in form looks like i have added code on onsubmit button, it errors
@AndyPowerAppNew Check if formulas I gave in my most recent response work.
You don't need anything on the form at all other than the Sign in button.
You don't even need a form actually, since these formulas are using Patch.
Since the formulas are using Patch the Remote Working control doesn't have to be in a Form.
If you want to use your Remote Working control you need to reference it in the Patch formulas for Sign In, such as YourAppropriateColumn:YourControlName.YourAppropriateProperty
but focus first just on getting it to work without this control, then you can try adding it in after you got it to work without it first and just with the Sign in button and sign out buttons by themselves.
I changed the formulas again now in my recent post but that is all, and you should try to adjust the formulas so they work for you. You can check the notifications and check the SharePoint List to see if it is working or not.
You'll need to figure it out from here how to do it yourself now @AndyPowerAppNew or maybe someone else could help you if they are available and willing to do it.
Hi @poweractivate , one quick question, if we also have a signin button on the form, so are different meant to signin how will the system know this , and feed back to SP list - is there anyone else you know how can help ?
Hello, wonder if anyone can help again, i have made an sign-in/out staff/employee app, but i can the signout to work, this would be the signout screen,
The dropdown list above would be populated from the sharepoint list when users have signed in, they selecte their name from the dropdown press the button, it then fills in the date/time in the empy column again their name that is already in the list (because they signed in)
This is my SP list.
so, it would keep the record above, but just update the 'SignOutTimeDate' column, when user clicks button on form.
update; i have tried this
Where am i going wrong?
Thanks
Hello,
Has anyone got any ideas please - im really stuck
I try once more to help you, I just built out the whole app myself and it works for your scenario on my side.
I have a sign in and out functionality which also knows if the person is currently signed in or out, and it works properly when multiple people are using the app at the same time.
I corrected any imperfection in the previous formulas for you, so please follow the below including the screenshots, step by step, and it should work for you.
These are steps to build everything from the List to the whole app.
These steps are different from what I gave before and the formulas are different,
so be sure to follow each step carefully below.
1. Here is how your SharePoint List should look and it should be called MyStaffList.
Go ahead and see the next steps to check the setting for each column.
Title should just be left alone and it should still be called Title for now.
2. Here are the settings for the other columns
2a. SignInDateTime
2b. SignOutDateTime
2c. SignedIn
Make sure the Default value is set to No for the SignedIn column just like in the above screenshot.
Now to build the app:
3. After doing both steps above you have built out the SharePoint List MyStaffList
Add this SharePoint List MyStaffList as data source to a brand new canvas app
When you are done adding the data source it should look like this:
For the next steps from this point, just ignore any errors (if any even appear at all), and do all of the steps all the way through, and there should be no more errors by the time you are done with all the steps below.
4. Now add a few Screens - rename the first one SignInScreen and the next one MainScreen - and the third one BlankScreen
4b. OnVisible of SignInScreen use this formula
Set(var_myEmpName,User().Email)
4c. For best results, now click on BlankScreen from the left side (tree view) and then click on SignInScreen again. This initializes the variable, so you may see results more quickly in the next steps even as you are doing the steps.
5. Now add a Label control and call it SigninStatusLabel1.
For the Text property put this formula:
"Signed In: " & With({_myRecord:LookUp(MyStaffList,Title=var_myEmpName)},If(IsBlank(_myRecord),false,_myRecord.SignedIn))
6. Add another Label Control. Below it's called Label2. I've left the name of the Control alone this time. You can rename it if you want to.
For the text Property of that Label put
var_myEmpName
7. Add a Button. Below it's called Button1. I've left the name of the Control alone this time. You can rename it if you want to.
For the OnSelect of that Button use this formula:
With
(
{_myRecord:LookUp(MyStaffList,Title=var_myEmpName)}
,If
(
!IsBlank(_myRecord)
,If
(
_myRecord.SignedIn
,Notify(_myRecord.Name & " is already signed in - they must sign out first",Error);
Navigate(MainScreen)
,Patch //change the existing record to signed in
(
MyStaffList
,{
ID: _myRecord.ID
,SignedIn: true
,SignInDateTime: Now()
}
);Notify(var_myEmpName & " has signed in!",Success);Navigate(MainScreen)
)
,Patch //create new record if not existing yet and set it to signed in
(
MyStaffList
,{
Title:var_myEmpName
,SignedIn: true
,SignInDateTime: Now()
}
);Notify(var_myEmpName & " has signed in for the first time!",Success);Navigate(MainScreen)
)
)
7b. For the Text property of that Button put
"Sign In"
8. Now go to MainScreen
Add a Label Control. I have left the name as the default, you can rename it if you want to.
For the Text property put:
var_myEmpName
9. Now add a Label control and call it SigninStatusLabel2.
For the Text property put this formula:
"Signed In: " & With({_myRecord:LookUp(MyStaffList,Title=var_myEmpName)},If(IsBlank(_myRecord),false,_myRecord.SignedIn))
10. Now add a Button control
For the OnSelect property put this formula:
With
(
{_myRecord:LookUp(MyStaffList,Title=var_myEmpName)}
,If
(
!IsBlank(_myRecord)
,If
(
!_myRecord.SignedIn
,Notify(_myRecord.Name & " is already signed out - they must sign in first",Error);
Navigate(SignInScreen)
,Patch //change the existing record to not signed in
(
MyStaffList
,{
ID: _myRecord.ID
,SignedIn: false
,SignOutDateTime: Now()
}
);Notify(var_myEmpName & " has signed out!",Success);Navigate(SignInScreen)
)
,Notify(var_myEmpName & " does not exist in the table / is not signed in",Error);
Navigate(SignInScreen)
)
)
10b. For the Text property of that Button put
"Sign Out"
11. Now try the app. If not sure how to try it, check Step 12 below.
The app should know if they are currently signed in or not.
Even if you test the app starting with the MainScreen instead of starting with the SignInScreen it should still work correctly and it knows if they are not signed in, and takes them to the Sign In page, giving a message that they were not yet signed in.
Same is true vice versa - if they are already Signed In, and you intentionally start the app while on the SignInScreen and press Sign In, it should not sign them in again, it should take them to the MainScreen instead, giving a message that they were already signed in.
If you want step by step on how to try it, see the next step.
12. Preview the App (or you can ALT+CLICK if you want to test directly in the Editor)
12a. Click on Sign In.
After you see the green message saying they successfully signed in, go to your SharePoint List and manually check the entry. You should see it as correct - the Sign In Date Time
12b. Click on Sign Out
After you see the green message saying they successfully signed out, go to your SharePoint List and manually check the entry. You should see it as correct - the Sign Out Date Time
13. Repeat Steps 12a and 12b above again.
Notice it's working and it updates the Sign In Date Time, Sign Out Date Time and Sign In Status accordingly to the correct record in the SharePoint List every time.
If you use multiple different users at the same time on this app, it should work correctly for all of them.
14. If you like this solution, go ahead and add in your other columns you had before into this same SharePoint List MyStaffList.
See if it helps @AndyPowerAppNew
P.S.:
I have attached a working sample msapp file SignInOutApp_1.msapp of the full app built out with all formulas.
if you would like to import a full, working example yourself for your convenience.
To use the sample msapp attached, follow these steps:
1) Download the msapp file attached to this post (it's at the bottom of this post), to Desktop or a folder of your choice, by clicking on it from this post.
2) Create a new, blank Power App Canvas App
3) Click on the three dots / ellipses (just to the right of Settings)-> then from the menu that appears, click Open
4) Click Browse
5 ) Navigate to location of .msapp file from Step 1, select it, and press the "Open" button.
6 ) The working example msapp file should load
7) There will be errors showing up. So now you need to add the data source MyStaffList.
Follow the instructions at the top of this post to build out the SharePoint List from scratch.
See if this helps as well @AndyPowerAppNew
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