Home > PowerApps > Dataverse | Traditional Quick Find vs Enhanced Quick Find (2020 Wave 1 Update)

Dataverse | Traditional Quick Find vs Enhanced Quick Find (2020 Wave 1 Update)

I got a following question from a blog follower who recently started working on Dataverse on ‘Quick Find Search’.

Why the ‘Quick Find’ view not fetching the data though there are matched records?

So this article is for those who recently started working on Dataverse to differentiate Traditional vs Enhanced Quick Find view.

Traditional ‘Quick Find’:

  • Traditional ‘Quick Find’ fetches the matched rows irrespective of the current view.
  • As an example, below ‘Male Students’ view contain 2 records where Gender=Male.
  • If I search for a ‘Female’ record which is not part of this view, it will show up as below.

Enhanced Quick Find (2020 Wave 1 update):

  • With the 2020 Wave 1 update, by default ‘Quick Find’ fetches the matching records only from the currently selected view.
  • As an example, If I search for a ‘Female’ record while a ‘Male Students’ view selected, no records would be fetched. This is because of the search confined to the selected ‘Male Students’ view.

How to enable Traditional Quick Find post 2020 Wave 1 Update:

  • Post 2020 Wave 1 Update, ‘Traditional’ Quick Find will be turned off, by default.
  • To enable ‘Traditional’ Quick Find, from the Admin Center, select the Environment, go to Settings -> Features and turn on the “Use quick find view of an entity for searching on grids and sub-grids” setting.

🙂

Categories: PowerApps Tags: ,
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: