The rating control in Adaptive Cards was on a roadmap. Long time ago. However, no updates were published and still no such control is available oob. Despite that, it is still possible to build a star rating, maybe not the perfect one, but working one for sure.
I have faced to day a very bizarre situation when I was trying to share an element within a SharePoint Online library, with a user who didn’t have access to the site at all. After the element was shared, user was getting access denied unless was added to “Members” permission group.
In this post I would like to share with you my latest findings about the ways you can mention actually anything in Microsoft Teams in messages sent from Power Automate, whether it is a user, a tag, a channel or a team.
This post was inspired by a message that Sergi Dominquez sent me on Twitter. It turns out, that when a request from Actionable Message in Outlook is sent to a server, Outlook waits only a specific amount of time for the response.
In Adaptive Cards there are multiple ways to show and hide content depending on other content or conditions, or even user interaction. But despite that most of them is available since the version 1.2 (so quite early) it requires a bit of knowledge how to actually implement them.
I am working with Power Automate Desktop for more than a year now. Over that time I faced a lot of weird errors that were occurring somewhere between cloud flows I used to trigger RPA and the bots themselves. Let me help you understand where are they coming from and how to resolve them (or create workaround).
Images always enricher Adaptive Cards designs. However in Microsoft Teams max. message payload is just 25KB and that includes also the size of card’s JSON. Therefore it is very often not possible to display even the smallest image inline. What other options we have?
When writing my previous post on working with Tasks in Power Automate I realized existence of a column name Flow Notification URI inside of Flow Approval table, which I so far really underestimated. Let me show you how powerful it is!
After I have successfully published and got certified with my first connector in the Independent Publisher connectors program (myStrom connector), I decided to share my journey and experiences with you, so that you can as well share your work with the whole world!
This is a re-post of the summary we wrote as a team after participating in hackathon during the South Coast Summit this year. The event was epic. The hackathon even more. Enjoy! The app and more details about our solution can be found here: https://github.com/LuiseFreese/HackSouthCoastSummit/.
I was seeing this kind of error in Nintex for Office 365 workflows for some time, but actually never had enough determination to check what is the root cause. However when customer started asking, I started digging.
Recently I faced an odd situation, that user was complaining that they have access denied to the site, even though when I was checking their permissions, SharePoint was displaying, that they do have “Contribute” access level granted.
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?
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.
Not so long ago I wrote a post where I was describing how to integrate WinAutomation with UI flows (here). It didn’t take much time for Microsoft to release a dedicated connector, that does the same thing, but well… Is much easier to use!
With this new trigger you can add create a new level of governance for your Microsoft Teams. Especially when speaking about the on-boarding users or other automated processes for newly added Teams members.