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!

Web Forums - SalesLogix Web Platform & Application Architect
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix Web Platform & Application Architect | New Thread

View: Search:

Author

Thread: Best Practice Question

Dan Carvin
Posts: 227

Best Practice Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 25 Aug 08 1:41 PM

When you make a Userfield visible as an Entity Property, you also have the opportunity to change the Property Name and Display Name from "Userfield4" to something more descriptive of the data stored there.

This makes it easier to assign properties to controls, but if later you need to trace a control back to the database, you have the extra step of looking up the property to see which database field it maps back to.

So what makes better sense to do? Rename the userfield property or not?

[Reply][Quote]

Bob (RJ)Ledger
Posts: 1103

Re: Best Practice Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 25 Aug 08 4:11 PM

Since one can add "custom fields" to the core (OOTB) SalesLogix tables... forget using fields called "UserField... whatever"...

Create new ones. Leave UserField(s) for temp use (in fact, SalesLogix uses some of them - and that's not documented anywhere except in the "code"

This applies to web/Windows/Mobile.

[Reply][Quote]

Dan Carvin
Posts: 227

Re: Best Practice Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 25 Aug 08 6:01 PM

Unless you're developing a Web platform for a client whose been using SLX for several years and keeps data in some of the userfields.

[Reply][Quote]

Dan Carvin
Posts: 227

Re: Best Practice Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 25 Aug 08 6:09 PM

Unless you're developing a Web platform for a client whose been using SLX for several years and keeps data in some of the userfields.

[Reply][Quote]

Bob (RJ)Ledger
Posts: 1103

Re: Best Practice Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 25 Aug 08 6:36 PM

Quote:

Originally posted by Dan Carvin

Unless you're developing a Web platform for a client whose been using SLX for several years and keeps data in some of the userfields.

I would still go thru the changes....
We're upgrading a system right now for a client that has USERFIELD usage. With a bit of analysys we were able to locate all of the places where these fields were used. They are now all "converted" and clean. It's worth the extra effort in teh long run.

[Reply][Quote]

Nicolas Galler
Posts: 93

Re: Best Practice Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 26 Aug 08 12:16 PM

I think if you rename the field in the database manager (I mean change the field description) and in the App Architect it is a decent compromise... In most cases on 7.2 you don't have to write custom SQL anymore so the only place where you will still have to deal with the Userfield* name is in Crystal, and Query Analyzer (oh and external tools like KSync if they use those). In 7.0 I would have had more mixed feeling since you would still have had to use the physical name in VB scripts.

Finding and updating all references to fields in custom groups, forms, scripts, reports, templates, and external tools (KSync etc) is the cleaner solution but it is not cheap.

[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 \|

page cache (param): 2/23/2025 11:16:34 PM