Using addCustomFilter() to filter lookups in dynamics 365

(0) Share

Report

Posted on by Jamal JEK

Hi all,

i am using addCustomFilter() and the addPreSearch method to filter the "account" lookup in the opportunity entity, but it only works when i click the search button and when i try to type in field the filter doesn't work. is this normal?

OpportunityTest.setParentAccountIdFilter function is set in the form Onload event handler.

var OpportunityTest = window.OpportunityTest || {};
OpportunityTest.setParentAccountIdFilter = function (executionContext) {

    // get the form context
    formContext = executionContext.getFormContext();
    formContext.getControl("parentaccountid").addPreSearch(OpportunityTest.filterCustomerAccounts);
}

OpportunityTest.filterCustomerAccounts = function () {

    // Only show accounts with the type 'marketingonly'equal to yes
    var customerAccountFilter = ""   ""  
        " ";
    formContext.getControl("parentaccountid").addCustomFilter(customerAccountFilter, "account");
}

All responses (2)

Answers (2)

Verified answer

sdfasdf 840 on at

Like (1)

Report

RE: Using addCustomFilter() to filter lookups in dynamics 365

Since you're using the PreSearch event, this event only gets triggered when you tried to do the search. Maybe you don't need to use the PreSearch event here. Instead, just add your custom filters using the OnLoad event, like this:

var OpportunityTest = window.OpportunityTest || {};
OpportunityTest.setParentAccountIdFilter = function (executionContext) {

// get the form context
formContext = executionContext.getFormContext();
// Only show accounts with the type 'marketingonly'equal to yes
var customerAccountFilter = "<filter type='and'>" + "<condition attribute = 'marketingonly' operator = 'eq' value = '1' />" +
"</filter > ";
formContext.getControl("parentaccountid").addCustomFilter(customerAccountFilter, "account");

}
Verified answer

gopi.royal999@gmail... 430 on at

Like (1)

Report

RE: Using addCustomFilter() to filter lookups in dynamics 365

I haven't tested it though, did you try by disabling Recent Records on the lookup?