Experimental Feature: Embedded Adaptive Card Designer from Audrie Gordon

A very good introduction to the world of the Adaptive Card. I was able to take out a lot of things here and will now create one or the other Adaptive Card myself.

You can see this video here on my blog because I have rated this video with 5 stars in my Youtube video library. This video was automatically posted using PowerAutomate.

Power Apps Errors Function when using Patch and other data source changes from Shane Young

Very helpful guidance and explanation on how to create a simple error handling within the app. I particularly like the part where you create variable notifications. I’m a big fan of variables and don’t like the hardcoded stuff.

You can see this video here on my blog because I have rated this video with 5 stars in my Youtube video library. This video was automatically posted using PowerAutomate.

Create Responsive Power Apps from SharePoint list from Reza Dorrani

This is the easiest way to create a responsive app with PowerApps. The basis for this is the automatically creating app of data from Sharepoint. With small customizations, this app is ready for all Screensize.

You can see this video here on my blog because I have rated this video with 5 stars in my Youtube video library. This video was automatically posted using PowerAutomate.

PowerApps Tracker App including Add row numbers to a gallery from Shane Young

With this formula you will save a lot of time and nerves. Because you can easily add the current row numbers to any collection (or via patch also data table). Watch this video.

ForAll (XY,
Collect (tempCollection,
Last (FirstN(
AddColumns (
DropColumns ( XY, row ),
“row” , CountRows (tempCollection)+1),
CountRows (tempCollection)+1)),
ClearCollect(XY, tempCollection),
Clear (tempCollection)

You can see this video here on my blog because I have rated this video with 5 stars in my Youtube video library. This video was automatically posted using PowerAutomate.

The Big 5 (Variables / Parameters) in PowerApps

Photo by Ann H on Pexels.com

If you create a PowerApp and look around on the internet for solutions, you will come across the following functions from time to time.

  1. set()
  2. updateContext({})
  3. with()
  4. navigate(…,…,PARAMETER)
  5. param()

In the following I will show you briefly what I use them for and why you should think about using them too.


  1. set() function
    This is probably the best known function of all. It sets the value of a global variable. Global variables are useful when you want to store a value and use it on different screens. This can be used in the OnStart, where you set style variables, the logged in user or if you select an element from a gallery and want to use this element somewhere else.

Set(
varUser,
user()
)


  1. updateContext({})
    This is the little brother of the Set function. Sets the value of one or more context variables of the current screen. I mainly use this when I want to change a value (true,false) to show/hide something for example. Mostly a pop-up or another input window.

    Here I set the variable “locPopUp” first to “true” and then again to “false”.

UpdateContext({locPopUp: true});
UpdateContext({locPopUp: false})


  1. with({})-function
    This function I discovered some time ago and is again the little brother of UpdateContext. Here “variables” are stored exclusively for a function and can only be referenced in this function. I use this mainly within functions, as soon as I have to use a certain function several times.

    In this example I write the variable “locText”, to which I then reference 2x in the further course of the function. Important: the With function is closed only at the end of all functions.

With(
{locText: TextInput1.Text},
If(
IsBlank(locText),
“noText,
TextInput1.Text
)
)


  1. navigate(…,…,{PARAMETER})
    This parameter was unknown to me for a long time, because I usually stopped after the first comma and closed the parenthesis. But if you put two more commas after the Navigate, you can pass one or more parameters to the screen you want to navigate by using the curly braces. This parameter is then only available on the following screen. (unless you write it into another variable or pass this value again)

    In this example I pass to Screen1 the parameter “locVariableNextScreen” with the text “Yes we can use it”.

Navigate(
Screen1,
UnCover,
{locVariableNextScreen: “Yes we can use it”}
)


  1. param()
    This provides access to parameters passed to the app when the user has it open. This parameter is usually used less often, as this is exclusively appended to the app’s URL. Thus it is possible to navigate the user to a certain page or to pass certain values to the app.

    Here I pass the parameter “Admin” with the value “true” in the URL. In OnStart I then set the global variable “varAdmin” with the parameter “true”. So I can enable additional settings for an admin, using this parameter. (Visible: varAdmin)

https://apps.powerapps.com/play/543654354453543543?tenantId=dasfdgdsgsfsdfsdf&Admin=true

Set(varAdmin,Param(“Admin“))


Extra tip: If you use a variable and want to use it as a boolean, which is always the opposite of the current state, use the “!” in front of the variable. This reverses the value.

This example reverses the value every time it is executed. If is currently true, it will be changed to false and vice versa.

UpdateContext({locPopUp: !locPopUp})

Power Automate get SharePoint Group Members & flow code snippets from Reza Dorrani

A very PowerFull tip from Reza in this video. We all know the “Add to clipboard” function. I already knew that this TAB works across the board. But the fact that you can simply pass on the “code” and then insert it will make my day-to-day work enormously easier.

You can see this video here on my blog because I have rated this video with 5 stars in my Youtube video library. This video was automatically posted using PowerAutomate.

Power Apps: Planning SharePoint Lists Relationships from Daniel Christian

I think these videos are fundamental when using PowerApps with SharePoint. You not only save your nerves, but also unnecessary workarounds -> Because with this tip you can interact easily and directly in the PowerApp.

I personally use the knowledge especially in SharePoint Customized Forms (with PowerApps). I don’t use LookUp columns or similar in the SharePoint list, but only within the app. So I have a better and easier control, where I can directly enter the functions without using any long “code snippets”.

Power Apps change the app owner with PowerAutomate

In the post of 2020-12-09 I showed the video of Shane Young, where it is shown how to change the AppOwner using PowerShell. However, there is another, perhaps even easier way to change the AppOwner. Using PowerAutomate.

Why should I change the owner of the app, which is the creator? One of the reasons that comes to mind is that the person has left the company, or you want to transfer all apps to one account.

Here is the short tutorial on how to change the AppOwner of PowerApps using PowerAutomate.

Here you can see the simple structure of a flow, which is triggered manually.

Next, the new AppOwner is searched for in the action “Search for user”. Make sure that this is unique and that only one user is found.

Then use the action “Set App Owner” and fill in the fields. Under Environment Name you can get the ID from the URL above. (2. on the picture below) The same applies to the PowerApp name. Just insert the App ID here. (1. on the picture below)

Finally insert the ID that comes from the action “Seach for user” and the AppOwner will be changed. (if you have the permissions)

 

Power Apps Date Difference Calculations for Business Days from Reza Dorrani

Calculation of days exclusive weekends and holidays in the Powerapp.

You can see this video here on my blog because I have rated this video with 5 stars in my Youtube video library. This video was automatically posted using PowerAutomate.