This post is inspired by some recent talks I have delivered. I will describe you deeply how approval tasks are organized in Microsoft Dataverse and what can we do with them.
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/.
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.
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.