Today’s post is about something many app makers are trying to prevent users from doing when not necessary. And that is, adding special characters in text inputs, especially when a Power Automate flow is involved in the background! 😁 Personally, I’d rather stop the issue at the source (PowerApps) than messing around with the flow(s). So, if you know that special characters are not needed, this post is for you!

In this blog post, we’re going to add an admin account into a user’s OneDrive for Business via the interface (UI) in 2 different ways. There might be situations where you need to have access to the user’s personal area (aka OneDrive for Business). For example, you might need to create folders pre-migration, or quickly “audit” something. The below 2 methods require you to have an admin account (i.e.: SharePoint admin, or Global Admin) as we’re going to use the Microsoft 365 Admin Center & the SharePoint Admin center.

Subflows in Power Automate Desktop are a way to isolate some actions out of the Main flow. This has many benefits: Main flow is cleaner Repetitive actions can have their own flow Can be used as “branching” (more on that later) Where can I create subflows? When you open the Power Automate Desktop designer, you’re landing straight into the Main flow tab. If you look on the left of that tab, you’ll see “Subflows” as a dropdown menu.

Did you know there are multiple ways to update or modify your user’s OneDrive for Business? In this blog post, we’re going to go through 3 methods! Hopefully that will give you sense of where to go depending on your role/permissions within Microsoft 365. Microsoft 365 Admin Center Probably the most obvious way is the Microsoft 365 Admin Center. If you navigate to Users > Active users, you can select a particular user by clicking on their name, and then a panel/blade opens on the right handside.

In today’s blog post, we’ll talk about how we can update a person field in SharePoint from another list, using Power Automate. This might sound a bit “cloudy” right now (pun intended 😉), but will be clearer when we get onto it. And I found this solution/workaround very useful with some of my customers. What’s the scenario? Let’s say you have a SharePoint list with information about people. Basic information as in their display name, email address, role, etc… and those users are in that SharePoint list for a reason: They will somehow be involved in your PowerApps application.

Wouldn’t it be nice and kinda logical that, when someone creates a request via an app (i.e.: expenses, training), if the creator is also the first approver, we skip this particular approver? After all, if I create a request it’s because I “want” something? So I’m pretty sure I’ll approve it 😏 In this blog post, that’s why we’re going to do using SharePoint as a backend for the requests, and Power Automate for automating the approval process.

In this post, we’ll make your app flexible when it comes to enter data. More specifically how we can switch between a combobox and text input. I’ve build an app for a customer where a user needed to choose between defined values (combobox) and his/her own value (text input). Of course, we’re also going to see how to send this data back to the data source (SharePoint in my case) depending on the controls and values chosen!

In this blog post, I wanted to talk about the different types of tabs you can add in Microsoft Teams when using PnP PowerShell. More specifically about the -Type parameter which offers multiple values, but also because we have a dynamic parameter for the Add-PnPTeamsTab cmdlet. The easy ones… Most of them are pretty self explanatory. For instance, -Type PowerPoint or -Type WebSite. We also provide an example in the Add-PnPTeamsTab documentation for the PDF type.