So to access a hidden SharePoint List, navigate to:
The solution was to set the revert to self option of the BCS service to true. To do that, run the following in the Management Shell.
I received this error when I was trying to restore a SharePoint 2013 SiteCollection using the Restore-SPSite command. The backup, a .bak file, was created using the Backup-SPSite command in the management shell. Following is the screenshot of the error message:
After little bit of digging, I figured out that the database backup doesn’t seem to be compatible with my latest web application. The issue in fact, also occurred when I tried to restore the db within the same web application whose one of the SiteCollection was backed in the file!
Read More »
This is a two series blog in which I will try to cover lots of SharePoint TermSet Metadata operations. The idea is to achieve the following:
Export Terms to CSV
- Existing Terms along with their child Terms,
- Current Guid,
- Available for Tagging option, &
- Deprecate state.
Import Terms from CSV
- Import Terms which will create Terms only when they don’t already exist. The search will be done using the Term Name.
- Can create the Term with the given Guid. This is optional. If you don’t want to use this option, then keep this column blank and the Term will be created using a brand new Guid.
- Deprecate/Un-Deprecate an existing or a new Term. If you have to change this option on a number of pre-existing TermSets then simply update the exported CSV accordingly and then run the import script.
- Modify the availability for Tagging option. If you have to change this option on a number of pre-existing TermSets then simply update the given CSV accordingly and then run the import script.
- Most importantly, it also applies custom sorting. So the Terms and their child terms will exactly appear in the same order as has been mentioned in the processing CSV.
In this post, I’ll only be showing the export operation. The import operation has been defined here, https://realmpksharepoint.wordpress.com/2015/09/23/import-sharepoint-metadata-from-csv-along-with-their-guids-deprecate-state-and-custom-ordering/. Please note that since the generated output will be in CSV format, we’re converting any comma (,) that might be included in the Term name to “,” otherwise the format will get distorted.
The script expects two parameters that needs to be set before executing it. They are:
- $termGrpNm: The name of the TermGroup whose all TermSets will be exported to CSV files respectively.
- $svLoc: File System location where all the CSVs will be dumped.
Here’s the script preview. Download link for the same has been provided in the later segment.
I had this requirement where there was a need to rename some of the existing Managed MetaData Terms, [Old Parent, Old1, Old2, & Old3] to a single new Term [New Term].
Usually, renaming a single term is no big deal. However, this was a Many => One relationship and you cannot have 2 or more Terms with identical names at the same level of hierarchy. So renaming was not an option here. We had to make sure that for all the existing ListItems, the GUIDs of every old term should get replaced with the New Term GUID. Following is the PowerShell script I came up with to do this job.
Read More »