1. Ensure Document ID Service Feature is activated on the Target sites

• Should not be left empty

• Must be 4 to 12 character long

• Click on ok. If we re navigate to the same page it will comes up with the following message and it will stay till the process completed

• It will take some time and once it is completed the document ID will be regenerated with appropriate target url and the Document ID will contain the Phrase provided in the Begin IDs with the following characters

Hence if we want to change or modify any permission level we will required to do so from parent site. This can be hacked using a very simple two line of powershell script.

$web = Get-SPWeb “<Sub site url on which the inheritance need to be broken>"

$web.RoleDefinitions.BreakInheritance($true,$true)

This two line of code need to be executed from the sharepoint WFE server. Once this is done user can see the below links on browser and free to do any changes on permission level for that sub site

In order to do so we need to do the following

To gather the site level changes 

Initialize the below variables as required.

Site rootSite;

ClientContext context;

DateTime dateTime;

string format = "1;1;{0};{1};-1";

ChangeQuery cq = new ChangeQuery(true, true);

cq.ChangeTokenStart = new ChangeToken()

 {
 StringValue = string.Format(format, rootSite.Id, dateTime.Ticks)
 };

 ChangeCollection changeCol = rootSite.GetChanges(cq);

context.Load(changeCol);
context.ExecuteQuery();

 while (changeCol.Count > 0)
 {

//DO THE PROCESSING TO GATHER ALL THE REQUIRED INFO LIKE SITE NAME, ID, CHANGW TYPE etc.

 }

At we level the process is same instead of Site instance we need to consider the instance of a specific WEB.

Different type of changes that can be gathered using the above approach are listed below, all are Out of the box .NET classes available under the Microsoft.SharePoint.Client namsespace

1.ChangeSite

2.ChangeItem

3.ChangeField

4.ChangeList

5.ChangeFolder

6.ChangeView

7.ChangeWeb

8.ChangeContentType

To overcome this issue in one of our migration project we used CSOM to migrate the documents with versions.

Using the following code piece we can migrate the documents with their version from one platform to the other one.

1. Prepare the source and target client context here I am assuming target is sharepoint online

 ServicePointManager.ServerCertificateValidationCallback += customXertificateValidation;
 ClientContext sourceContext = new ClientContext(sourceSiteUrl);
 sourceContext.Credentials = new NetworkCredential(sourceUserName, sourcePassWord, sourceDomain);

 ClientContext targetContext = new ClientContext(targetSiteUrl);
 var passWord = new SecureString();
 foreach (char c in targetPassWord.ToCharArray()) passWord.AppendChar(c);
 targetContext.Credentials = new SharePointOnlineCredentials(targetUserName, passWord);

2. Get the source folder

 Folder sourceFolder = sourceContext.Web.GetFolderByServerRelativeUrl(sourceFolderUrl); 
 sourceContext.Load(sourceFolder, fldr => fldr.Name);
 sourceContext.Load(sourceFolder.Files, files => files.Include(
 file => file.ListItemAllFields
 ));

 try
 {
 sourceContext.ExecuteQuery();
 }
 catch (Exception e)
 {
              
 }

3. Get the target folder

 Folder targetSiteFolder = targetContext.Web.GetFolderByServerRelativeUrl(targetFolderUrl);
 targetContext.Load(targetSiteFolder.Files, files => files.Include(
 file => file.ListItemAllFields
 ));
 targetContext.Load(targetSiteFolder);

 try
 {
 targetContext.ExecuteQuery();
 }
 catch (Exception ex)
 {
                
 }

4. Do the migration operation

 int fileCount = sourceFolder.Files.Count();

for (int i = 0; i < fileCount; i++)
 {
 Microsoft.SharePoint.Client.File sourceFile = sourceFolder.Files[i];

FileVersionCollection sourceFileVersions = sFile.Versions; sContext.Load(sourceFileVersions, fileVersions => fileVersions.Include( version => version.Url, version => version.VersionLabel, version => version.CheckInComment )); try { sContext.ExecuteQuery(); } catch (Exception e) { //handle exception   

 }

foreach (FileVersion fileVer in sourceFileVersions)

{ UploadFiles(sContext.Url + "/" + fileVer.Url, targetFolder, sourceItem["FileLeafRef"].ToString());

}

}

5.

private static void UploadFiles(string sourceFileUrl, Folder targetFolder, string fileName)

 {

 FileCreationInformation targetFileVersionCreationInfo = new FileCreationInformation(); targetFileVersionCreationInfo.Overwrite = true; try { WebRequest request = HttpWebRequest.Create(sourceFileUrl); request.Credentials = sContext.Credentials; using (WebResponse response = request.GetResponse()) { using (Stream stream = response.GetResponseStream()) { byte[] verBuffer = new byte[32768]; using (MemoryStream versionMS = new MemoryStream()) { int read; while ((read = stream.Read(verBuffer, 0, verBuffer.Length)) > 0) { versionMS.Write(verBuffer, 0, read); } versionMS.Seek(0, SeekOrigin.Begin); targetFileVersionCreationInfo.ContentStream = versionMS; tContext.RequestTimeout = System.Threading.Timeout.Infinite; targetFileVersionCreationInfo.Url = targetFolder.ServerRelativeUrl + "/" + fileName; Microsoft.SharePoint.Client.File targetVersionFile = targetFolder.Files.Add(targetFileVersionCreationInfo); try { tContext.ExecuteQuery(); } catch (Exception ex) { //handle exception   

 } } } } } catch (Exception ex) { //handle exception   

 }

 }

The above piece of code is able to migrate the document with version but it has few issues 

Issue 1. The created date,modified date,credated by and modified by field will be changed to keep these field intact we need to do the following

 List list = targetContext.Web.Lists.GetByTitle(fldr.Name);
 ListItem item = file.ListItemAllFields;
 targetContext.Load(list, listObject => listObject.EnableVersioning, listObject => listObject.EnableMinorVersions);
 targetContext.Load(item, itemObject => itemObject.File);
 targetContext.ExecuteQuery(); 
 [PLACEHOLDER 1] 
 targetContext.ExecuteQuery();
 FieldUserValue targetCreatedUser = new FieldUserValue();
 targetCreatedUser.LookupId = createdUser.Id;
 FieldUserValue targetModifiedUser = new FieldUserValue();
 targetModifiedUser.LookupId = modifieddUser.Id; 
 item["Editor"] = targetModifiedUser;
 item["Author"] = targetCreatedUser;
 item["Created"] = created;
 item["Modified"] = modified;


 item.Update(); 
 [PLACEHOLDER 2] 

 targetContext.ExecuteQuery();

Issue 2: In attempt to keep the created and modified information intact the code internally create additional version as the library is enabled with version changes.

To resolvethat we need to put the following code in PLACEHOLDER1 and PLACEHOLDER 2 subsequently

PLACEHOLDER1

 var isVersionEnable = list.EnableVersioning;
 list.EnableVersioning = false; 

 list.Update(); 

PLACEHOLDER 2 

 list.EnableVersioning = true; 
 list.Update(); 

Issue 3: With the above fixes we are done with migrating documents with versions for the libraries which are version enabled and Forcecheckout checkin option set as false.

 If the library is configured for Forcechecckout then with the above piece of code execution we will be end up with documents with latest version all the previous version info will not be available. To overcome this issue we need to do a small hack before staring actual migration code.

We need to set the forcecheckout option for the target library as false.

  targetList.ForceCheckout = false;

and at the end of migrating all the doc just set it back with actual settings.

In one of article I have explained how to implement the commonly used Query string webpart using powershell scripting.

In this article I will consolidate the details which deals with a User profile filter. It is almost same as of the other OOTB filter other than the highlighted parts.

Following piece of code is ready to use for the same purpose

# SPWeb context 
$web = Get-SPWeb <site url>

$PubWeb = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web) 

#Get the webpart manager

$oWebPartManager = $web.GetLimitedWebPartManager(<page url>, [System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared);

#Get the list

$list = $web.Lists[<List Name>];

#Instantiate listview webpart and added to the page

$listVWP = New-Object Microsoft.SharePoint.WebPartPages.XsltListViewWebPart;
$listVWP.Title =<Listview webpart Title.;
$listVWP.ChromeType = [System.Web.UI.WebControls.WebParts.PartChromeType]::None; 
$listVWP.Visible = $true;
$listVWP.EnableViewState = $true;

$listVWP.ListName = <List Name>;

$listVWP.ViewGuid = <View Guid>
$listVWP.WebId = $list.ParentWeb.ID;
$listVWP.ListId = [System.Guid]$list.ID;

 $oWebPartManager.AddWebPart($listVWP, "Main", 0);

$oWebPartManager.SaveChanges($listVWP);

  #Instantiate and add the Query webpart and set the connection

$queryPart = New-ObjectMicrosoft.SharePoint.Portal.WebControls.UserContextFilterWebPart;
$queryPart.FilterName="<Filter Name>";

$queryPart.ProfilePropertyName="<USER PROFILE PROPERTYC NAME>";

   $queryPart.ValueKind="ProfileValue";

$queryPart.ChromeType = [System.Web.UI.WebControls.WebParts.PartChromeType]::None; 
$oWebPartManager.AddWebPart($queryPart, "Main", 0);
$oWebPartManager.SaveChanges($queryPart);
$provWPCPs = $oWebPartManager.GetProviderConnectionPoints($queryPart) ; 
$conWPCPs = $oWebPartManager.GetConsumerConnectionPoints($listVWP) ;
foreach($provWPCP in $provWPCPs){
	
if($provWPCP.ID -eq "ITransformableFilterValues"){
 $providerCon = $provWPCP;
 }
 }

 foreach($conWPCP in $conWPCPs){

 if($conWPCP.ID -eq "DFWP Filter Consumer ID"){
 $consumerCon = $conWPCP;
 }
 }
$trans = New-Object Microsoft.SharePoint.WebPartPages.TransformableFilterValuesToParametersTransformer
$trans.ConsumerFieldNames = new-object System.string("<List Field on which Filter to be applied>");
$trans.ProviderFieldNames = new-object System.string("<Filter Name>");
	
$newConn = $oWebPartManager.SPConnectWebParts($queryPart, $providerCon, $listVWP,$consumerCon, $trans)
$oWebPartManager.SPWebPartConnections.Add($newConn);

$PublishingPage = $PubWeb.GetPublishingPage("<Page Url>");
$PublishingPage.CheckIn("Auto deployed - intermediate");

# Fix for list web-part sorting/paging issue

$PublishingPage.CheckOut();
		
$page = $web.GetFile("<Page Url>"); 

 $wpmgr = $page.GetLimitedWebPartManager([System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared);
        
 foreach($wpInstance in $wpmgr.WebParts)
 {
 if ($wpInstance.ToString() -eq "Microsoft.SharePoint.WebPartPages.XsltListViewWebPart")
 {
 $wpmgr.SaveChanges($wpInstance);
 }
 }

$page.Update();

# End fix for list web-part sorting/paging issue

$PublishingPage.CheckIn("Auto deployed - final");
$PublishingPage.ListItem.File.Publish("Auto deployed - final");

Now we are done with the scripting part once we run this script it will add the Listview, 

Query string web part on the page and set the required connection.

In url if we pass the query string value the given list view will be filtered based on that.

It was the usual scripting used everywhere. The listview webparts were added properly to the page with the following script

$web = Get-SPWeb <site url>

$PubWeb = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web) 

#Get the webpart manager

$oWebPartManager = $web.GetLimitedWebPartManager(<page url>, [System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared);

#Get the list

$list = $web.Lists[<List Name>];

#Instantiate listview webpart and added to the page

$listVWP = New-Object Microsoft.SharePoint.WebPartPages.XsltListViewWebPart;
$listVWP.Title =<Listview webpart Title.;
$listVWP.ChromeType = [System.Web.UI.WebControls.WebParts.PartChromeType]::None; 
$listVWP.Visible = $true;
$listVWP.EnableViewState = $true;

$listVWP.ListName = <List Name>;

$listVWP.ViewGuid = <View Guid>
$listVWP.WebId = $list.ParentWeb.ID;
$listVWP.ListId = [System.Guid]$list.ID;

 $oWebPartManager.AddWebPart($listVWP, "Main", 0);

Once added to the page we realized that the sorting and filtering option from the Out of the box sharepoint feature for these webparts not functioning. We tried few things during investigation to resolve the issue. We tried to add the same listview from UI and then introspect both the webparts from sharepoint designer.

But we couldn't figure out any fruitful solution. Then just realized the Savechanges method invocation is missing from our code hence added the below piece of code

$oWebPartManager.SaveChanges($listVWP);

This time once the deployment done to our surprise all seems to be working and ends with a happy note.

Still figuring out what extra this single line of code leads to the magic :)

Here I will just explain using powershell scripting how to add

1. A Listview webpart with a Query string filter webpart on a sharepoint page

2. Establish the connection between the two webpart

# SPWeb context 
$web = Get-SPWeb <site url>

$PubWeb = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web) 

#Get the webpart manager

$oWebPartManager = $web.GetLimitedWebPartManager(<page url>, [System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared);

#Get the list

$list = $web.Lists[<List Name>];

#Instantiate listview webpart and added to the page

$listVWP = New-Object Microsoft.SharePoint.WebPartPages.XsltListViewWebPart;
$listVWP.Title =<Listview webpart Title.;
$listVWP.ChromeType = [System.Web.UI.WebControls.WebParts.PartChromeType]::None; 
$listVWP.Visible = $true;
$listVWP.EnableViewState = $true;

$listVWP.ListName = <List Name>;

$listVWP.ViewGuid = <View Guid>
$listVWP.WebId = $list.ParentWeb.ID;
$listVWP.ListId = [System.Guid]$list.ID;

 $oWebPartManager.AddWebPart($listVWP, "Main", 0);

$oWebPartManager.SaveChanges($listVWP);

#Instantiate and add the Query webpart and set the connection

$queryPart = New-Object Microsoft.SharePoint.Portal.WebControls.QueryStringFilterWebPart;
$queryPart.FilterName="<Filter Name>";
$queryPart.QueryStringParameterName = "<query string parameter name>"; 
$queryPart.ChromeType = [System.Web.UI.WebControls.WebParts.PartChromeType]::None; 
$oWebPartManager.AddWebPart($queryPart, "Main", 0);
$oWebPartManager.SaveChanges($queryPart);
$provWPCPs = $oWebPartManager.GetProviderConnectionPoints($queryPart) ; 
$conWPCPs = $oWebPartManager.GetConsumerConnectionPoints($listVWP) ;
foreach($provWPCP in $provWPCPs){
	
if($provWPCP.ID -eq "ITransformableFilterValues"){
 $providerCon = $provWPCP;
 }
 }

 foreach($conWPCP in $conWPCPs){

 if($conWPCP.ID -eq "DFWP Filter Consumer ID"){
 $consumerCon = $conWPCP;
 }
 }
$trans = New-Object Microsoft.SharePoint.WebPartPages.TransformableFilterValuesToParametersTransformer
$trans.ConsumerFieldNames = new-object System.string("<List Field on which Filter to be applied>");
$trans.ProviderFieldNames = new-object System.string("<Filter Name>");
	
$newConn = $oWebPartManager.SPConnectWebParts($queryPart, $providerCon, $listVWP,$consumerCon, $trans)
$oWebPartManager.SPWebPartConnections.Add($newConn);

$PublishingPage = $PubWeb.GetPublishingPage("<Page Url>");
$PublishingPage.CheckIn("Auto deployed - intermediate");

# Fix for list web-part sorting/paging issue

$PublishingPage.CheckOut();
		
$page = $web.GetFile("<Page Url>"); 

 $wpmgr = $page.GetLimitedWebPartManager([System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared);
        
 foreach($wpInstance in $wpmgr.WebParts)
 {
 if ($wpInstance.ToString() -eq "Microsoft.SharePoint.WebPartPages.XsltListViewWebPart")
 {
 $wpmgr.SaveChanges($wpInstance);
 }
 }

$page.Update();

# End fix for list web-part sorting/paging issue

$PublishingPage.CheckIn("Auto deployed - final");
$PublishingPage.ListItem.File.Publish("Auto deployed - final");

Now we are done with the scripting part once we run this script it will add the Listview, 

Query string web part on the page and set the required connection.

In url if we pass the query string value the given list view will be filtered based on that.

As a result it was required some piece of c# coding to enable the Active directory data update. There are several articles on how to update an attribute in active directory, still for reference one can use the below code snippets       

//Open file

System.IO.FileStream inFile = new System.IO.FileStream(strFileName,System.IO.FileMode.Open,System.IO.FileAccess.Read); 

//Retrieve Data into a byte array variable

byte[] binaryData = new byte[inFile.Length]; 

int bytesRead = inFile.Read(binaryData, 0, (int)inFile.Length);

inFile.Close();

//Connect to AD

System.DirectoryServices.DirectoryEntry myUser = new System.DirectoryServices.DirectoryEntry("LDAP://" + <DISTINGUISHEDNAME FROM AD>);

--<DISTINGUISHEDNAME FROM AD Something Like CN=UserName,OU=User,DC=SampleDomain,DC=local

 // Clear existing picture if exists

myUser.Properties["thumbnailPhoto"].Clear(); 

//Update attribute with binary data from file

myUser.Properties["thumbnailPhoto"].Add(binaryData);

myUser.CommitChanges();

Now the challenge was this should be executed under a service account as for all user we are supposed to open then access door to update the Active directory properties.

To accomplish this there are certain changes we need to apply at Active directory end and trust me it was a real pain to find out  how to enable the permission for a specific user. There are several articles/blog which states the delegation but there are some additional steps that has to be executed on Active directory.

Here are the below required steps

Steps to enable Thumbnail photo update using Service Account

1.      Assign Recipient provisioning permission

• Login to the Exchange server with Active directory admin account.
• Run the powershell cmdlet.
• Execute the following command

 2.      Provide Delegate control to service account with thumbnail photo attribute read/write permission

• Load "Active Directory Users and Computers" Management Console (dsa.msc).
• Right click on the Domain or Organizational Unit containing the Domain Users that you would like your assigned user to be able to upload pictures for and select "Delegate Control". The "Delegation of Control Wizard" will be displayed on the screen. Click Next.

• Click the "Add" button to add the user(s) or group who you would like to grant permissions to change the Outlook Photo to and Click Next. 

• On the "Task to Delegate" page click the radio button "Create a custom task to delegate". Click Next. 

• On the "Active Directory Object Type" page choose the radio button "Only the following objects in the folder" and tick the check box "User objects". Click Next.

• On the "Permissions" page tick the check box "Property-specific" then in the permissions list tick the boxes for "Read thumbnail Photo" and "Write thumbnailPhoto". Click Next:

• Click "Finish" to complete the "Delegation of Control Wizard"