Hey all,
Taking the leap to a different ERP tonight after around a year in implementation and development.
We will keep the Epicor application and database as archival/reference, but I was wondering what is the protocol to make the application in read-only mode?
My plan was to upload a DMT file to inactivate most users for the cutover period, take my database copy to extract the data from, and then put the database in read-only mode and re-activate the users.
Is this the correct course of action or is there a different method I should be considering?
Thank you
I haven’t tested this, but you may be able to add the -ro switch with the DMT to the menu arguments across the board. I’m not sure how Epicor will react to the database itself being read only.
1 Like
Can read only be applied by user, or does it apply to the entire database only?
At another company, we used to have a read only security group that only had access to the tracker screens. Would that work for you? Requires a bit of setup, though.
I prob. don’t have bandwidth to do anything like that. The main thing we wanted to do is make sure users aren’t creating stuff that I’m not gonna be porting over for cutover.
I never tried that. Usually i just removed all permissions from Set up and any entry screens. So all they had was trackers and reports. Are you moving to a completely different ERP system?
That’s probably what @hmwillett was referring to too. Yes we are going to a whole new ERP.