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.

One way to improve user experience, and increase adoption to a certain level, is to add “little” things that would help users. In this blog post, we’re going to create a popup that will warn users when they want to navigate to another screen, BUT they’ve already entered data. Let’s offer them the choice to “Leave” or “Stay”. Scenario I have an app for rewarding employees once they’re nominated by their colleagues.

Have you ever had the scenario where, you had values in SharePoint (or Dataverse) with a character, or the end of the value is not relevant for your app, and it should not be displayed? I did. In this first PowerPlatform blog post, we’ll get rid of the end of the value that’s after a specific character. And we’ll also include getting rid of the character since it won’t be relevant nor nice to see anymore!

A new feature to use very carefully! OK, you’ve been warned now 😉 In this blog post, we’ll have a look at how we can limit access to OneDrive For Business, and the impact when enabling this feature. Scenario Let me lay out the environment first, so we understand the impact later. In this example, we’re going to have the following: 2x users (Adele & Debra) 1x Security Group called “SG-Consultants” Both users have OneDrive For Business provisioned, with sample content (private or shared with others) 1 of those users (Adele) will be a member of the Security Group we’ll be using, but not the other user (Debra)

Finally! We can now see how many Private Channels a Microsoft Teams Team has, directly from the SharePoint Admin Center! As a reminder, when you create a Private Channel, it creates another SharePoint site with different permissions. Meaning a Team could have many other SharePoint sites that we couldn’t see, and therefore, do “things” that would have been regrettable! In this short and sweet post, we’ll see where to find the information about Private Channels in SharePoint Online.