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...
Post a Comment

Back ( ) and Navigate ( ) - Canvas App

 Back ( ) & Navigate ( ) - Canvas App


Canvas App - Back () and Navigate ()


PRE-REQUISITE

  • Login to your Power Platform
  • Create a Canvas App of your desired screen-size

NAVIGATE ( )

Navigate allows you to switch between screens. That is, telling my app that when I click some UI element/Control [like a button], I want this screen to appear/be displayed on the screen.

BACK ( )

Back allows you to get back to the screen which was displayed before the current screen. That is, telling my app to go back to previous screen when I click on some UI element [like a back button].

USING NAVIGATE AND BACK IN CANVAS APP

A minimum of two screens are required to switch between them using Navigate and Back.

Adding new screen in the Canvas App



Objective 1: I will navigate from Screen3 to Screen4 using a button click and Navigate formula

Insert a button and format it as you desire
Insert Button - Canvas App


Use the formula "Navigate(ScreenName)" in the OnSelect property of the Button. Then,  Play the app to see when the button is clicked, we navigate from Screen3 to Screen4.

Navigate - Canvas App




Objective 2: I will use Back to go back from Screen4 to Screen3 using the Back Icon and Back formula

In Screen4, Insert Back Icon and put "Back ( )" formula in the OnSelect property.
Now we can navigate between screens
Back - Canvas App


Extra Fun!

While navigating between screens, we can give it fun transitions like, Sliding left, SlidingRight Fading, etc.
Here's how you do that!
Transitions - Canvas App


To explore more on transitions, Go here👉 Transitions With Navigate & Back

Thank You for visiting my blog.

Please leave a comment if you have any questions.

Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

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 "...
Post a Comment
Read more

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 ...
Post a Comment
Read more