Sage 100

I forget, was one of the new features in one of the updates the ability to limit the view of certain customers to those owned by certain salespeople?

No

SAGECRM has this functionally but not standard MAS

That's typical. That's why ERP systems that have CRM embedded inherit this ability. SAP Business One, NAV, and Epicor all handle this because it's a basic requirement of CRM. From: do-not-reply@socialcast.com [mailto:do-not-reply@socialcast.com] On Behalf Of Jim Woodhead Sent: Wednesday, August 01, 2012 4:08 PM To: Mark Chinsky Subject: Re: [90 Minds Consulting Group] I forget, was one of the new features in one of the updates the ability to limit the view of certain customers to those owned by certain ...

You can achieve the same results however, using Custom Office and ALE lookups. So the tools to achieve this are ""out of the box"".

I know you can block people from seeing the results in search, but can you keep them from entering an 'unauthorized customer?' Can you keep them from drilling to that customer from say an inventory screen that ends up drilling down to customer info?

I wonder if this could be scripted????

I believe it was in one of the scripts that Steve Malmgren demoed a couple years back.

The problem with the scripting is there are so many areas that need would need a script. I have a different scenario where this company has 7 different warehouses and the staff at each location can technically enter entries into each others warehouses. So wish something like this was standard option. I wish user maintenance had the ability to have more info - such as email address, warehouse code assigned to or sales person number assigned to. Then this would make it more native in some ways.

I agree that it would be nice for much of this to be standard. Larger customers with sizable sales forces typically want this type of segregation. I have other experiences with custom office that make me shy away from large scale implementation as my primary tool (note the word primary - I'm not saying Custom Office is totally bad - just that I do not feel it is a primary customization tool): - Any type of issue with a panel customization and the general cure is ""reset the panel"" -- this type of weak design tool is not acceptable for larger companies. Ever tell a customer with 50 users that they need everyone out for 3 hours while you redesign their custom office screen after a reset? I have. Not fun. - Upgrades. The more stuff that touches core functionality and doesn't survive an upgrade the poorer the experience. Mostly Custom panels survive upgrades - but not always. The cure is generally the same - kick everyone out and re-implement (after you've prayed heavily they survive upgrade). - Design tools - the Custom Office design tools suck. Large 50 user sites typically have in-house resources that are going to make panel/screen customizations. Same thought process as above in my first comment. The first time a user removes a required field (or places it outside some boundary) and receives a panel type error message - there's often no practical way to debug short of ... (wait for it, wait for it) ... panel reset.... In short I believe that a lot of our conventional thinking of how to resolve issues with Sage 100 work -- though they don't scale well to larger sites when used as PRIMARY customization methods. I'd be more enthusiastic about Custom Office if Sage had better debugging tools or disallowed a user from making a panel change that in turn provoked an error message due to a field move.

I am new to this group and was wondering if anyone thought of DSD has 2 ES mod that might work AR-1157 Security For Customer/Salesperson by User ID or AR-1152 Security by Division - they really are only for SO and AR so not sure if you need it other places like Inventory or if you found a solution already.