Workaround to filter on taxonomy columns using OData filters instead of CAML using REST in SharePoint

Wow, that was a long post title indeed. The thing is, you cannot use OData filters on taxonomy columns in SharePoint, hence you see posts on the interwebs about using CAML instead to filter on taxonomy fields by using this construct:

/_api/web/Lists/GetByTitle('<List>')/GetItems(query=@v1)?@v1=<caml>

And this works just perfect. But if you try to add a field expansion at the same time on a lookup field, then it blows up. So you can either do an $expand=MyLookupFiled on the /Items endpoint or filter using CAML on a taxonomy field using the /GetItems endpoint.

What if I told you that you can accomplish both using a workaround!! You may either contact me and pay up, or continue reading for free :)

Diagram on adding a new content source in SharePoint

Looking for a Visio file I discovered this one which I forgot to publish some time ago. So here’s a small diagram you can use when adding a new content source to cover the most important aspects you need to think about when adding it.

There are more complicated scenarios of course, and feel free to reach out if you have any questions.

SharePoint Search: New content source diagram—Mikael SvensonDocs.com

Appending query terms to a search URL

I have written about appending query terms before without having them in the search box, and I’ve missed out at the best approach for this until now. Sometimes it takes years for the obvious solution to step forward.

In SharePoint 2010 you could add a= to a query and the terms on the a parameter would be included in the query as a hidden constraint. So how best to do something similar in SharePoint 2013/2016 or SharePoint Online? You modify the query template!!

A simple query template like {searchboxquery} {?{\QueryString.a}} will take the value of the a parameter and append it to the query. Problem solved, and you can keep existing code if you migrated even.

Craft a query like: https://contoso.sharepoint.com/search?k=foo&a=title:bar and the query will filter to items where title includes the term bar, but not show it in the search box.

Introducing SharePoint Framework!

Today Microsoft announced SharePoint Framework, the framework which will take SharePoint web development into 2016. At last, client side development has become a first class citizen of SharePoint development, and developers can use the open source framework of their choice like React or AngularJS to develop web parts, pages and views in SharePoint like there was no tomorrow!
Want to read more? Take a peek at my article on Puzzlepart.com and see a demo of what I’ve built using this new framework being part of an early test group. Or head over to the official Microsoft blog post.

Hello, it is you we are looking for!

Are you an opinionated gutsy person in the Oslo, Norway area with at least some work experience who want to work with Office 365 and SharePoint? Maybe you should get in touch with Puzzlepart, ‘cause we’re hiring!

We’re a mix of nutty, crazy and passionate people, so if you love having fun at work while also delivering real business value feel free get in touch.

You’ll find my contact information in the right column of this blog :)