8/17/2025 9:26:50 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 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.
|
|
|
| |
|
Re: What Rocket Scientist made it so you can't bind webforms to userfields in Account and Contact tables?
Posted: 20 Feb 09 3:41 AM
|
Matt,
This is default behaviour rather than a fixed behaviour. I think the reason for this is that now we have the ability to add properties / fields to the core entities / tables, it was probably deemed inappropriate to use the user fields. A better approach is to use new fields. I can see where Sage are coming from with this decision.
Either way, the user fields are set up as properties in the Account. They have simply been set not to include them within the Account object model.
To include them simply do the following:-
1. Open the Account entity under 'SalesLogix Application Entities'.
2. Scroll down to the user field you wish to expose.
3. Tick the 'Include' check box
4. Save
5. Build interfaces.
I have found that if changing 'Include' properties, it is usually necessary to do a CTRL Build as the changes are not always picked up with a standard build.
You will now be able to see the User Field under the account for the purposes of binding.
Hope this helps,
Martin |
|
|
| |
| |
| |
|
Re: What Rocket Scientist made it so you can't bind webforms to userfields in Account and Contact tables?
Posted: 25 Feb 09 12:39 AM
|
Originally posted by Sankar
its sad to know that its true for custom tables too... we are upgrading from 7.2 LAN to 7.5 Web... we have 100s of custom tables. its such a pain to add each and every custom table to the entities... |
|
I'm not sure I follow. If you have a custom table that you bring in as an entity, add fields are included in that custom entity by default. Am I missing what you mean by this? |
|
|
| |
|
Re: What Rocket Scientist made it so you can't bind webforms to userfields in Account and Contact tables?
Posted: 26 Feb 09 5:05 PM
|
I agree with this functionality. If only Userfield1 and and Userfield5 are used in your system, you can enable only those Properties and the unused userfields won't be cluttering combo boxes elsewhere in AA that allow you to select properties. You can also rename the property to something more descriptive of the data being stored there, such as "SoftwareVersion" or "AppointmentDate."
One warning though, in 7.5.0 (haven't tested this in SP1), a descriptive name you assign to a userfield in an entity isn't recorded in a bundle, although it is when you display it in a QuickForm. This will cause an error if you don't go back in to rename the property.
|
|
|
|
Re: What Rocket Scientist made it so you can't bind webforms to userfields in Account and Contact tables?
Posted: 04 Mar 09 5:43 PM
|
Personally in versions prior to 7.0 when doing a customization I always tried to use an extension table rather than the userfields. In 7.0 and later I added the new fields rather than using the userfields. My practice was at best to use the userfields for things like data migration ids, something that had value initially, but wouldn't be used as long term in the system. BUT, as I'm sure everyone else here has had to do, I have had to follow other developers who thought nothing of using the userfields, with forms, scripts, crystal reports, and even scribe and knowledgesync jobs pointing to them (ugh), in these scenarios its not easier to move the data to a more appropriate field.
I am just perturbed at Sage for arbitratily hiding these things by default. It may not be a best practice, but it's been done, and we have to accomodate it. To be quite frank, I'm on the fence regarding SalesLogix anymore - if they do away with the LAN client in upcoming versions, they are left in reality playing catchup with MS CRM - going from having a more mature deployment than MS, to having a less mature (and quite frankly almost illogical) application architect that is trying (and failing) to emulate MS CRM.
Thanks for the info on how to enable these fields though. It is appreciated. Even if I don't agree with the thought behind hiding them (but who here ever agrees with everything done by another developer) 
All of our custom fields and tables go by the wayside once they implement unicode support anyway. So it's square one even for those who have developed customizations solely in the 7.5 web client I'm sure... |
|
|
|
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!
|
|
|
|
|
|
|
|