Modern business process is essential for transforming organizational productivity in Microsoft 365. Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only...
Published Jul 06, 2020
Version 1.0
Blog Post
IvanCole-dxcecl I have been able to have Power Automate run on a classic calendar. In my case, it runs when a new calendar item is added. We use it for time off requests.
Chris McNulty I figured this day would come when I first started using Designer back in 2013 so avoided making any 2010 workflows. That said, there is one thing I wish Power Automate (and 2013 workflows for that matter) had -- the ability to Declare a list item ( List specifically not to be confused with a document library item) a record. I can do it in 2010 easily without having to resort to breaking inheritance and changing the permissions. While saying what I'd like in PA. is the ability to MOVE a LIST item to another list. Moving it means moving the version history as well. Just adding to another list does not help when I need the version history. That leaves me to have to manually use Content and Structure to move list items which I'm always afraid is another thing that will get retired with no replacement.