Microsoft PowerApps: Identify Soon-to-Be-Deprecated Office 365 Connectors in Your Environments Using PowerShell

For the Time-Crunched:Jump Ahead to the Script and Usage Instructions What's Happening? Back in August 2019, Microsoft announced the pending deprecation of several Actions and Formulas utilizing the Office 365 Outlook connector
If any of your Flows or PowerApps use any of the to-be-deprecated Formulas (eg: 'Send email', 'Get calendar', etc.) you will want to update them prior to their impending departure - or risk being left with broken PowerApp.
In a previous article, I covered how to identify any Microsoft Flows using the affected Actions and Triggers using PowerShell - if you haven't already, I highly recommend you give that a read to learn a bit of how PowerShell works and how we make it work for us in this scenario.

Once you've taken a look at that, come back here and I'll give you a run-through of how this new script works - since most of the same concepts covered in the other article were applied here.

Did you read it? Great! Let's continue.…

Microsoft Flow: Identify Soon-to-Be-Deprecated Office 365 Connectors in Your Environments Using Powershell

For the Time-Crunched:Jump Ahead to the Script and Usage Instructions Did you feel that? It was the collective shudder throughout the Power Platform community as they came to grips with this week's announcement from Microsoft regarding the deprecation of certain actions in the Office 365 Outlook connector.
Like a large tremor out in the deep ocean, the impact of this notice may not strike you immediately. But the inevitable wave has been put in motion and will reach the shore soon enough.
Thankfully, Microsoft does provide us the tools to plan for and mitigate the effects of this change - you may just have to dig a bit to find them - and this post has been created to help guide you through doing just that.
Together, we'll weather the storm and you may even learn some PowerShell along the way! What's Happening? I'll leave it to the previously mentioned announcement for the nitty-gritty details, but the watered down version is if any of your Flows or PowerApps use any o…

PowerApps: Apply Multiple Filters to a Gallery

Learn how to filter PowerApps Galleries using multiple filter selections without running into delegation warnings.

Introduction: When working with Gallery components in PowerApps, often a common ask is to be able to filter the items displayed inside of that gallery based on a filter selection field - such as a Dropdown or Text Input component.
While filtering off of a single dropdown is simple enough, when you wish to filter based on multiple filter selection fields things can begin to get messy quite quickly.
One of the issues you can run into, depending on your Items formula, is delegation warnings - also hereby known as the 'Blue Squiggles of Impending Doom' ('BSID').
I'd direct you to Microsoft's very helpful Understand Delegation in a Canvas App article for more detailed guidance on the subject, but for convenience I'll highlight the following line from that article as it most succinctly sums up what delegation helps you accomplish:
"The key to bu…

SharePoint Online: Give Your Modern News Web Part Title The Boot!

This one's a really simple problem that was brought to me recently with just as easy a fix (and may or may not just be an excuse to show off some cute penguins...).

Scenario: You've added a News Web Part to your modern SharePoint page and have decided that you don't want a title to display on the web part.

That's easy enough, right? Simply remove the text from the title and click publish!

(Let's use our imagination to visualize me clicking the backspace key...)

... hmm. It looks like the default 'News' title sticks around. Go ahead and click 'Publish' to verify if you'd like.

Now, you might think that you can try the old 'hit space to trick SharePoint to thinking there's something in there' trick - but that won't work (believe me, I tried...).

The more technically-savvy among you might even try to use 'Alt-0160' to create a non-breaking space instead. No dice.

So then I guess that's that, right? Nope!
Solution: Throu…

Microsoft Flow + Cognito Forms: Error uploading Form attachments to SharePoint Online

This post is decidedly more product-specific, but hopefully it will help someone out there facing the same issue that is looking for an easy fix.
Cognito Forms is an online form building service that, while I personally haven't tried, has been in use by some departments at this organization. They also provide Microsoft Flow integration to their forms, which is ultimately how this post came to be.
The Problem: The Flow is simple enough, it takes a submitted Cognito Form, does a handful of things, and ultimately populates a SharePoint List with the form information and attaches the form attachments to the list entry. This works exactly as expected for most forms submitted - assuming the files don't exceed a certain combination of size and quantity (which I didn't have time to nail down specifically during troubleshooting).

Under most circumstances, the following Flow action would work just fine:

The Cognito Forms-provided Name and Content attributes work as expected and all is…

SharePoint Online: Expand Your Horizons! (Or At Least Your Document Viewer Web Parts)

Here's a quick tip for you: When you use SharePoint Online's modern 'Document Viewer' web-part, you'll notice that regardless of window size the height of the viewer is unusually 'short'.

You won't even get a full view of a single page in most cases!

We can easily remedy this with only the tiniest bit of effort!

Microsoft Flow: Create a Flow Log in SharePoint to Display Flow Run Outcomes to Your Users

Scenario: As you're probably aware, Microsoft Flow already provides a list of Flows and their outcomes when you visit your 'My Flows' page.

However, if your Flow is triggered regularly but only really does something occasionally not every run displayed here is relevant. In addition, since each run is labeled only with the outcome, how long ago it was run, and duration, finding a specific Flow run can sometimes feel like a shot in the dark.

In my case, the Flow in question was tied to a very active SharePoint document library and triggered 'When an item is created or modified'.

More specifically, I was looking to move new and updated Excel Macro-enabled workbooks into a fileshare which acted as a pickup location for a separately developed business application. Here's what my Flow looks like:

In essence, the Flow does a conditional check to see if the file is an Excel file. If it is, it copies it. If not, it does nothing. I only care about the Flows that involve…