6/7/2025 12:22:38 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 the use of .NET Extensions in SalesLogix version 7 and higher. View the code of conduct for posting guidelines.
|
|
|
|
external .net application calling slx features.
Posted: 20 Jul 07 12:53 PM
|
Hi everybody,
I have an external .net application that I am trying to use to handle some administration work that bridges across sales logix. I would like the app to be able to pull things like the account information from the current account in saleslogix to save the admin some copy pasta, as well as implement the security features of sales logix. I am unsure if I need to implement something more than the .net extensions or if I may just be missing something. From most of what i have been reading around on the forums, and on the net most of the .net extensions are being used to run things from inside sales logix.
Is this just how things are and I need to accept it? I would prefer that the app could be launched external to slx but with slx open to pull the info of course. I don't think I would have a problem if the form is launched from within slx but my end users might.
any help would be greatly appreciated
TJ |
|
|
|
Re: external .net application calling slx features.
Posted: 24 Jul 07 3:11 PM
|
As long as your data access code uses the SLXOLEDB provider, row level security will be imposed. If your app connects as the TJ SalesLogix user, you will only be able to see accounts that TJ can access.
There are many layers of security. Please elaborate and we can lend a hand. That being said, you are going to have to code it if you want to implement anything but Row Level Security.
The main benefit of the SLX .net extensions is the deployment mechanism - it ensures every SalesLogix workstation has the .Net code you have written, including remotes. If this is an admin feature and deployment isn't a concern you don't need to use .net extensions.
Timmus |
|
|
|
Re: external .net application calling slx features.
Posted: 24 Jul 07 5:21 PM
|
Sorry for the late reply - I've been on vacation, and I hate missing out on fun threads like this one 
If what you want is "external", then you don't want a .NET Extension. A .NET Extension is meant to allow you to use .NET code "inside" the client. For external, you just build a .NET app and launch it. That's all. As Timmus mentioned, for any writes or reads to the database you'll want to use the SLX OLEDB provider. This will ensure the data will sync to remotes and also allow SLX security to be involved. For "invoking" things in the running client, you'll want to use COM with SLX. Add a reference to the COM library "SalesLogix Library" and instanciate a SlxApplication object. You'll find everything you need there. Anything you can invoke from an internal SLX script you can access from an external app via this object.
Make sense? |
|
|
|
Re: external .net application calling slx features.
Posted: 24 Jul 07 5:57 PM
|
That makes perfect sense thank you!
I have been trying to piece through some of the resources here, and i watched through the leveraging .net in slx screencast and thought i had pretty good idea that i needed com of somekind. I just wasnt sure what. I figured as a fellow c# lover you would be able to help Ryan.
TJ |
|
|
| |
|
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!
|
|
|
|
|
|
|
|