Field Security - oops

Yahoo Archive
1
Thanks for the reassurance that I'm not the only one who's done this!  LOL

Actually, after much time with Epicor support, several queries going nowhere, and much time banging my head on the desk... on a whim, I decided to test the Security group, as soon as I put one of my users in a new group, he was able to proceed!  I think, somehow, the security group got corrupted??  I'll try and confirm that with Epicor support later today.  
2

I knew better than to touch it, but i was asked to block buyers from changing the GL account on PO Releases.  Hind-site, what I should have done was to customize the User interface to blank out the field, but what I did was go to field security and change TranGLC.GLAccount to Read Only for those users.


What it did was make it so that when They go to do a PO, and buy to "Other", they get an error saying that "The account cannot be blank".  So, I changed it back in field security.  


But, they are still getting the same error about the account being blank.


What should I try next?


Do you think restarting the appserver will help?

3
I've made a similar mistake. Obviously go back and make sure that that everyone has full access to it and you don't have individual people set to read only or security groups set to read only. Restarting your app servers shouldn't be necessary, but it is necessary for you to get everyone to log out and log back in to effect the change. 

I've made a similar mistake before and it definitely seemed to take longer than 5 minutes for everything to get updated properly. 

if you want to prevent them from changing it you could always do a BPM to prevent certain groups from changing that field. 

hope this helps,

Bobby