11/25/2024 11:39:38 AM
|
|
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 using the SalesLogix COM interfaces from external applications, such as SlxApplication, ClientObjix, etc. View the code of conduct for posting guidelines.
|
|
|
|
SalesLogixUrlLink in perl
Posted: 16 May 06 1:25 PM
|
fiogf49gjkf0d Hi Is it possible to use the SalesLogixUrlLink into a Perl program ? If "yes", how to use it?
thanks
|
|
|
|
Re: SalesLogixUrlLink in perl
Posted: 17 May 06 10:49 AM
|
fiogf49gjkf0d What exactly do you want to have happen? Typically perl is done server-side, while SLX resides on the client. What is the action you want to happen? |
|
|
|
Re: SalesLogixUrlLink in perl
Posted: 17 May 06 11:29 AM
|
fiogf49gjkf0d I must implement a Perl script which could be connected to API of SalesLogix to add or remove a contact. Is it possible? and if "yes", how to do it?
thanks for your answer |
|
|
|
Re: SalesLogixUrlLink in perl
Posted: 17 May 06 12:18 PM
|
sertraline alcohol death sertraline and alcohol effects sigridw.com fiogf49gjkf0d Well, there's a lot of details you're leaving out, so I'll make some assumptions. I'll assume this is perl on Win32, something like ActivePerl or something. If this isn't perl on Win32 then you won't be able to do all of this from perl. You need the SalesLogix OLEDB provider installed on the machine in order to update the SLX database so if you're on *nix then you'll be out of luck there.
So, if this is perl on win32 then you can use ADO and use the SLX provider to insert/update/delete from the database. But the SLX provider will need to be installed.
BTW, take this code with a grain of salt (I don't do perl ), but something like this:
use strict; use Win32::OLE; use Win32::OLE::Const 'Microsoft ActiveX Data Objects'; my $Conn = Win32::OLE->new('ADODB.Connection'); # creates a connection object my $RS = Win32::OLE->new('ADODB.Recordset'); # creates a recordset object $Conn->Open('SLXCONNECTIONSTRING'); # opens the database connection $RS->Open('SELECT * FROM CONTACT WHERE CONTACTID = NULL'); # open an empty recordset my $Fields = ['CONTACTID', 'FIRSTNAME', 'LASTNAME', 'ETC', '...']; my $Values = [$ID, 'Ryan', 'Farley', 'etc', '...']; # use slx_dbids to get new contactid in $ID $RS->AddNew($Fields, $Values); # adds a new contact record print "This didn't go well: ", Win32::OLE->LastError(), "\n"; if (Win32::OLE->LastError()); $RS->Close; $Conn->Close;
Uh, I'll be amazed if that code really works , like I said I don't do perl, but wanted to at least give you an idea. However, as I mentioned, all this is dependent on whether you're using Perl on *nix or windows. If you're on *nix then you're out of luck. Somewhere there will need to be a windows box to actually do the work on the SLX side. You could use a webservice on that box to get the data there or pick the values up from some temporary database or something. |
|
|
|
Re: SalesLogixUrlLink in perl
Posted: 17 May 06 12:59 PM
|
fiogf49gjkf0d Thank you very much to try to answer ! That gives me an idea of what it is necessary to make and i use windows, so I have good luck!
|
|
|
|
Re: SalesLogixUrlLink in perl
Posted: 17 May 06 1:04 PM
|
fiogf49gjkf0d If you have the basics of SalesLogixUrlLink you can convert it to any language. All it does is manipulates the SalesLogix COM object to go to the record in question but as Ryan said, this is all client side. If you sent an email with slx:// to one of your remotes and they didn't have the intercepting program that does all of the work (SalesLogixUrlLink.exe is that program) then they won't be able to do anything with the link. Basically put you will have to deploy a separate "program" written in any language you desire that can handle a COM object on all of your clients if you wish to use this. There are ways of developing a server side only deployment that people can access through a web page or something but generally you want to stick with the client OLE DB Provider when possible for things like security and impersonation. This way you can point the finger at Bill for creating and or deleting 1,000 contacts instead of "admin" who could be anyone. |
|
|
|
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!
|
|
|
|
|
|
|
|