This is a quick tip post. I am facing this problem myself quite often when working with Nintex for Office 365, especially in “Classic forms”. Sometimes, when you click the “preview” icon, the dialog window pops up, covers the designer with an overlay and… freezes. How to solve it?
When working with LUIS (Language Understanding Intelligent Service) from Microsoft, the most common scenario is that this is used in business processes. The very important feature of the service is that it can be trained with new utterances. This can be done either manually, via user interface or… using service’s REST API. Let me show you how to do it using Power Automate.
When you build RPA to handle processes in SAP, it is a good practice to check what status bar displays every time bot confirms data inserted on a screen or tries to navigate away from it. Just to be sure, there is no warning or error message, that should be handled by a bot.
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?