It seems like once you have logged into the regular epicor client in the browser, it becomes very difficult to load data collection even when putting the ?mode=mes or ?mode=dc in the url. It either reverts to the login screen (over and over, even after completing the Azure AD auth). Or it loads but it goes to the regular app home screen instead of data collection.
We are using various workarounds like open a new tab and then put the data collection url, close the browser and relaunch, or even open a new incognito window. This is really frustrating for the users who need to be able to easily use both the regular app and data collection.
Anybody have any secrets to making this easier? How are you making data collection accessible to your users in the browser?
I have experienced some issues with MES browser. I think most of my problems revolved around our three data collection users. We have 3 DC locations around the shop. Each PC should be logged in to one of the three MES accounts. At some point, one account didn’t work, and someone used another PCs account. Since I don’t have ‘multiple sessions’ turned on in user account security maintenance, it boots one or the other user if both are trying to use the same account. Once I got each PC back on its own unique account, those issues went away.
Yeah we run into that issue too - especially with the people who need to use both the regular app and data collection - but this particular issue is different since they can’t even get into data collection at all.
Yeah that may be what we need to do. Typically we just set up the employees separately, no link either way. This is so that when they are using shared workstations anybody can use MES on that computer.
Typically IT sets up the epicor user account. Separately, warehouse management sets up employee records (and they have no access to user account security to be able to go back and link the employee). We keep them unlinked so that the people on shared workstations can log into MES without having to worry about which Epicor user is logged in on that workstation.
not that i know of but i honestly have lost track of irons in the fire at this point. its on my list to revisit since we intend to go live Jan1. but i did just try it yesterday and failed using Idp + AAD
Yeah I had mentioned that as one of our current workarounds. Many shop floor users don’t know what that means, so its a burden on help desk resources to train. Plus then you have to go through the full mfa authentication process from scratch which is time consuming. All for something that SHOULD just work. Its 5 or 10 minutes of the day wasted, sometimes more, on a completely valueless task.
s about parity. Still not beneath me to use the ‘parity-pledge’ to push what’s wanting in Kinetic.