Advertisements

Speaking at SharePoint Saturday Baltimore on May 20

I’m speaking about using Microsoft Flow and SharePoint Designer Workflows to streamline processes next weekend at SharePoint Saturday Baltimore, May 20, 2017

Advertisements

Solution: Microsoft Flow error “The field ‘…’ is not supported in query. The lookup list is in another web.”

flow1

Perhaps you, like me, built an exciting Microsoft Flow workflow and let it go into the wild without much additional thought. But at some point, you drop a lookup column into the mix and your Flow stops working. It tells you the field is not supported in query, even if that specific field isn’t being utilized in the Flow. I believe this has something to do with REST, but we won’t dwell on the cause – let’s get to the workaround.

The scenario I’ll be using is my cross-site publishing alternative using Microsoft Flow where I’m basically copying data from list items in one site collection to create new list items in a different site collection. This is helpful when someone does some sort of data entry once, and other people are then entering much of the exact same data. This copies all of the overlapping data to a new list item for the second site collection to reduce duplication of work.

It sounds simple but with a lookup column in the destination list we get the error. For this I’ll be using SharePoint Designer and Microsoft Flow (of course) in combination, though you could certainly try it all in Microsoft Flow. I just find parts of the process simpler in SPD. And while your origin data may be different (MailChimp, Twitter, etc.), and your exact scenario may differ, this workaround should still have value in concept.

Creating a “Today” column in SharePoint that always gives today’s date

Update 12/8/17: There’s a better way to do this using Microsoft Flow, if that’s available to you.

update7

You may, at some point, find yourself working with calculations among dates, including “today’s date” which conceptually seems simple but requires a bit of work to function correctly. You may have even created a “today” column that defaults to “current date” or attempted a calculated column only to find that the date will not automatically update each day or that calculated columns cannot show dynamic data like that. Fret no more.

Today columns are essential for use in calculated columns that tell you things like “days until event”, “days without incident” or “years of service” without needing to click any buttons or take any additional steps. Here are some ideas for how you can use the “Today” column in calculations. We’re going to create our solution via SharePoint designer workflow and a new Today column.  …

Automatic iCal (.ics) hyperlinks for SharePoint calendar items using calculated column

ical7

Updated 10/17/17

This project allows users a quick option to save something they see on a SharePoint calendar to their own calendar. Spend 5 minutes on these few instructions and your users will have a convenient way to get involved going forward. Note that in modern calendar experiences, there’s a built-in “add to calendar” option for event items. This post is for classic experience calendars and calendar items/events.

Basically we’re going to add a calculated text column called iCal which will use the list’s GUID (easy to get, don’t worry) and the specific calendar item’s default ID number to generate a clickable .ics (iCal) file link. Let’s get started!

Adjust SharePoint list column widths in classic view

columnexpand

This is a popular request that I’ve recently modified, thanks to the recommendation of a colleague, to be responsive to different device or browser sizes. By default, SharePoint lists respond to their viewer’s size but once customized with a fixed pixel width will lose that feature. This solution utilizes percentages so you can create column widths ideal for any screen.

Remove select/de-select checkmark column, column headers, edit/new options, and border in SharePoint list view web parts

tooltiplinkedtitlesIn a recent post, I discussed hyperlinking URL title text and adding tooltips. I used the above screenshot which also illustrates what we’ll accomplish in this post which is to remove the select/deselect checkmark column, column headers, toolbar edit/new options and chrome border. This leaves us with a simple title and list. Pick and choose what you’d like to remove for your specific needs, and let me know if you run into any issues.

Creating hyperlinked titles with tooltips in SharePoint link lists using SharePoint Designer workflow

tooltiplinkedtitlesLet’s put those link lists to good use. I wanted one master or parent link list with a number of views. I would then use those views in different list view web parts across my site, removing the toolbar (view/edit/add options), column headers, chrome border and select/deselect checkmark column so that essentially I had a section of my page with a header/chrome title like “HR Forms” (removing default link to “parent” list) and then just a list of hyperlinked form titles with tooltips providing more info on each form as seen above. This post will cover how to get the hyperlinked title text with tooltip. Another post coming soon will cover the “clean-up” of the list view web part so that you’re left with a title and list items alone.…

Solution: Microsoft Flow error “The query to field ‘/fieldname/LinkTitleNoMenu’ is not valid”

I recently ran into the following error message in Microsoft Flow that was triggered by a SharePoint – modified list item flow: “The query to field ‘/fieldname/LinkTitleNoMenu’ is not valid.” You’ll see this message in some cases when lookup columns are being utilized on the lists you’re referencing in Microsoft Flow.

This error was caused, at least for me, as a result of setting my “destination” list’s lookup column setting to display as Title (linked to item) instead of just Title. The following details the steps involved in fixing it.

Including or excluding multiple property filters in SharePoint search results web part query

In one of my projects, we built a directory largely based on this article with content created by Stacy Deere-Strole of Focal Point Solutions. Something we ran into was wanting to include multiple departments in our base search query (not refiners, as that only narrows our results instead of expanding them). We also wished to eliminate multiple results in the JobTitle property within the query text. While this is a simple solution, hopefully it will save you some trial and error in writing your search language.