cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Employee signin/out

  • have a list called 'StaffWhosin' the 'employee' name is a lookup list from 'StaffNames' i can get a signin date time etc, but the signout againist the name, doesnt work, can you help again.

 

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 

53 REPLIES 53

@AndyPowerAppNew The StaffNames List serves no purpose currently since all you have is their name, and you want their name to be duplicated again in StaffWhosIn anyway. You might as well just use StaffWhosIn and just delete StaffNames (but don't delete it until you moved all their names to StaffWhosIn though using copy and paste in SharePoint grid view or the like - and keep it for a while as a backup until you're really sure the app is working with just StaffWhosIn and with all the data moved to StaffWhosIn). 

Try just using StaffWhosIn and pretend its called StaffNames for now.

You don't need a whole List to determine if they're signed in or not, you just need the Yes/No Column in the StaffWhosIn List - not the whole List itself. The extra List serves no purpose, since you're not keeping an audit log currently. If you ever need it later you can probably add it in later anyway, but for now it makes most sense to only use one list.

There's no purpose to have a separate whole List of Who is in just to determine Who is in or not, as that is not the best way to do it.

StaffWhosIn contains the most information so far, that's why I want to use it, I see EvacCheck and other stuff that looks like you might actually use later. StaffNames is pretty much useless as it's just their name, and you have it repeated again in StaffWhosIn anyway and you actually wanted it repeated there. Why not use just the one List to avoid complication? Try to use the formulas I provided and use only the StaffWhosIn List. Ignore for now that it's called StaffWhosIn, that's going to become your Staff List just for now.

 

Take all the Staff from StaffNames and copy it over to StaffWhosIn, it's easy if you use Edit in Grid view or something like that in SharePoint.

Now rewrite the formulas I gave recently only using the  StaffWhosIn List, see if it works better.

 @poweractivate , I think i understand, i will try this, so in 'StaffWhosIn' list at the moment the 'Employee' column is a lookup, so i can delete that, is just use a text feild? if we had extra staff members joining, how would i add these so they are in the system, am i understamding right?

@AndyPowerAppNew Yes you can do that, just use out of the box Title column or just create a new column if you want.

You can use grid view to copy all the names of the employees from StaffNames (probably Title field) to StaffWhosIn (Title Field) as new records, they should all be created with the SignedIn column defaulted to No or false automatically if you created the column correctly in SharePoint - that column SignedIn should be set to have the default value of No or false in SharePoint for the column settings. 

 

Then try like this for the formulas:

 

EmployeeDropdown in the Items property:

StaffWhosIn.Title

 

Sign in button OnSelect property:

 

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(StaffWhosIn,Title= var_mySelectedEmployeeValue)}
	   ,If
		(
			!IsBlank(_myRecord)
			,If
			(
			   _myRecord.SignedIn
			   ,Notify(_myRecord.Title & " 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 the table",Error)
			
		)
	)
)

 

and then

 

Sign out button OnSelect property:

 

If
(
	 IsBlank(var_mySelectedEmployeeValue)
	,Notify("A value for the Employee must be selected from the dropdown",Error)
	,With
	(
		{_myRecord:LookUp(StaffNames,Title = var_mySelectedEmployeeValue)}
	   ,If
		(
			!IsBlank(_myRecord)
			,If
			(
			   !_myRecord.SignedIn
			   ,Notify(_myRecord.Title & " 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 the table",Error)
			
		)
	)
)

 

 

See if this works better @AndyPowerAppNew 

 

Hi @poweractivate , Im so sorry , im really not understand this at all, the code isnt doing anything, how can i proceed past this, could you make a video that i can follow?

poweractivate
Most Valuable Professional
Most Valuable Professional

@AndyPowerAppNew 

 

Actually I have a better, easier idea for you

Don't bother to migrate any Employee Names at all.

Just delete that StaffNames table, who needs it? (or if unsure, get the below working first, then delete it)

Why have a table of names anyway if you can just use User().FullName instead?

Actually, why bother even with the dropdown too? 🙂

Take that entire dropdown out too,

That dropdown where you have to select a name just makes the app a bad experience and prone to error in selecting their own name from a dropdown.

- let's make it a good experience instead and not force the user to bother to select any name from any dropdown since the app already knows it anyway! Why bother with having any list of names anyway? 

Why would someone have to select their own name from some list, possibly select someone else's name by mistake, and waste their time doing an extra step, when their name can already be pre-selected for them with no chance for user error!

 

Just do this

 

Sign in button OnSelect property:

 

With
(
	{_myRecord:LookUp(StaffWhosIn,Title=User().FullName)}
   ,If
	(
		!IsBlank(_myRecord)
		,If
		(
		   _myRecord.SignedIn
		   ,Notify(_myRecord.Title & " is already signed in - they must sign out first",Error)
		   ,Patch
		   (
			  StaffWhosIn
			 ,{
				  ID: _myRecord.ID
				 ,SignedIn: true
				 ,SignInTimeDate: Now()
			  }
		   )
		)
		,Patch
	     (
		    StaffWhosIn
		   ,{
		  	    Title=User().FullName 
			   ,SignedIn: true
			   ,SignInTimeDate: Now()
		    }
	     )
		
	)
)

 

and then

 

Sign out button OnSelect property:

 

If
(
	 IsBlank(var_mySelectedEmployeeValue)
	,Notify("A value for the Employee must be selected from the dropdown",Error)
	,With
	(
		{_myRecord:LookUp(StaffNames,Title = var_mySelectedEmployeeValue)}
	   ,If
		(
			!IsBlank(_myRecord)
			,If
			(
			   !_myRecord.SignedIn
			   ,Notify(_myRecord.Title & " 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 the table",Error)
			
		)
	)
)

 

See if this works better @AndyPowerAppNew 

 

Hi @poweractivate , i tried this , i get this error, nothing happens when i click sign in

AndyPowerAppNew_0-1671536152683.png

how can their name be preseleted, i dont understand, wont they need to pick their name? there are about 50 staff members all using the same system

 

Thanks

 

Andy


@AndyPowerAppNew wrote:

wont they need to pick their name? there are about 50 staff members all using the same system

 

 


No because User().FullName picks their name for them, it's a built in functionality. It will use the name they are signed in with, every person has a name who will be using Power Apps.

If you are not comfortable with their name, such as because two people may happen to have the same full names -  you can instead use their email - User().Email - to put in the Title field - this is almost always unique when using Microsoft 365, I'm not sure of a case where this is not unique per person. 

I am not sure why you got any error, in case I have time I might check on it.

 

 


@AndyPowerAppNew wrote:

wont they need to pick their name? there are about 50 staff members all using the same system

 

 


No because User().FullName picks their name for them, it's a built in functionality. It will use the name they are signed in with, every person has a name who will be using Power Apps.

If you are not comfortable with their name, such as because two people may happen to have the same full names -  you can instead use their email - User().Email - to put in the Title field - this is almost always unique when using Microsoft 365. 

I am not sure why you got any error, in case I have time I might check on it.

 

 

Hi @poweractivate ,Thank you, can i leave with you , do you need any more information from me to fix issue?

Thanks

poweractivate
Most Valuable Professional
Most Valuable Professional

@AndyPowerAppNew 

I recommend using User().Email as the unique identifier for now

Sign in button OnSelect property:

 

With
(
	{_myRecord:LookUp(StaffWhosIn,Title=User().Email)}
   ,If
	(
		!IsBlank(_myRecord)
		,If
		(
		   _myRecord.SignedIn
		   ,Notify(_myRecord.Title & " is already signed in - they must sign out first",Error)
		   ,Patch
		   (
			  StaffWhosIn
			 ,{
				  ID: _myRecord.ID
				 ,SignedIn: true
				 ,SignInTimeDate: Now()
			  }
		   )
		)
		,Patch
	     (
		    StaffWhosIn
		   ,{
		  	    Title=User().Email
			   ,SignedIn: true
			   ,SignInTimeDate: Now()
		    }
	     )
		
	)
)

 

 

 

and then

 

Sign out button OnSelect property:

 

 

With
(
	{_myRecord:LookUp(StaffWhosIn,Title=User().Email )}
   ,If
	(
		!IsBlank(_myRecord)
		,If
		(
		   !_myRecord.SignedIn
		   ,Notify(_myRecord.Employee & " is already signed out - they must sign in first",Error)
		   ,Patch
		   (
			  StaffWhosIn
			 ,{
				  ID: _myRecord.ID
				 ,SignedIn: false
				 ,SignOutTimeDate: Now()
			  }
		   )
		)
		,Notify(User().Email & " does not exist in the table",Error)
		
	)
)

 

 

 

See if this works better @AndyPowerAppNew 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (1,841)