Sage 100

Customer on v2013 has unchecked allowing new items to be created in Role Maintenance. Yea but now they get prompted with ""Is this a new Alias Item Code?"" instead in S/O Entry when keying in an invalid item. They don't want that either. If I take off Create rights for Item Maintenance, Vendor Maintenance, and Customer Maintenance under Role Maintenance it suppresses the new alias prompt. Gee that's all it took. Is there any other functional way to deal with this without mods or scripts?

Initially it sounded like maybe a corrupt custom Lookup so I was gonna suggest trying to delete and re-create the Lookup. But sounds like you're all set.

But they don't want me to prevent them from creating new vendors and customers as a way of suppressing the ""Is this a new Alias Item Code"" prompt. I was being sarcastic when I said ""Gee"". I'll have to start using the new emoji in SocialCast :anguished:

Why not put a column pre-validate script on the item code? This should prevent that message in S/O without having to mess with security too much. sItem = """" retVal = oBusObj.GetValue(""ItemCode$"", sItem) set oItem = oSession.AsObject(oSession.GetObject(""CI_ItemCode_svc"")) retVal = oItem.Find(sItem) if retval <> 1 then retVal = oScript.SetError(""Item Not Found."") end if

I thought of that too but no scripts allowed in this case and they don't want the ""Item Not Found"" prompt either. :no_good:

No scripts allowed..... Hardcore!!

With all the restrictions, I would tell them them to set up two user IDs - one with the ability to create Customers and Vendors and another with it all switched off. They will just need to switch user ID as needed. Crazy, but so are the restrictions on customizations.

Thanks everyone! The core issue on the restriction of customizations is about money. This client is on an annual support plan but didn't budget for anything else. They are a hospice and I'm guessing their Medicare reimbursements are low.