Login / Register  search  syndication  about

          Kris Halsrud's Blog

Kris Halsrud on development and Integration with CRM and Development

Changing the default condition operator in the SalesLogix Group Lookup Control in the SalesLogix 7.5.4 Web Client

 

 

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.

 

 

What's This?
  
Bookmark and Share

About Kris Halsrud

   Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.


Related Content
   Confirming Actions With an "Are you sure?" Prompt in Infor CRM (Saleslogix)
I'm not a huge fan of bugging end users. I figure, if an end user clicked something, he or she meant
Posted on Nov 18, 2014 by Ryan Farley to Ryan Farley's Blog
 
   Manipulating the DependencyLookup Control in the Infor CRM Web Client (Formerly Saleslogix)
 The Dependency Lookup control in the Saleslogix web client is what is used for the hierarchical Are
Posted on Nov 14, 2014 by Kris Halsrud to Kris Halsrud's Blog
 
   Infor CRM (formerly Saleslogix) Statement of Direction
Learn more about the future of Infor CRM. Recently I received my login information for the Infor Partn
Posted on Nov 13, 2014 by Brianna Ojard to The Inbox
 
   Adding a report link to the Common Tasks pane in Infor CRM (formerly Saleslogix)
When you are viewing an Entity Detail page, the Common Tasks pane on the right of the page provides a nu
Posted on Nov 12, 2014 by Jason Buss to Jason Buss' Blog
 
   How to Sum a Collection using Hibernate Criteria and Projections
 To sum the results of a criteria collection you can use code such as the following, which gets the
Posted on Nov 07, 2014 by Kris Halsrud to Kris Halsrud's Blog
 
Comments

No Comments

Leave a Comment

(required)  
(optional)
(required)  
Add
All contents Copyright © 2014 Customer FX Corporation
Customer FX Corporation
2324 University Avenue West, Suite 115
Saint Paul, Minnesota 55114
Tel: 800.728.5783

  Follow @CustomerFX on twitter
Follow the best news, tips, and articles
  Subscribe to Customer FX on youtube
Watch SalesLogix tutorial videos from Customer FX
Login / Register