6/29/2025 9:32:45 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.
|
|
|
|
Area - Category - Issue dependency lookup problem! Please help!
Posted: 13 May 10 6:46 PM
|
i have a custom Area - Category - Issue but noticed in web that having categorys with the same name affect the issue list.
Example, 1st i create:
Area: area1
Category: test
issue: issue1
2nd i create:
Area: area2
Category: test
issue: issue2
When i go to the tickets and try to select Area1 and Area2 with category test, both returns issue1 and issue2 in the issues list. |
|
|
|
Re: Area - Category - Issue dependency lookup problem! Please help!
Posted: 14 May 10 5:24 AM
|
AFAIK it uses the textual value to determine the cascading of the area - category - issue, so Im not sure how you could change that. You mention it a is custom area -= category -issue screen? 2 options, either change the name of category "TEst" to something different for each instance, or if this is not possible, flag the record someway at the database level (Maybe set the Customer flag to F/T or something different to the other standard area - category - issues). This way you can have some code that will apply an additional lookupprefilter to the Issue list that will depend on the flag you set in the database. I.e. if the category selected had your special flag, only show issue records whose category had the special flag AND the category selected. This prefilter would be applied (or not) onchange of Category.
Make sense?
The downside to this is that it wouldnt be very versatile. It would only work in static instances. But hopefully you do not have too many instances where the categories are identical...hopefully... |
|
|
|
Re: Area - Category - Issue dependency lookup problem! Please help!
Posted: 14 May 10 11:30 AM
|
But the code of the AreaCategoryIssue lookup is:
<SalesLogix:DependencyLookupControl runat="server" ID="dplArea" ToolTip="nada" LabelCssClass="lbl" AutoPostBack="true" >
<LookupResultsHeaderStyle BackColor="ActiveCaption" Font-Bold="True" ForeColor="White" />
<LookupDialogStyle BackColor="Control" />
<LookupResultsStyle CellPadding="4" ForeColor="Black" />
<DependentLookups>
<SalesLogix:DependentLookup LookupEntityName="IAreaCategoryIssue" LookupEntityTypeName="Sage.Entity.Interfaces.IAreaCategoryIssue, Sage.Entity.Interfaces, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null" DropDownDisplayProperty="Area" ParentProperty="" PropertyDisplay="Area" BindingPropertyName="Area">
</SalesLogix:DependentLookup>
<SalesLogix:DependentLookup LookupEntityName="IAreaCategoryIssue" LookupEntityTypeName="Sage.Entity.Interfaces.IAreaCategoryIssue, Sage.Entity.Interfaces, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null" DropDownDisplayProperty="Category" ParentProperty="Area" PropertyDisplay="Category" BindingPropertyName="Category">
</SalesLogix:DependentLookup>
<SalesLogix:DependentLookup LookupEntityName="IAreaCategoryIssue" LookupEntityTypeName="Sage.Entity.Interfaces.IAreaCategoryIssue, Sage.Entity.Interfaces, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null" DropDownDisplayProperty="Issue" ParentProperty="Category" PropertyDisplay="Issue" BindingPropertyName="Issue">
</SalesLogix:DependentLookup>
</DependentLookups>
<LabelStyle Width="100px" />
</SalesLogix:DependencyLookupControl>
How can i apply a prefilter to the issue lookup if it is on a dialog. Remember the control itself is from the Controls.dll so i cannot modify it. |
|
|
|
Re: Area - Category - Issue dependency lookup problem! Please help!
Posted: 14 May 10 6:24 PM
|
I solved this issue with a little ugly workarround.
1-Create a field in the Architect.exe on the AreaCategoryIssue table called AREACATEGORY.
2-Import the new field in AppArchitect.exe on the AreaCategoryIssue entity, take note if it reads AREACATEGORY or Areacategory because Entity Framework is case sensitive. Re-build, Deploy...
3-Go to SQL and edit the field to be a Calculated Field of: Category + ' / (' + Area + ')'.
4-Change the Category dependent lookup to be AREACATEGORY.
5-Change the Issue parent to AREACATEGORY.
6-Create an onchange procedure to truncate the ' / (' + Area + ')' text of the Category field when you select an area-category-issue. You can doit with javascript.
GOOOOOLLLLLLLLLLLLLLLLL!!!!!!!!!!!! |
|
|
| |
| |
|
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!
|
|
|
|
|
|
|
|