onChange of an optionset apply presearch on a lookup field

(0) Share

Report

Posted on by EBMRay

905

Hello,

In a form i have an option set that has two options (Type A and Type B), and a lookup field.

OnChange of the option set, I would like to apply a presearch or addCustomFilter to only show the data that are based on the type that is selected from the option set.

Could you please point me in the right direction to achieve this kind of requirement?

I would highly appreciate if you could provide a very small sample code on how it can be done.

Any help is greatly appreciated.

Best regards,
EBMRay

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Abdul Wahab 12,119 Moderator on at

Like (1)

Report

Hi EBMRay.

My suggestion is to avoid code. Convert option set into a lookup because we have a filtering option available between two dependent tables.

Was this reply helpful? Yes No
Suggested answer

Abdul Wahab 12,119 Moderator on at

Like (1)

Report

Hi EBMRay,

Here you find details about the pre-search and addCustomFilter with examples:

addPreSearch (Client API reference) in model-driven apps - Power Apps | Microsoft Learn

addCustomFilter (Client API reference) in model-driven apps - Power Apps | Microsoft Learn

Solved: Filter lookup field using addCustomFilter control ... - Power Platform Community (microsoft.com)

Was this reply helpful? Yes No
EBMRay 905 on at

Like (0)

Report

Hello Abdul Wahab ,

Thank you for providing those helpful documentations.

The reason I am using options set instead of lookup is to avoid the user keep changing the label title and to always have a static value that you can rely on in your code.

Because using lookups he can at any time rename type A to type Z and that might affect any filtering logic that you might have (Plugins, JS, a workflow...)

What do you suggest in that case?

Awaiting your response.

Best regards,

EBMRay

Was this reply helpful? Yes No
Verified answer

Abdul Wahab 12,119 Moderator on at

Like (1)

Report
Hi EBMRay,

There is no doubt you are using the most effortless way.

"to avoid the user keep changing the label title and to always have a static value that you can rely on in your code."

You can prevent updates using security roles similarly prevented in the option sets.

You have a record GUID similar to a value for the option set.

I am referring to the low now code. When you use lookup by replacing the 'option set'. You can filter the records on a model-driven app with a configuration... It will also help you maintain dependencies...

"Because using lookups he can at any time rename type A to type Z and that might affect any filtering logic that you might have (Plugins, JS, a workflow...)"

I do not think there is a still need to answer this...

Was this reply helpful? Yes No

Join the conversation

Community site session details

onChange of an optionset apply presearch on a lookup field

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

onChange of an optionset apply presearch on a lookup field

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates