Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Thursday, May 2, 2024 
 
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 .NET Extensions
Forum to discuss the use of .NET Extensions in SalesLogix version 7 and higher. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to SalesLogix .NET Extensions | New ThreadView:  Search:  
 Author  Thread: SLX Provider Security Plugin
Mike
Posts: 6
 
SLX Provider Security PluginYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 01 Sep 10 10:26 AM
Hi,

I am trying to add a custom SLX Provider Security Plugin, much like the one described here:
http://www.techadv.com/technology-advisors-blog/Sage-SalesLogix-Provider-Plugin-For-Custom-Security.html

However unlike this example (which edits the WHERE clause of a SELECT statement), I am trying to edit an UPDATE/INSERT statement when certain conditions apply. I want to take the fields being SET in the UPDATE/INSERT statement and add one additional field with a hardcoded value. I have played with the code from the example above and from some of the interfaces I have found, I believe this is possible. However I am unable to find the correct code to make this happen.

Has anyone done something similar to this? Does anyone know of any documentation on this that they can point me to? I have searched all the forums and search engines and have come up empty.

Any help would be greatly appreciated.
Thanks!

-Mike
[Reply][Quote]
John H. Hedges
Posts: 62
 
Re: SLX Provider Security PluginYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 04 Sep 10 12:32 AM
I've done something similar to that, and I would recommend taking almost any other feasible approach if you can. The extension architecture is designed specifically to *prevent* you from modifying INSERT/UPDATE statements, though the documentation for it and the interface properties/methods themselves indicate otherwise. This documentation has never been fixed, and whoever built the functionality (and documented it) left Sage shortly after building it.

Meanwhile, extensions can work beautifully for what the architecture is meant to allow for, which is to modify the "AND SECCODEID = 'XXXX'" clauses for SELECT statements, so as to expand on (or completely change) the base provider security model. Anything beyond that though, and you're likely to have problems.
[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 © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 5/2/2024 12:14:24 AM