Sage 100

Is there a way to restrict most users from viewing Summary & History Tabs in Customer Maintenance & Inquiry and the Summary & History Tabs in Vendor Maintenance & Inquiry?

Custom Office doesn't let you hide the tabs, but you can hide all the fields on those tabs

Yes, but you'd have to do it a user at a time. Was hoping there might be a way to group users and then hide the fields. Just trying to keep the company from having to do this 17 times on each of the four panels

How about using the customization group field in User Maintenance?

@MarkKotyla , is this a new function?

Not that I know of. I recall using it in tha early 4.0x days (maybe earler).

Hummm, well that's interesting. So, I assume the field doesn't require setting up groups, just specify something in the field and use that vs the user ID in Customization?

@DebThomas that is exactly how the field is used. This particular field has been around since role maintenance appeared in version 4.0. It is nice because it works accross roles but each login can only be a member of one customization group.

Basically it is left from the 3.xx security group feature, and now only used for Custom Office.

Thanks everyone! I thought I'd read/heard about such a field. Did a test and voila! Too bad there's only one group field per user, but at least it's there.

Ok, so now I have a secondary problem after thinking this was all resolved. Apparently they have modified something else using All users and All companies and there is a conflict between whatever they did there and the Group panel customization. Is there a priority system that CO reviews when determining what panel information to display?

It goes most specific to more general -- e.g. an individual user would get priority over ""all users"".

That's what I thought. If we've specified the user in a Group, then it would look at those panels changes and then to any for All...correct? That is, if panel mods are done for all AND we have a unique mod for a few on the same panel - both mods will appear right?

No, it's not cumulative -- it would only display the mod for the customization code not the ALL customization.

So...just to be clear. If the specific panel has an all user modification, then once you create a specific mod for a single user for some other field let's say, then you'd have to specify both on the single user for both of the mods to work - have I got it right now?

Crud, this has become a nightmare. Ok, so for example we are trying to hide the all of the information on the History tabs in AR, IM & AP. When you check the boxes to hide the info on the Group modification, MAS also checks the same boxes on the ALL User customized panel. Any changes made for the specific user/group is changing it for all!

Deb, is this 4.4 or 4.5? If so it may be easier to use a script. On the post read event of these master tables you could fire off a script to test if the user belongs to a role, like ""History"", and if they don't, the script could disable these folders. Here's an example of the script: retVal = 0 retVal = oSession.AsObject(oSession.Security).IsMember(""History"") if retVal = 0 then retVal = oScript.SetUIControl(""fldr.pSummary"",""DISABLE"") retVal = oScript.SetUIControl(""fldr.pHistory"",""DISABLE"") end if

There's a sample script from a 2010 session by Steve Malgren. Perhaps it can be modified for what you need. AR Customer Row Level Security (AR Customer Maintenance) If Salesperson is not ""0100"" then the Summary and History folders will be disabled. If focus is already on the Summary or History folders and the user browses to a customer whose Salesperson is not ""0100"" then focus will be set to the Main folder. Here's the script: retVal = 0 slsperson = """" retVal = oBusObj.GetValue(""SalespersonNo$"", slsperson) ' if slsperson <> ""0100"" then If oSession.UserCode <> ""XXX"" then ' this example forces control to the main folder and disables the summary and history folders if the salesperson ' is not 0100. Instead we could have used oSession.UserCode or ' IF cBool(oSession.AsObject(oSession.Security).IsMember(""rolename"")) then ' to check to see if the user belongs to a security role retVal = oScript.InvokeButton(""fldr.pMain"") retVal = oScript.SetUIControl(""fldr.pSummary"",""DISABLE"") retVal = oScript.SetUIControl(""fldr.pHistory"",""DISABLE"") else ' else if it is salesperson 0100 enable these folders retVal = oScript.SetUIControl(""fldr.pSummary"",""ENABLE"") retVal = oScript.SetUIControl(""fldr.pHistory"",""ENABLE"") end if

*Steve Malmgren.

Sadly scripting and the use therein is not a strong suit. @MichaelNottoli this is 4.4 SU6. My frustration is that CO should handle this ... shouldn't it?

I agree that CO SHOULD be able to do this. However it can be maddeningly clunky. IMHO, a reasonable payment to someone like Dan Burelson to set up a few scripts would give you a simpler and more elegant solution.