2/21/2025 6:01:02 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 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.
|
|
|
|
Dependency Lookups - How far can we take them?
Posted: 12 Feb 08 8:40 AM
|
I have a client who has redone the A/C/I functionality of Tickets. Instead of using cascading picklists, they are populating cascading listviews with recordsets generated from the preceding selection.
In depedency lookups, it appears that it is returning distinct values from a specified table/column based on a value passed from the parent item.
My problem:
1. Binding of each level can only be to fields in the MainEntity. I need to bind them to fields in an extension table. Extensions seem to work everywhere but here.
2. Instead of the table AreaCategoryIssue, my cascade will be generated from columns in the product table. I don't see this as a problem but would like to hear any other experiences with this control and extending it |
|
|
| |
|
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!
|
|
|
|
|
|
|
|