Sage 100

A client of ours claims that when she worked in MAS at a previous employer that she was able to restrict people from accessing different divisions from within AR and AP. Of course, she can't duplicate this trick now and I have never done this. Is anyone familiar with this sort restriction? Is it possibly an add-in?

Find out who her reseller was????? Custom ALE filter? After sitting in on the Amazing Alnoor and his Side Kick Nicole's scripting class, I would almost bet that you could do this with a script....

I would go that route as @JeffSchwenk suggest but I also think DSD had a mod for that.

There were old Extended Solutions for this and DSD has them now. http://www.dsdinc.com/enhancement/security-by-division-3/ http://www.dsdinc.com/enhancement/security-by-division-4/

I have done this Chuck without buying an add-on. First step is to assign each user a user group in LM, user maintenance. Then use the LM, Main, user lookup wizard to modify the ALE using a filter as @JeffSchwenk and @DianeRuth suggest. That keeps the users from modifying the lookup as long as proper security is enabled.

@DougHiggs , are you talking about the ""Customization Group"" in the User Maintenance screen?

Yes. Exactly. Make up a 3 character customization group for each user. .. similar to a role. That keeps you from having to define a lookup for every user... you can then a different ALE for each customization group.

Actually, a script is much better as it would not allow ANY access to the customer/vendor. Filtering the ALE will keep the casual lookers out, but all you have to do is enter the number or use the video button, and the verboten information will appear. And an added benefit of the script is that you could have it display a picture of the green jacket/red pants man to scare some sense into them!!!!!!!!

I definitely see your point, Jeff!

That is a good point @JeffSchwenk . My client wanted to restrict AP inquiry to certain users.. They didn't want users to know from whom they bought material. They divisionalized AP and made material vendors division 99. The ALE filter excluded division 99. So, unless you can guess there is a division 99 and know the vendor number, the user would not be able to view the 99 vendors. Not defcon 5 security but good enough without having to do any scripting or provideX customizations.

Oh, but @DougHiggs - It is unfortunate that you had to cancel out of last week's meeting as the Scripting 101 class would have given you a LOT of ideas that are ""somewhat"" easy to do, but would give you many more arrows for your quiver. A script for the added security would probably take as long as finding the correct ALE window to modify, maybe even less.

I attended the 2 day scripting class in Vegas... Scripting is great... my implementation of the above was a couple of years ago..but if you don't know how to write scripts the above would be an alternative to outsourcing the scripting work.

Don't forget about the accessibility of all that info you're trying to hide on reports, though. The nice thing about the DSD enhancements is that the security restrictions flow through to those as well. So users can run reports for vendors they have access to and won't get info for restricted vendors.

I would probably use the old ""role"" trick with scripting. That would enable the end user to maintain it fairly easy. You could also assign a person multiple roles if they did need to access multiple division. Of course - the DSD mod is probably the safest and most tried and true.

We just purchased AP-1058, security by division, from DSD for a new implementation. Haven't done more than install it yet, but I agree that the report restrictions are going to be important and one of the reasons to go with that. I'm sure scripting is a great option too if I had a clue how to set it up!

Barb - when you're ready to implement it, you should download and re-install the latest version. We found a problem with the inventory sales history report where restricted users couldn't run it at all. DSD fixed it and released a new version of the installer yesterday.