Skip to main content

Database actions - PAD

  POWER AUTOMATE DESKTOP - DATABASE Pre-Requisites Power Automate Desktop Access to database  Under the database action, we have only three sub actions, namely: Open SQL connection Execute SQL statement  Close SQL connection Open SQL Connection The first step is to connect to the database. So, we will use the Open SQL connection action and provide a connection string to establish the connection (the connection string in the video is a sample). When the connection is successful, the connection details is stored in a variable during execution. Execute SQL statement This action can be used to execute SQL queries. Here, I am using select query and the result is stored in a variable of type datatable. Close SQL connection It is a best practice to always close the database connection once the required queries are executed. YAY! BONUS!😮 How to execute a stored procedure using database action? Stored Procedure without arguments Stored Procedure with arguments (Comma separated in...

Build Canvas App with Microsoft Dataverse

Time to build a Canvas App in Power Apps!

Pre-requisite
  • Log In to Power Platform
  • I will be using Pizza Table which I created in my previous article. You may Create Pizza Table or you may choose to use any other table available in the Dataverse.
STEP 1: Navigate to "Create" and click on "Microsoft Dataverse".



STEP 2: Create "+New Connection"




STEP 3: We are going to create a connection to the Microsoft Dataverse to fetch the Pizza table.



STEP 4: Search, select Pizzas Table and Connect. The Canvas App editor opens.




STEP 5: Take a look at the "Tree View", "Canvas", the Play Button on top, the Screen on the RHS with Properties, Adavanced and Ideas tab.
In the Tree View, you can see three screens: "BrowseScreen1", "DetailScreen1" & ""EditScreen1". You may click on each of it and see those screens on your canvas.
The play button can be used to use the app.
The screen on the right side can be used to set different features to the select screen and its components.


STEP 6: Click on Play.



STEP 7: I will click on + to add more Pizza options. Uh-oh! it looks like the screen is not asking us for correct information. Lets fix that.


STEP 8: Close and go back to the Canvas App editor. In the Tree View, select and expand the "EditScreen1" screen.


STEP 9: Select the component "EditForm1".


STEP 10: In the right-side, under Properties tab, click on "Edit fields" and add necessary fields.
Fields added: Size, Crust, Cheese, Sauces, Toppings
You may also re-arrange the fields.


STEP 11: Now, lets play the app again and add the details.
                      
 

You may explore the app and the editor.

Have Fun!


Please feel free to reach out if you have any doubts.


Comments

Popular posts from this blog

Database actions - PAD

  POWER AUTOMATE DESKTOP - DATABASE Pre-Requisites Power Automate Desktop Access to database  Under the database action, we have only three sub actions, namely: Open SQL connection Execute SQL statement  Close SQL connection Open SQL Connection The first step is to connect to the database. So, we will use the Open SQL connection action and provide a connection string to establish the connection (the connection string in the video is a sample). When the connection is successful, the connection details is stored in a variable during execution. Execute SQL statement This action can be used to execute SQL queries. Here, I am using select query and the result is stored in a variable of type datatable. Close SQL connection It is a best practice to always close the database connection once the required queries are executed. YAY! BONUS!😮 How to execute a stored procedure using database action? Stored Procedure without arguments Stored Procedure with arguments (Comma separated in...

On Block Error - PAD

POWER AUTOMATE DESKTOP - ON BLOCK ERROR During development, testing or the actual execution of the desktop flows, we might get into errors. When error occurs, we might want the flow to exit gracefully, run another subflow or even set a value a variable. This is exactly why we use On Block Error action for. Here is a quick example on ways to use On Block Error:   We place the other actions within the "On Block Error" and "End" actions: Actions within On Block Error, There are options to Continue Flow Run or Throw Error. Throw Error will throw the error and stop the flow during run-time. If the Continue Flow Run option is chosen, the action can be repeated, we can skip to a Label or end of block or beginning of block or even go to the next action. If we have logical actions like division by 0 or trying to access a out-of-bound index from a list or datatable, then we can toggle on the "Capture unexpected logic errors" option. We also have the option to "...

Microsoft Dataverse & Power Automate - Part 1

POWER AUTOMATE & MICROSOFT DATAVERSE - 1 PRE-REQUISITES Login to Power Automate Create a manually triggered flow In this post, I will be using the data that is available in the Accounts table. In Cloud flow, we can use the dataverse connector and perform multiple actions as required. LIST ROWS IN DATAVERSE Use List rows action to list rows/records from a selected table. Use Apply To Each control to go through each row in the table. Data in the Dataverse table Accounts is shown. In Cloud flow, Use List Rows and Apply to each to get data from dataverse and loop through each row. Test Time: LIST ROWS WITH SELECTED COLUMNS From dataverse table, fetch the selected columns only. Multiple column names can be comma separated. Fetch the logical name of the columns (to be selected) from the Dataverse table. (In my observation, fetching only required rows, reduces the execution time) Enter the logical name of the column in Advanced Options of the List rows action. Test Time: Next: List Rows ...