I’m hoping someone has been through this before and can offer advice. We are multi-company and on-premises. One of our companies was sold and we worked with Epicor to copy out thier data. However, we’re still left with that company in our Epicor instance. Best practice would be to have the sold compnay’s data avilable but in a “read only” state. Has anyone accomplished this and how? As we explore doing this ourselves, it seems like we would need to manually copy every single menu item to the sold company, and then tick the “read-only” box on every single menu item.
Does anyone have a faster way to do this? From experience, I’ve found DMT doesn’t play well with menu security. Perhaps there is some query kung-fu that can isolate a company and its data and lock it down from the SQL server side?
What we do when we need to shut down a company in Epicor is remove everyone’s access to it save for a small handful of people who do need it (like finance) to run any last reports/look up history. Once the final year end is complete and all those related tasks are done we basically take it down to only the manager account having access, granting temporary access upon request if anyone needs to look something up.
Not the ideal answer I know, just what we have done with similar cases.
In this case, The new company is also on Epicor, and the database has been handed off to Epicor Professional Services to strip out our company and then set them up in their own Epicor environment - so all of their data is still accessible from their new environment. However, as you said, finance still wants access to the new company in our multi-company database.
The roadblock is that “All Companies” checkbox. If we mark anything as read only, it will set it as such for “All Companies” without first going to Actions => Copy To Current Company.
Is there a means of Mass processing the “Copy To Current Company” for ALL menu items, so that we can then mark everything in the sold company to “Read Only?” There are specific people who will still be accessing the new company’s new environment, and we don’t want them accidentally getting mixed up and logging into the multi-company environment.
I work with NottaEngineer - and this is a joint task we’re both focused on.
Anyone who has had to Mass “Copy To Current Company” all menu items before, how you went about it would be helpful!!!
The Company field in the Menu DMT Template is Owning Company. Setting it for the company in question adds a new menu for that company only, the same way as manually clicking “add to current company”.
I’ve never used the Read Only flag in the Menu Template but I have to imagine it works fine.
In testing, one thing I discovered when testing setting the Company and the ReadOnly, is that if I only setup the “Required” fields, the change crashes the menu item, as it’s no longer updating the menu item, but creating a new company specific menu item from scratch - thus this does require having all requisite fields filled in for adding a menu item to the menu.
I tested on Order Entry and Allocation Wave Tracker under Order Management - and the error (when trying to access from the main menu) was that it couldn’t be blank… because neither a classic .dll or a kinetic url was populated. Definitely adds a level of complexity to the DMT process - and I still need to test regarding items, like Order Entry that have both filled in, even though the classic option is the one set and the url field is grayed out even though it’s populated.
