SharePoint search can crawl managed metadata fields, and it stores the values inside a Text search property. But what are the values stored there? What format are they in? Do they contain the path to the term/s, etc?
Well, the project I’m working on needed me to retrieve some managed metadata fields from the REST search API. Continue reading “Get the text out of a Managed Metadata Search Property”
Edit: It seems Chris O’Brien has been thinking about the same problem, and has a good post about it.
Microsoft claim that Office 365 has PowerShell support. I had assumed that this meant that most, or at least many, of the PowerShell commands I can use in a normal farm would also be available in Office 365.
I was wildly, spectacularly wrong. Continue reading “Powershell in Office 365 … and why you need CSOM”
If you’re a SharePoint developer like me, you probably find the Query Throttle in SharePoint an absolute pain. This is a feature where, under an unnecessarily complicated set of conditions, if you try to ask for too many list items in one query, SharePoint refuses.
Now, while I understand why such a limit is necessary – albeit I’d rather it was simpler – it is something of a problem. For example, multi-choice columns cannot be indexed. If you want to query such a column, and there are more than 5000 items in the list, we’ll, you’re outta luck.
That situation is surprisingly common in Document Management systems. Continue reading “"Minor" Search limitations in Office 365”
So I’ve discovered an interesting problem with Content Approval, which is a special issue for Office 365. I have a document library with more than 5000 documents in it. Content Approval is turned on, and the customer would like a view of ‘Unapproved Documents’.
For a Document Management System, 5000 documents in one repository is small beer, so this is a bit of a problem. “Okay”, I thought, “this must be a choice column, so I’ll just add an index to the column”. Continue reading “Content Approval and Large Lists”
Right, so I’m trying to develop some Remote Event Receivers. I’ve been using our company’s tenant. Lets call it https://mytenant.sharepoint.com. That tenant was a SP2010 one, which has been upgraded.
I am trying to test using https://mytenant.sharepoint.com/sites/AWBTest. It’s a SP2013 site collection. Unfortunately, https://mytenant.sharepoint.com is still running in 2010 mode. Continue reading “Fail: Visual Studio 'Verify' for Office 365 in 2010 compatibility mode”
So I’ve been working with Office 365, and deploying site collections and their contents can be … fun. I’ve found that the best approach seems to be to use the Client-side Object Model (CSOM) – the C# API – to deploy and configure my content.
On thing I didn’t think would be easy was adding Custom Actions – but this turned out to be pretty easy, to be honest. Continue reading “Adding Custom Actions to SharePoint using CSOM”
So, I’d an interesting problem. I have a SharePoint 2013 list that uses a Managed Metadata (or ‘Taxonomy’) field. I need to, through the JavaScript Client Object Model, get all items that have a particular value or a child of that value on the taxonomy tree. As an example, here’s my taxonomy:
Sounds like it should be simple to query this, right? Well, not so much. Continue reading “Using JSOM to query SharePoint 2013 lists with Taxonomy Fields”
So, I had an issue that I’ve a customer who wanted to have some items look up against a large list. (In fact, it was a large document library). This large list had more than 5000 items. This is a little unfortunate, due to a painful and annoying quirk in SharePoint’s design. Continue reading “Looking up against Large Lists in Office 365”
We have a customer who are planning on putting a lot of documents into a Library in SharePoint. These documents will be uploaded, by hand, and are nearly always the ‘final’ version of the document. Given the number of documents in the library, the plan is to find them again using their metadata, which seems like a good idea.
However, there’s a catch – what if someone has uploaded a document with that filename already? Continue reading “O365: Uncheck the Overwrite checkbox”
I’m upgrading a Visual Studio 2010 solution to a Visual Studio 2012 one. It’s part of a migration of a solution from SharePoint 2010 to 2013 (and there are good details about this here). Annoyingly, though, every time I open the project it says that it has ben upgraded and shows an Upgrade Report. Nothing appears to be modified, but still, it’s shown.
Google didn’t show a lot of help on this, but in the end I decided to simply open the .csproj file and look for some sort of flag about being upgraded. I found the element:
<FileUpgradeFlags>0</FileUpgradeFlags>
so I tried deleting the ‘0’ and reloading the project – and it didn’t show an Upgrade Report. Hurrah. Not sure why I needed to so this, though.
Andy Burns' Blog 