I blogged recently here about how you can change the default operator behavior for the Lookup Controls found on the smart parts in the SalesLogix Web client. The SalesLogix group area also has a lookup control, that while it looks similar to the standard Lookup Control is actually a separate control with different code base. However you can make a similar type of change to this control as well.
The Group Lookup behavior is largely controlled by client side libraries. This client side code is contained in several files inside the VFS structure. The location is under Portal Manager…Sage SalesLogix…Support Files…Sage-Controls…Sage-Controls-Group
The file involved in this behavior is the sage-controls-group-lookupmanager.js file. If you look in that file you will see a function defined called getTemplateObj that looks like this:
Sage.GroupLookupManager.prototype.getTemplateObj = function() {
var mgr = Sage.Services.getService("GroupLookupManager")
mgr.setupTemplateObj = (window.lookupSetupObject) ? window.lookupSetupObject : {
fields: [{ fieldname: '', displayname: ''}],
operators: [{ symbol: 'sw', display: 'Starting With' },
{ symbol: 'like', display: 'Contains' },
{ symbol: 'eq', display: 'Equal to' },
{ symbol: 'ne', display: 'Not Equal to' },
{ symbol: 'lteq', display: 'Equal or Less than' },
{ symbol: 'gteq', display: 'Equal or Greater than' },
{ symbol: 'lt', display: 'Less than' },
{ symbol: 'gt', display: 'Greater than'}],
numericoperators: [{ symbol: "eq", "display": "Equal to" },
{ symbol: "ne", "display": "Not Equal to" },
{ symbol: "lteq", "display": "Equal or Less than" },
{ symbol: "gteq", "display": "Equal or Greater than" },
{ symbol: "lt", "display": "Less than" },
{ symbol: "gt", "display": "Greater than"}],
index: 0,
hideimgurl: 'images/icons/Find_Remove_16x16.gif',
addimgurl: 'images/icons/Find_Add_16x16.gif',
hideimgalttext: 'Remove Condition',
addimgalttext: 'Add Condition',
addrowlabel: 'Lookup by:',
hiderowlabel: 'And:',
srchBtnCaption: 'Search',
errorOperatorRequiresValue: 'The operator requires a value'
}
}
Similar to the other lookup control, the “default” operator for the lookup control is based on the order the operators get added to the list. If we change the order to something like this, the default lookup will be contains instead of starting with:
Sage.GroupLookupManager.prototype.getTemplateObj = function() {
var mgr = Sage.Services.getService("GroupLookupManager")
mgr.setupTemplateObj = (1!=1) ? window.lookupSetupObject : {
fields: [{ fieldname: '', displayname: ''}],
operators: [
{ symbol: 'like', display: 'Contains' },
{ symbol: 'sw', display: 'Starting With' },
{ symbol: 'eq', display: 'Equal to' },
{ symbol: 'ne', display: 'Not Equal to' },
{ symbol: 'lteq', display: 'Equal or Less than' },
{ symbol: 'gteq', display: 'Equal or Greater than' },
{ symbol: 'lt', display: 'Less than' },
{ symbol: 'gt', display: 'Greater than'}],
numericoperators: [{ symbol: "eq", "display": "Equal to" },
{ symbol: "ne", "display": "Not Equal to" },
{ symbol: "lteq", "display": "Equal or Less than" },
{ symbol: "gteq", "display": "Equal or Greater than" },
{ symbol: "lt", "display": "Less than" },
{ symbol: "gt", "display": "Greater than"}],
index: 0,
hideimgurl: 'images/icons/Find_Remove_16x16.gif',
addimgurl: 'images/icons/Find_Add_16x16.gif',
hideimgalttext: 'Remove Condition',
addimgalttext: 'Add Condition',
addrowlabel: 'Lookup by:',
hiderowlabel: 'And:',
srchBtnCaption: 'Search',
errorOperatorRequiresValue: 'The operator requires a value'
}
}
One important thing to note is the change of the condition. T his is needed to force the page to always load from this library rather than the behavior built into the lookup control in the Sage web control assembly.
This code is also in the Sage-Controls.js file which is one level up. This file is a minified consolidated file of all of the other library files. This minified version is what is actually used by the deployed site so you will need to make the same changes to that file in order to see the changes take effect.
One other thing to note is that if you do not see the behavior change after making these modifications, you should clear out your browsers history cache as it is likely it has stored the old client side code and is using that.