Question about Global/Quick Find across regions

(0) Share

Report

Posted on by Community Member

Hi,

I have a client with offices in different countries. They have a requirement that when using either the Global search or Contact quick find, that the results are filtered by the region of the office of the person doing the search, e.g. UK office user search for "John Smith" returns John Smith contacts marked as being associated to the UK office business organisation (via lookup on contact record).

I was wondering how I might achieve this if I'm only able to add 1 quick find view for the contact entity?

Any guidance would be much appreciated!

Thanks,

Andrew

Categories:

Customization / Solutions / SDK and API

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

Wayne Walton 13,730 on at

Like (1)

Report
Copy link

Link copied!

The search functionality is scoped by the same security roles that govern what a user can see. So the most straightforward way to do this is to make Business Units based on geography, make sure Read permissions are set to Business Unit and not Global, and then your search results will be limited by security.

If this is not acceptable, you're looking at custom development.

Was this reply helpful? Yes No
Verified answer

Kokulan 18,054 on at

Like (0)

Report
Copy link

Link copied!

Hi

Like Wayne suggested, best way to isolate records to regions/locations, you could create Business Units but if your business processes and security is not modelled that way and if you only want the Quick Find or Global Search results, you can look into Creating Retrieve multiple plugins, intercept the query and add conditions dynamically to filter the results only to the current users office region

Please have a look at the example below that just adds more condition to the query

[View:https://community.dynamics.com/crm/b/crmeventexecutionpipeline/archive/2018/12/10/append-search-column-s-in-quick-find-view-microsoft-dynamics-365:750:50]

One thing to note, the example is shown in the above link, the query parameter passed to the plugin is converted to QueryExpression. This will work for the classic interface but won't work on Unified Interface. For unified interface, you have to convert the query parameter passed to the plugin to FetchExpression

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks for the reply Wayne, that will do the trick

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thank you Kokulan, I appreciate the detailed response! Thankfully the Business units should suffice.

Was this reply helpful? Yes No