Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Thursday, June 19, 2025 
 
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 ThreadView:  Search:  
 Author  Thread: Adding custom fields to Insert New Lead...
Mike Haney
Posts: 20
 
Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 26 Jul 07 7:34 PM
I'm just a newbie when it comes to SLX but am picking it up fast, the language and framework are very easy to work with. I've got a decent background with ASP & VB6, and intend to order the DevLogix book this week...

That being said I'm hoping someone can point me in the right direction for a customization that I need to have in place as soon as I can as management is biting to get this done. I've added several custom fields throughout the contacts, leads and accounts main plugins but am now trying to add these fields to the "Insert New" plugins. I've got the fields into the form but I'm not sure where to start with getting the data from those fields into the db tables.

From Architect when the form loads it creates an instance for gLI, linked to the base Lead record from what I can tell:
Set gLI = New LeadInfo

Using this instance it runs a PrepareLeadInfo function when saving the lead record, which assigns the field values to the gLI object:
gLI.Prefix = nedName.NamePrefix

So, my question is how do I get my custom fields into LeadInfo, or is there a totally different way (direct SQL? I hope not!) to go about this?

Thanks in advance for your help, and for the great resources already in this forum!
[Reply][Quote]
Bob (RJ)Ledger
Posts: 1103
Top 10 forum poster: 1103 posts
 
Re: Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 26 Jul 07 9:28 PM
You will have to modify the Class LeadInfo. It's in System:SLX Lead Info vbscript.

..but as you probably know.. just open the form Insert New Lead.. show the includes.. click on them.. away you go!

It's all there..

--
rjl
[Reply][Quote]
Mike Haney
Posts: 20
 
Re: Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Jul 07 7:27 AM
I'm going to take a wild guess here, but that's not available in the Standard Edition (v7.01) is it? I found the SLX Lead Info vbscript from the plugin manager and the Open Plugin option is greyed out...

If it's not available in Standard, is there a workaround that I can use that won't be too "ugly"?

Thanks!
[Reply][Quote]
Bob (RJ)Ledger
Posts: 1103
Top 10 forum poster: 1103 posts
 
Re: Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Jul 07 7:43 AM
You need to purchase an Architect Upgrade.

Your BP has sold your company the "cheap" package.

The standard package will only allow you to modify what has already been customized.. and that's on a per form/vbscript, etc basis.


When a BP does this to make a deal it really "pizzes" me off! It impacts the entire partner community in a negative way.

--
rjl
[Reply][Quote]
RJ Samp
Posts: 973
Top 10 forum poster: 973 posts
 
Re: Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Jul 07 8:38 AM
come on RJ:
"You need to purchase an Architect Upgrade.

Your BP has sold your company the "cheap" package.

The standard package will only allow you to modify what has already been customized.. and that's on a per form/vbscript, etc basis.


When a BP does this to make a deal it really "pizzes" me off! It impacts the entire partner community in a negative way.
"

Often times the CUSTOMER is simply too CHEAP to buy the advanced package.....and / or doesn't have the BIG BUCKS to develop their internal IT Staff to be proficient in SLX. Have been making money as a BP for a decade because of this Make or Buy mentality....including off of some BIG customer's that don't want to do this in house.

It doesn't impact the BP community negatively at all.....the customer can always pony up the big dollars and upgrade their server and clients and maintenance (now at 15% of the higher list pricing!)..... that they haven't and then complain about it speaks negatively about the customer.....not about the BP.

Some people want to try to limp buy (pun intended) on the cheap route.....

Of course, what really ticks me off....is that the ARCHITECT was free in SLX 2 - whatever...... unlimited scripting, forms, fields, SLX report writer (OK not so good), decent mail merge to contacts, WinFAX support.......now those were the days.

Stop being a Jaguar salesman 'pizzed' off because I bought a Prius.... if I need to go FAST then I'll come back to you and buy or lease the Jag.

RJ Samp
[Reply][Quote]
Ryan Farley
Posts: 2265
slxdeveloper.com Site Administrator
Top 10 forum poster: 2265 posts
 
Re: Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Jul 07 10:57 AM
Quote:
Originally posted by Bob (RJ)Ledger

Your BP has sold your company the "cheap" package.

When a BP does this to make a deal it really "pizzes" me off! It impacts the entire partner community in a negative way.


OK. I have to call you on that on RJL

I have to agree with RJ Samp on this one. There's nothing wrong with selling a system with the standard license. The standard license exists for a purpose and a very valid one at that. Many companies don't have *any* plans to even customize SLX themselves and plan to go through their BP for customization. Are you saying they should have to shell out additional $$$ for the license that allows them to do something they'll never intend to use themselves? A BP that pushes for the customer to NOT go with standard, when all they'll need is standard isn't being fair with their customer. The customer can always buy it later if they need/want to. I don't have many customers on standard license, but I do have some, and they would never feel "jipped" because they can't do customization themselves. They don't want to - and I'd be very afraid for them and their system if they did . They are far better served by having their BP make customizations for them, knowing that the customizations will be done right. They are very happy with that relationship, and so are we - so what's wrong with that?
[Reply][Quote]
Bob (RJ)Ledger
Posts: 1103
Top 10 forum poster: 1103 posts
 
Re: Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 28 Jul 07 12:54 PM
I had a direct phone conversation w/the individual who posted. I turns out that his BP did NOT tell him (or his company) what all the differences were in the various "versions" (Premier/Standard, etc).

The BP was aware that the client wanted (as had the technical background) to do customizations. They could have sold them a "Standard" w/a Premier Architect license "upgrade" in teh original deal and there would have been no issues...but they did not.

I think that the BP was waiting to see if the client would come back to ask for help in customization so that they could than sell them a bunch of services.


This is the 2nd time in less than a month involving the same BP where the client was sold a "Standard" and not told of teh customization limitation the I personally know of and got involved. In teh forst case we got them an Architect upgrade ... in this case I told them what to ask for from their BP and if teh BP won't selll them teh upgrade.. I told him we will.

I stand on my original post.. the BP did NOT inform the client of what his options were and was doing the client a dis-service BIG TIME!
--
rjl
[Reply][Quote]
Ryan Farley
Posts: 2265
slxdeveloper.com Site Administrator
Top 10 forum poster: 2265 posts
 
Re: Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 28 Jul 07 2:28 PM
That's a different scenario than a blanket statement of:

Quote:
Your BP has sold your company the "cheap" package....When a BP does this to make a deal it really "pizzes" me off! It impacts the entire partner community in a negative way


Selling the cheap package isn't a bad thing. Standard licensing is great when that is what the need is. Not telling your customer all the options is bad. No one would argue with that.
[Reply][Quote]
Bob (RJ)Ledger
Posts: 1103
Top 10 forum poster: 1103 posts
 
Re: Adding custom fields to Insert New Lead...Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 29 Jul 07 12:06 PM
Quote:
Originally posted by Ryan Farley

That's a different scenario than a blanket statement of:



Selling the cheap package isn't a bad thing. Standard licensing is great when that is what the need is. Not telling your customer all the options is bad. No one would argue with that.


To quote "another".. ".. Zactly!.."
--
rjl
[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 | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 6/19/2025 11:19:00 AM