8/23/2025 10:31:03 PM
|
| |
| 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!
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.
|
|
|
|
Design Limitations: Seeing what I don't have access to.
Posted: 28 May 08 7:11 AM
|
I have a new requirement from an existing customer running 7.2.2
Originally they wanted to 'search for accounts'... If they owned the record - or of the record was owned by a team to which they were a member - they should have full access. However if they did not have access to the record they should see the record returned in the search and see who the Account Manager is but they should not be able to open the record. They would have to go and speak to the Owner/ADMIN and get added to the appropriate Team.
There also needs to be management groups that have override permissions on these rules.
They want this to permeate throughout the entire application - with the same applying to contacts and opportunitues (all being controlled by the Account access)
I have heard about modifying the OLE DB Provider but have been toild there are technical hurdles to be overcome
I have also muted the idea of allowing all records to be searched for but creating different views depending upon team group department membership...
Modifying Screens is not enough - I have to ensure that user are restricted in the Query builder as well as in thier views..
How would you guys do it?
Anyone done it?
Tanks in advance.
Mike.
|
|
|
|
Re: Design Limitations: Seeing what I don't have access to.
Posted: 28 May 08 6:02 PM
|
Firstly, I have no experience of modifying the provider, so cannot advise on that solution.
I would use SLX security as it comes OOTB and add extra enquiry features over the top of the standard functionality to provide the extra access that you need. This extra functionality could be scripted to use the SQL Native Client, not the SLX OLEDB Provider, thereby bypassing security. Obviously, no updates should be done this way.
That is not exactly what you want, but it is achievable if you can get the client to adjust their expectations a bit. "Permeation throughout the entire application" is not going to be feasible economically (excepting, perhaps, some custom work to the SLX OLE Provider as mentioned above), unless you're speaking to a client with a very large wallet.
Phil
|
|
|
|
Re: Design Limitations: Seeing what I don't have access to.
Posted: 30 May 08 8:39 AM
|
| Phil's right, for your client to see data that they don't have access to through the SalesLogix security model, you'll have to bypass the provider altogether - which is painfully easy to do. Then you would just have to create your own custom lookup class that allowed this behavior by utilizing a standard oledb or sql native client connection rather than using the slxoledb provider. You'll run into problems with remotes though, as the connection string for these will be different than that for the main server. |
|
|
|
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!
|
|
|
|
|
|
|
|