So we have a couple of areas(Part, Customer, Supplier) tables that other areas need access to update sub databases.
I.E. -
Part - update description, min, max, reorder, buyer, supplier, etc. but really don’t want them to be able to create a new part.
So at first tried doing UBAQ and that almost worked until getting to the supplier.
Customer - need to be able to add, change ship to location address info without adding a new customer.
First idea - use app studio to create a copy of part, customer, supplier, etc. and remove the add / create button from the top. - Unsure if that will even work.
Suggestions?
IF (and this is a pretty big IF) all you want to prohibit them from doing is creating a new customer record, then a BPM can do that pretty easily.
If, however, there is a boatload of things you want to optionally allow/prohibit, there isn’t a “good” (meaning easily implemented) way to accomplish that.
Epicor has both Field Security and Service Security, but wading into that quagmire gets tiresome very quickly… and maintenance is just as bad.
You should also be aware of the “Min Max Safety Mass Update” program that was added in 2023 at some point, it will want access to other fields under Part and Part Class if your going to use that. Which makes your issue more complex. You may just have to turn on logging and let them have at it.
Below are bpms we use to stop new Parts and Vendors. We do not stop new customers, but I have a bpm that makes them all suspects and only allow accounting to change them from Suspects to Customers. You can also do the same for field X has changed from any to any and User is not in Y security group with a message referring them to a user that can make that change. If they are all bpms it does not matter what UI/UX you are using.
