Multiple rows or records can be retrieved in Microsoft Dataverse using List Rows. You just need to introduce a structured query using either Fetch XML or OData queries. You should know that all columns are by default retrieved in List Rows if you do not mention the columns you want to retrieve explicitly.

Moreover, if the flows return all the columns then the performance of the flow is affected. In this regard, it is better to practice and perform tweak to mention the columns directly in the list rows action Select Columns field.

We have shown you an example so you can see how Select Column contains name and amount field only for the sake of Loan Entity. It only retrieves the record with only two columns and other columns are not retrieved in the output.

Be careful!!

You should remember that if you are mentioning column list in Select Columns then you need to use those columns which are actually mentioned in the list in next actions steps of the Power automate. Here, you cannot use other columns which are not retrieved. For this you should need to add other columns as needed.

We hope this read was helpful for you, if you have any questions you can contact us.

Search data in the Dataverse can be a big hassle for some people; I often hear people saying that it is very frustrating and confusing. Today, I will tell you five easy ways through which you can find data in the Dataverse.

1.    Dataverse Search

Most people think that Search Bar is not a very helpful place to look for important items and it is overlooked for its simplicity. You will be surprised to know that it has great power to help you find what you ask for. Simply enable your search in the bar; an easy way to do it is in Power Platform Admin Center

2.    Modern Advanced Find

The “go-to-way” feature has been modernized to help users find data. After modification, it has been introduced to the Search Bar. You simply need to open it and press “Search for Rows in a table using Advanced Filters”

This feature is available on each view with the option of “Edit Filters”

•   You can also do this by “Level Up Chrome Extension”

3.    FetchXML Builder in the XrmToolBox

FetchXML Builder is the go-to option for most consultants worldwide as it is the query language for Dataverse. You can use this tool to easily create a search and run it.

4.    SQL 4 CDS in the XrmToolBox

All credit goes to Mark Carrington for creating this efficient tool. It is one of the most popular tools to find data. Use SQL knowledge and apply it to Dataverse. You will be happy to know that it integrated very well with FetchXML builder and allows you to move back and forth between both tools.

Moreover, this magical feature also supports the options of:

•   Insert
•   Update
•   Delete

5.    Excel and Power BI

Most people prefer Excel and Power BI as it allows real analysis when connected to Dataverse. Once you connect these tools use the option of “Power Query” to perform the research.

This post will help you in using a new pipeline through Azure. You should know that Pipeline is very simple and enables you to transfer solutions from one environment to another; which later on can be used to publish your customizations as well. There is another thing; this post is only helpful if you have successfully configured the connection between the Power Platform environment and the DevOps environment.

How to Create your Pipeline

• The first step is to go to the Azure DevOps project and choose Pipeline.
• There you will create a New Pipeline and then click “Use the classic editor to create a pipeline without YAML”
• Next, you will need to tell Azure pipelines where you have stored your repository. You can also use Azure Repo or any other Repo that befits your needs. You should know that Azure Repo is your best option out there because it is easy to configure as compared to other ones.
• The next step is to choose a template; you can also go for the option of “empty job”.

• The following step includes the addition of tasks to agent Job 1 to build a new pipeline

You need to add the following tasks to your agent job

• Power Platform Tool Installer
• Power Platform Export Solution
• Power Platform Import Solution
• Power Platform Publish Customization
• Next, you need to find the variables tab and edit the window to add a new pipeline variable.
• You can name this variable according to the solution i.e. “Solutionname” and then set the value to the name of your solution in the Dataverse environment.

• Following the step above, you need to go back to the Tasks tab and configure the added tasks

1. Power Platform Tool Installer

No configurations are done in this step, you just need to add it and move to the next one!

2. Power Platform Export Solution

Here you will find your solution from Power Platform Environment and import it to the target environment.

• You will need to use a “Service Principal/Client secret” authentication type
• Once you are done selecting the required option; select the service connection you have configured to form a connection to the Power Platform environment
• For the solution name; use the variable you created earlier
• Next, for the solution output file, you need to use this value as $(Build.ArtifactStagingDirectory)\$(SolutionName).zip
• Next, check the box to export as a managed solution; do this if you are transferring this solution to a test or production environment; because if you move the solution to another environment this step is not needed.

3. Power Platform Import Solution

This step is very easy as you will be importing the solution to your target environment. So, select the service collect of the environment and use this value: $(Build.ArtifactStagingDirectory)\$(SolutionName).zip$(Build.ArtifactStagingDirectory)\$(SolutionName).zip

4. Power Platform Publish Customization

This step is also very simple; here you just need to select the service connection of the environment which is to be imported; it will enable you to publish all the solutions XML changes in the environment.

 

Congratulations you are done! Make sure you save your Pipeline and do not forget to test it.

It happened to be the response to a question on one of the PowerApps forums about how to use the Dataverse Choice (OptionSet) field to display a dropdown containing the phrase “All.”

The Choices function returns a table of the lookup column’s potential values.

Use the Choices function to provide your user a list of options from which to choose.

It’s simple to combine the term “All” with the Items attribute of the dropdown when using SharePoint as a Datasource. However, while implementing Dataverse, things are different.

SharePoint

ClearCollect( ColAllStatusSP, {Value: “All”},Choices(SPList.ChoiceName) );

Dataverse

Solution: As seen below, we have to loop over the Dataverse choice values.

ClearCollect( ColAllStatus, {Value: “All”} ); ForAll( Choices(GlobalChoiceName).Value, Collect( ColAllStatus, {Value: Text(ThisRecord.Value)} ) )

So, for the reason option will not fluctuate greatly, Collect and apply the values of the screen’s Onvisible parameter. You may need to filter the option field depending on use cases in some circumstances.

Summery

To include the word “All” in the Dataverse option field, we must loop through it and add it to the collection. You may utilize Concurrent to boost the page load performance.