This post was inspired by a situation I faced at one of my customers. I was migrating SharePoint 2010 to SharePoint Online and in one site customer had many lists, where users were able to create items. Every time someone created or updated an item, SharePoint Designer workflow was sending them confirmation e-mail. Case was, that the lists were using the same workflow simply replicated per list.
In SharePoint Online, whenever you create a library and turn on “Require check-out” before editing documents option or not, users are able to open files for collaboration in browsers or in their local Office clients. When they do that, the file is getting locked from access that could lead to its metadata changes. If you create Power Automate flow which purpose is to update file’s metadata or approval status it will end up with failure when trying to do so.
This post is totally focused on description of the Dataverse structure that is used to store details about runs of all Power Automate Desktop ui flows. Or as called today: desktop flows and cloud flows built using Power Automate platform.
This is going to be a short post. I want to share with you my approach for overcoming the threshold called data row limit, that prevents function “Collect” to get more than the set number of items. The data source in my case is SharePoint.
In my previous post I guided you through a list of steps required to build, send and handle response from Adaptive Cards as Actionable Messages in Outlook. Let me now tell you, how to secure the response.
It has been a while since I first thought about writing this post. Recently I had more questions around this topic and somehow realized, that indeed this is something about Adaptive Cards that I haven’t yet written about. So let me fix it with this ultimate guide.
I’ve been asked that question multiple times – how to assign a single Adaptive Card to multiple Microsoft Teams users and then collect responses. The point is, that action “Post an Adaptive Card to Teams user and wait for response” lets us to collect just a single response at a time. So how can we do it?
This topic has been continuously raised by multiple people I’ve been talking to. How can a user be mentioned in Microsoft Teams when a message is sent from Power Automate? This issue seemed to never been really possible for us, Power Users, until couple days ago Microsoft released new action in Microsoft Teams set in Power Automate called: “Get @mention token for a user”. It’s even cooler, because it works with Adaptive Cards too!
In the beginning of July Microsoft has added two new triggers for Power Automate to integrate better with Microsoft Teams: For a selected message and When a new team member is added. In this post I will go you in details through the first one from them.
With a huge pleasure I would like to announce that we (as I had some role to play in this as well!) have completed work over preparation and testing of the Microsoft RPA labs!