Microsoft Dynamics CRM (Archived)

Javascript addpresearch not working in UCI

(1) Share

Report

Posted on by Community Member

HI Team

Javascript addpresearch not working in UCI, throwing error as "

UciError: Required parameter is null or undefined: handler"

Could you please help on this?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

ravikiranpatil24 5 on at

Like (0)

Report

Not working for me as well. Is there any bug around this?

Was this reply helpful? Yes No
a33ik 84,331 Most Valuable Professional on at

Like (1)

Report

Hello,

Can you please provide code you use?

Was this reply helpful? Yes No
Naveen Ganeshe 3,397 User Group Leader on at

Like (0)

Report

Hello Manasa,

It will be more investigable if you can share the code. However, there are some threads that might be helpful for you. Please see below link:

community.dynamics.com/.../addpresearch-and-not-working-in-dynamics-crm-365-v9

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hey Manasa,

I have applied a addPreSearch script just recently in UCI and it works fine.

I've noticed that the most important thing developing anything with JS for the UCI, is always to use the latest supported ways, which means you need to use the executionContext (and formContext) instead of the good old Xrm.

On the other hand, if you know the procedure on how to apply a addPreSearch you will know, that you need to add the presearch via calling another function, which will add a fetchXML query via addCustomFilter. Unfortunately you cannot pass the formContext further when you call the second function.

In order to do all this, I have come up with a little workaround using the execution context. I think the code says more than a thousand words. You simply will need to call the "LookupFilter" function onload and pass the executionContext as first parameter (tick the necessary box when adding the function on the form).

Cool thing is, it also works inside the BPF. To accomplish that, simply add "header_process_" as a prefix for the fieldname if this field is in the BPF:

I hope that my approach helps you or any other colleague from the Dynamics world experiencing issues with this requirement.

Was this reply helpful? Yes No