How to use optional parameters of Dataverse Search in Power Automate Flow?

As demonstrated in our previous blog, we can use the Dataverse search in Power Automate Flow comfortably. In this blog, we will have a look at how the optional parameters are used to limit the search as per our requirements. So, let’s dive in without further ado.

To quickly revise everything that we have discussed in the previous blog, below is an example to use the search API to find all the entities which have “Jim” somewhere in their indexed fields.

Now, the successful response will consist mainly of three things –

• Value
  • An array of all the matching records. By default, 50 rows are returned but can be changed from 1 to 100 using the Top
• Total Record Count
  • Returns the total number of matching records if the parameter is set to true. By default, will always be false and return -1.
• Facets
  • The results of the facet parameter i.e. additional filtering on the received search results.

It will look like this –

<

pre class=”lang:css gutter:true…

Source link