If you’ve been ultra efficient and create a calculated Date Field that will display the month and year (e.g. Aug 2015) of a date column so that you can group something like News Articles in this way, you may have already discovered that grouping your list view using this new column displays the group header as blank. When you include the calculated field in your view, you see it has value BUT the won’t display in the group header.
I found a work around for this – simply edit your view and change the style to Basic Table. I also played around with default expansion of the groupings. This should now display your calc field group headings and display any items underneath.
After creating a SharePoint 2013 Wiki library, the quick launch navigation under Updated Pages reports “an error has occurred on the server.” When you click on the Updated Pages link it displays the error: Invalid index. (Exception from HRESULT: 0x80070585).
This error occurs when there is no index column in your Wiki list. To fix it, add a column for indexing:
Library Settings -> Index Columns: Create a new Index on the ‘Modified’ column.
There you have it. The problem should now be solved.
You CAN route a document deposited in the Drop off library, to a document set. You wouldn’t think so considering there is no way of selecting a document set within the browse-library UI, available in the Content Organiser rules page, but there is a trick. Just type the Document set name on the end of your library URL. Don’t copy and paste from the address bar- it won’t work. Make sure, if your document set name is multiple words e.g. Shipping ABC, then use %20 for spaces – /Shipping%20ABC
Ok so now we have that out of the way, I have a complaint about the Drop off library. Even if all metadata is filled out on a “dropped document” the document won’t be routed until it’s properties are edited. That seems completely pointless! I email enabled my drop off library will all metadata fields having defaults. When a document arrived it didn’t route until I edited the properties (which were all already filled out and correct) and clicked submit.
I was seeing this error when trying to check in a document after completing the required metadata in Word (via DIP). I found this post claiming the issue was due to the content type of the document containing a managed metadata field. Although that sounded far fetched, I ended up following the workaround instructions and adding a new managed metadata field directly to my library (Test with one term- test). I then deleted the field, and suddenly I could check my document in! Weird.
I also saw this error when I used the Specify default content feature of Document Sets – automatically creating a number of documents from templates, within a new set. I could not complete the metadata and check those documents in. When I turned off check in/out on the library, I could no longer get to the DIP properties in Word. The only way to set the document metadata was to use the edit form in SharePoint. I never got around this issue. If anyone has an ideas, please let me know.
There are a few circumstances under which you may come across this error :
We’re having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again
Here I will provide a solution for one of those – You are trying to open a SharePoint document library in explorer view while on the SharePoint server.
There is an excellent post here that provides a detailed description of the problem and solution, but to summarise, you need to install the Desktop Experience feature under User Interfaces and Infrastructure on the server.
Recently I set up Managed Navigation – navigation based on a Managed Metadata term set – in my Office 365 developer site. I came across a few problems so I’ll provide steps here that should help you circumnavigate those.
Using Publishing Navigation Settings
- Create new site collection or ensure you are dealing with a site collection that you have provisioned. This will overcome the strange issue reported here: http://community.office365.com/en-us/f/148/t/282769.aspx – “Sorry you don’t have access… (to update Navigation Settings.)”
- The publishing feature should be turned on so you can set global navigation via the Navigation settings, so either use the appropriate site template type or enable the publishing feature in your site collection.
- Under site administration settings, open the Term Store Management Tool and :
- Locate the Navigation term set under the site collection group
- Create new terms for each navigation link
- In the term’s Navigation tab select Simple Link or Header and then add the link address
- Go to Site Settings in site collection and click Navigation
- Choose Managed Navigation: The navigation items will be represented using a Managed Metadata term set and ensure your new term set is selected before saving the settings.
- Now you should see your managed navigation links displayed that the top of the page 🙂
Using Custom JS in master page to Create a Navigation Bar
Follow this blog post to generate reusable nav bar and embed into master page. In this scenario you don’t need the publishing feature and you create your own Navigation term set from scratch. I haven’t tried it yet but it looks pretty cool!
If you attempt to execute a PowerShell script on the SharePoint server and see : “Script cannot loaded. The file is not digitally signed. The script will not be executed on the system” or “… the execution of the script is disabled on the system…”
It means you either need to :
Sign the script OR
Set the PowerShell execution policy to allow you to execute unsigned scripts, e.g.
powershell.exe -executionpolicy bypass -file C:\script.ps1
If you want to make changes to a PowerShell script but you are always prompted to save as a new version, the file may be locked. Right click the script file and select Properties. Ensure the Read-Only checkbox is unchecked. If there is a Unblock button next to the Read Only property, click Unblock.