How does one tie a User Account to an Employee record, through the Employee field on User Account Security Maintenance on the Company page? The drop down lists the employee name, but what does one do if you have more than one employee with the same name?
Could you put an initial in both the employee names that are the same to distinguish them? Ideally it would present you with 2 columns or use the search method where you could lookup by name or EmpID but unfortunately we are stuck with just names.
PITA… but pick one, then do a real quick BAQ between UserFile and EmpBasic. That would at least give you the ability to see the IDs on both sides and not just names.
I think the best way to do that would be to add the User ID to the employee in Person/Contact. That should populate all the way through all screens.
Back to the original topic.
We have User Accounts set up for our MES workstations. I was able to log in to the MES account and launch MES but when I performed the employee login on the MES home page, Epicor brought up a new login splash screen and forced me to log in the MES workstation using my login. At that time my employee record was linked to the User account, and my user was linked to my Employee record. It was necessary to delete them both in order to eliminate this behavior.
Ok, I think I know what is happening.
On the User File, you want to link that to an Employee, this allows Office MES, Get Requests, etc to work from the full Epicor.
On the Employee file you want the Employee ID to point to your generic user account, that should allow you to use the generic one with regular MES on your shop floor but also allow those who need full Epicor access to be able to work as well.
This is what we do here and it has worked without issue from E9 through 2024.1 (well Kinetic Office MES with AD-SSO is broken now but hey, its Kinetic, what else do we expect).
I guess I should close the loop on the initial topic… (user having to click the Log-In button twice)… The PRB was closed out with supposedly fixed/implemented in 2024.2.
I can’t say I’ve verified this was done and the issue is gone. Though, I have also not heard any gripes about it either… so I’ll assume this one was taken care of.
That being said, there is a new issue that the previous person to log in… their ID is preloaded and the user needs to delete it and put in there.
So, I won’t say “one step forward, two-steps back”… but I’m also not quite sure we’re moving forward, either.
1 Like