Ok, so some time ago, I have committed a post about an issue which occurs, when one tries to turn on a flow deployed to another environment, that has a circular reference with other flows.
The Microsoft Graph API is just another, extremely useful API, that can be used in variety of automations within the whole Microsoft 365 ecosystem. I am quite often using it with Logic Apps processes, that are running on application permissions.
I have been struggling with this topic for some time. Almost every time, when I was supposed to work with SharePoint API in Power Apps or Logic Apps, I was googling and going through the same partial solutions.
Have you faced this issue when trying to turn on a child flow, that you deployed to another environment? I think I found a solution!
In 2026 Microsoft will turn off SharePoint add-ons and workflows. This will put many Nintex customers on the crossroad – whether to move to Nintex Automation Cloud or to Power Platform.
This post is a result of a challenge I faced sometime ago during a project, which goal was creation of a Power App using offline capabilities.
Have you ever faced it? A system, that accepts just international characters while users input local ones, like Polish? Or Spanish? Well, Power Automate is here to help them get replaced!
I was recently trying to use Power Automate to write to an Excel worksheet, when I found out that the file is password protected. I was trying to find any action to let me unlock it, but I failed. After some research I realized this can be done using the power of Office Scripts!
In my previous post I was describing a solution to provision SharePoint lists dynamically and also to set their permissions. However, I want to share as well the solution that will let you to create list items using XML data.
In this blog post I would like to share with you a cool solution I have recently built for my customer, that allows dynamic creation of lists based on existing templates, together with setting all needed metadata and permissions.