Flow Tip: Use Condition or Scope control to skip or debug Flow action(s)

As part of the Flow design process, I often end up building in some debug actions like Send email, Set variable etc. to capture/troubleshoot values that in turn help along with the actual design. But I’d want to retain those actions for debugging later rather than recreate them. Also when building/designing complex Flows I need to find failing actions and test or disable subset of actions.

Issue

Ideally, you want to be able to deactivate or skip a specific action or set of actions. Microsoft Flow does not have this feature available at this point of time. This requires you to either create a copy of the flow for testing purposes or debug by deleting actions only to realize later that those actions you just deleted weren’t causing the issue. This means you’ll need to re-configure those actions from scratch to restore your Flow design which can be time consuming.

Resolution

Below are two approaches I’ve used and found useful for disabling/skipping actions for testing and debugging purposes.

Continue reading

Role Based Security In PowerApps using SharePoint Groups

Recently a customer asked if PowerApps can support role based security controlled by SharePoint Security Groups. For example, can you make an Admin screen that is visible only to users who belong to a specific SharePoint Security Group? Yes, you can and this is where Microsoft Flow comes to the rescue!

This blog post is an attempt to share an approach for finding out the SharePoint Group membership of a signed in user and make certain features or screens of an app available to them.

Continue reading