Generate and send reports, files or lists regularly with Microsoft Flow’s “recurrence” trigger

Capture.PNG

Automatically create and send reports, files and lists on a regular schedule using Microsoft Flow’s recurrence trigger. Whether hourly, daily, weekly or monthly you can deliver the most current and relevant data from SharePoint or OneDrive to interested parties via email without lifting a finger. Combine this with calculated columns in SharePoint and conditions for some awesome possibilities:

Alerts Calendar Relevance Routine
Report costs or expenditures above a certain amount Current month’s birthdays and/or workiversaries to your secretary Send expenses per department or individual to that department or individual Budget and salary or payroll figures weekly
Notify when an open ticket is idle for a week or incomplete Upcoming events per location Share evaluation status with supervisors for just their employees Recently closed deals and contracts
Survey responses or reviews under 3 stars Upcoming deadlines per department Client info and updates to proper salespeople based on location or product Distribute new hires’ contact/location info to the organization in weekly batches

Continue reading “Generate and send reports, files or lists regularly with Microsoft Flow’s “recurrence” trigger”

How to change Microsoft Flow’s default limit of 100 items for “Get Items” and “Get Rows” actions

100itemlimit

The first time I created a flow for a list with over 100 items, I noticed an “Apply to Each” block stopping at 100 items. It’s a simple fix:

Continue reading “How to change Microsoft Flow’s default limit of 100 items for “Get Items” and “Get Rows” actions”

How to make a Microsoft Flow mobile button to be emailed Microsoft Forms or SharePoint data as Excel link or attachment

screenshot_20171109-143752.png
Microsoft Flow mobile buttons are magical. One touch on your mobile device, and gears start turning to retrieve and deliver the data you need when and how you need it. Recently, I set out to deliver all Microsoft Forms responses to a recipient on-demand as an excel file using a Microsoft Flow mobile button they could press whenever they wanted the results. I also created a button someone could use to be sent all the birthdays coming up in the next week for our organization whenever they need it. You can adjust the following steps to fit your situation and tools, but the following outlines two ideas:

  • Sending someone all responses to a Microsoft Forms survey whenever they press the button (Take a snapshot in time of responses, or pull up-to-the-minute feedback into your meeting)
  • Sending someone SharePoint list items in an excel sheet that match a certain criteria (Projects ending in the next two weeks)

Continue reading “How to make a Microsoft Flow mobile button to be emailed Microsoft Forms or SharePoint data as Excel link or attachment”

Convert Time Zones in Power BI using DAX

timezonecorrection.png

Even if your SharePoint site’s regional settings are correct (or whichever data source you’re pulling from), Power BI could convert it to the wrong time zone upon import. It’s a quick fix, luckily. Instead of using your “modified,” “created” or other date field in your report, we’ll create a new calculated column in Power BI to use with an accurate time zone.

Continue reading “Convert Time Zones in Power BI using DAX”

Convert SharePoint documents to PDF using Microsoft Flow

convert.PNG

Edited Dec 10, 2018 to include “for a selected item” function in modern sites.

Can you convert SharePoint documents to PDF without leaving SharePoint? Heck, yeah!

Basically we’ll create this flow:

  1. “When a file is created or modified” in SP -OR- “For a selected item”
  2. Create document in OneDrive for Business -OR- OneDrive
  3. Convert document (OneDrive action in Flow)
  4. Create document in SP

It’s a bit of a hack but we get exactly the result often requested: convert SharePoint docs to PDF automatically. Here’s how to set this up. A video walkthrough using the “created/modified” trigger is available at the bottom of this post.

Continue reading “Convert SharePoint documents to PDF using Microsoft Flow”

Dealing with &#39 and &amp in SharePoint Designer document library workflows

If you’re using a document Name field in a workflow but it’s not working as expected, it could be because there are apostrophes () or ampersands (&) in document names. In this case, SharePoint evaluates apostrophes () to &#39semicolon and ampersands (&) to &ampsemicolon As you can see here, most other punctuation evaluates perfectly well:

cats

Note: This problem only occurs when using apostrophes and ampersands in document names, in document libraries. And we can fix the issue without needing to rename the files.

Document names cannot contain these punctuation marks: \ / . : * # “

Regular lists and document library fields aside from the Name field shouldn’t experience this issue. But if you’re using & or in your file names, and calling those file names in workflow, here’s how we can make it work:

Continue reading “Dealing with &#39 and &amp in SharePoint Designer document library workflows”

OneDrive and SharePoint sync issue: “You now have two copies of a file; we couldn’t merge the changes in [filename]” appended with computer name

couldntmergechanges

If you’ve seen a similar notification, I empathize with your pain. I don’t know that there is one solution to this problem, either, so I’m going to share a number of them we’ve used and hope that one (or all) of them will help you.

Basically a file is added through file explorer (a cloud library in OneDrive or SharePoint being synced locally to your computer) but then after a moment a notification appears which says “You now have two copies of a file; we couldn’t merge the changes in [filename]” and then the filename is appended with your computer name again and again until eventually the filename is too long and is harder to delete. Let’s not get to that point.

Continue reading “OneDrive and SharePoint sync issue: “You now have two copies of a file; we couldn’t merge the changes in [filename]” appended with computer name”

Solution: Using a Yes/No checkbox in a Microsoft Flow condition statement

2017-09-17_13-59-37

It’s not uncommon to want to use yes/no checkboxes when building Microsoft Flow conditions. [Field] is equal to “Yes” or [Field] is equal to true won’t work because it reads the Yes or true as a string rather than a value. So when the flow runs, even if the checkbox is checked (true), the run history says the expression result was false.

Fortunately it’s a simple two-step fix. Follow these steps to be able to use yes/no checkboxes as conditions in your flows:

Continue reading “Solution: Using a Yes/No checkbox in a Microsoft Flow condition statement”

Speaking at SharePoint Saturday Kansas City on September 16

I hope to see some of you this Saturday at SPS Kansas City, where I’ll be sharing an overview and demos on using workflows to improve business processes. Here’s what you can expect from me:

spskc2.pngLet Microsoft Flow and SharePoint Designer Workflows Do the Work

Your team members would appreciate getting some time back. Give it to them in ten minute increments here, thirty minutes there by using Microsoft Flow and SharePoint Designer to build them thoughtful workflows that range from simple one-steppers to more complex and conditional multi-stagers, even across site collections. We’ll cover specific HR and Accounting scenarios in this session based on real-case experience at KU Libraries, including automation of some onboarding and off-boarding processes, simple automated management of otherwise complex item-level permissions, travel plan submission and approval, receipt submission and reimbursement tracking and more all through utilizing workflows to save you and your colleagues time.