slxdeveloper.com Community Forums

The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!

Architect Forums - SalesLogix Scripting & Customization
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix Scripting & Customization | New Thread

View: Search:

Author

Thread: Team or Group Name.

Michael Rivera
Posts: 41

Team or Group Name. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 18 Sep 09 12:20 PM

Hi all,

I am trying to limit access to something by Organizational Department or Team Name. I know that you can access the username (Application.BasicFunctions.SystemInfoFor(UserName)) but how do I get the Organizational Department or Team Name of the user who is currently logged in?

Thanks ahead of time.

[Reply][Quote]

Ryan Farley
Posts: 2265

Re: Team or Group Name. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 18 Sep 09 12:48 PM

You can take a look here for some help: http://customerfx.com/pages/crmdeveloper/2003/11/19/39084.aspx

-Ryan

[Reply][Quote]

Michael Rivera
Posts: 41

Re: Team or Group Name. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 18 Sep 09 12:59 PM

Thank you. Exactly what I needed.

[Reply][Quote]

Mike Spragg
Posts: 1226

Re: Team or Group Name. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 19 Sep 09 5:35 AM

Hi, I've just re-written the normal user/team lookup functions - essentially, my client wanted to prevent access by team/user *prior* to it being checked i.e. ensure the user can only pick from teams [and then users] that they naturally have access to. See here for an example: http://www.empath-e.com/external/LimitTeamUser.png

With this function/control - you can pass in whether you want to see all teams or whether you want to see just the teams this user has access to (read/write/team owner) and then only those users who have read/write capability.

The reason for this is that, within Opps, they didn't want the user to be able to change it to an owner/user that would then *not* be able to see/manage it. Which makes sense, the normal controls allow you to just throw it out to anyone - a combination of user/teams that don't make sense for example. But, equally, it's flexible enough to be used for any example. The absolute advantage is that you will only ever be able to assign [the A/C/O/T) to people who can then subsequently see/manage it.

Contact me if you'd like to discuss it,

Regards
Mike

[Reply][Quote]

Page 1 of 1

You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 8/29/2025 3:21:23 PM