Note: I previously shared how to do this in SharePoint Designer. The following method utilizing Flow is better, and does not use loops/pauses.
It’s well-known that SharePoint calculated columns don’t permit [Today] to be used as a formula for a calculated date column. And the “default to today’s date” setting only works upon creation, and doesn’t update daily. But we can create a standard date column and have Microsoft Flow automatically update it daily for us, therefore allowing us to effortlessly perform calculations against today’s date such as:
- Age =(TodayDate-Birthday)/365
- Years of Service =(TodayDate-StartDate)/365
- Days Past Due =(TodayDate-DueDate)
- Weeks until summer break =(SummerStart-TodayDate)/7
Here’s how to create your own, always accurate/updated, today column (see bottom of post for video):
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:
|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
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:
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)
We’ve been waiting a lifetime (dramatic?) for this feature. And now it’s here! Sort of.
Currently, with a new “Preview” action release in Microsoft Flow, we’re able to convert documents to PDF in OneDrive for Business via workflow. While this isn’t ready for SharePoint yet, we can make it look that way for our end users. Basically:
- When a file is created or modified in SP
- Create document in OneDrive for Business
- Convert document
- Create document in SP
It’s roundabout but we get exactly the result often requested: convert SharePoint docs to PDF automatically. Here’s how to set this up. A video walkthrough is available at the bottom of this post.
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 ' and ampersands (&) to & As you can see here, most other punctuation evaluates perfectly well:
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:
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:
I’m speaking about using Microsoft Flow and SharePoint Designer Workflows to streamline processes this weekend at SharePoint Saturday Kansas City, Sep 16, 2017
We’ve all been there. One location on a shared calendar will be referred to by multiple people as 20 different things. Johnson Building Room 214 can be entered as “214,” “Johnson 214,” or “J214” to name a few. Canceled events stay on the calendar, sucking up real estate and waiting for someone to delete it manually. Items copied from another calendar make you pay for the convenience of a simple copy and paste by adding the “Copy: ” prefix to the item.
But with a single workflow, we can fix all of these and make our SharePoint calendars look more professional and polished without making more work for end users. This post will cover how we can use workflow to standardize naming of locations with workflow, delete events once they’ve been canceled and get rid of Outlook’s “Copy: ” prefix. You will need SharePoint Designer and appropriate permissions to create workflows to complete the following steps:
SharePoint Designer 2013 workflows verify workflow email recipients are part of your organization, while SPD 2010 workflows do not.