Hi, in reference to this article:

http://customerfx.com/pages/integrationblog/2012/05/22/changing-the-default-condition-operator-in-the-salogix-group-lookup-control-in-the-saleslogix-7-5-4-web-client.aspx

Does anyone know how to do this in SLX 8.1 as the code as changed a lot and cant seem to find the relevant javascipt files?

Basically I would like to change the default operandor in the Account Lookup from "Starting with" to "Contains" as well as defaulting the focussed field to the text field for searching instead of the first field.

Regards,

Byron

It may not be simple the first time, but once you've done it once, it will help you extend the functionality across all JavaScript code.

You need to substitute the function "sortedConditionManagerFields" from the class "Sage/UI/ConditionManager" (see the file "jscript\Sage\UI\ConditionManager.js"). In order to extend the class, see the BigDeal customizations for an example on how to properly customize files in the jscript folder:

http://customerfx.com/pages/integrationblog/2013/10/14/saleslogix-v8-big-deal-example-file.aspx

Inside your custom JS file, substitute the widgetTemplate this way:

ConditionManager.prototype.getOperatorsByField = function (field) {
 // OOB code here, with customizations
}

The only thing you need to change to the original getoOperatorsByField OOB code is to change the order of the "stringLikeOptions" so the "Contains" (like) operator is shown in the first place for every Lookup control.

If you want to do so only for Account, you may check for the current family or any other information that can be accessed from the "this" object or any other piece of code.

Regards,

     Marcos

I maybe being dumb - but, in Tools | Options | Group - there is the option Default Lookup Condition - this defaults to Starting With. Wouldn't you just change it here ?

Mike is right. The customizations I mentioned were part of other customizations that included changing the order of the Lookup options list, forcing the first operand to a specific one, etc. So it would be overkilling for the problem stated by Byron.

Mike's solution is simpler for this particular problem.