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.
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…