I recently came across an interesting problem when trying to match the logged in user to a user selected in a person column. Even when the user is the same, the result would sometimes not be a match. In this post, I’m explaining the cause of this problem and a possible solution.
In this blog post I’m creating a UI element to add items into a dynamic list using only standard canvas controls. This reminded me of filtering in a webshop using tags, so I called it a tag box component.
A couple of months ago, I shared how to create a button with an icon as a component. With the new behavior property functionality in Power Apps, we can now improve this component so it can not only navigate, but trigger any function you want…
Galleries are one of the core components of Power Apps canvas apps. In this post, I’m sharing a solution to expand and collapse a row in a gallery to show additional information before going to a second detail screen.
In the final blog post of this series I’m presenting a solution to optimize your Power Apps trigger input parameters in a Power Automate flow using JSON. This is a flexible solution that separates the trigger from the logic of your flow.
After understanding how Power Apps trigger input parameter names are generated in Power Automate, we can use this knowledge to create a uniform approach for these input parameters. This is the second part in a 3-part series on optimizing Power Apps trigger input parameters.
When you’re using a Power Apps trigger in a Power Automate flow, the input parameter names are generated automatically. In this first post of a 3-part series, I’m explaining how these names are generated so that we can look at how to optimize this in the following posts.
It’s very easy to customize the standard SharePoint form for a list or library using Power Apps. However, out of the box it’s not possible to use this to create document sets. In this post I share a simple solution to create document sets from a Power Apps SharePoint form.
The standard button control in canvas apps doesn’t allow adding an icon. For one of my recent projects, I needed to create buttons that do have an icon on them. In this post I’m sharing the steps taken to create this button…
In documentation typically only one data policy is applied to an environment and its effects are described. I was wondering what happens when you apply multiple policies to an environment, here’s what I found…