Sunday, February 11, 2018

SharePoint Online SystemUpdate Vs Item Update

In CSOM / REST Api for SharePoint Online, We have new method for List Item called "SystemUpdate".

This is an attempt to bring the same functionalities of Server Side Object Model (SSOM) into SharePoint Online also.

This method is very useful, if you wanted to retain the Modified By and Modified Date on your SharePoint list for Auditing purpose when you migrate to SharePoint Online.

Its appropriate to understand the difference but List Item's Update method and System Update method.

If you want to update the fields Modified, Modified by then you can explicitly assign the new values to its field or you can also ignore when you call the method Item.Update().

If you wish to retain the Modified and Modified By column but wanted to update the rest of the fields, then you should use the Item's SystemUpdate method.


 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
var pwd = "yourpassword";
            var securePassword = new SecureString();
            foreach (char c in pwd)
            {
                securePassword.AppendChar(c);
            }

            var onlineCredentials = new SharePointOnlineCredentials("murugesan@codethinker.onmicrosoft.com", securePassword);
            var context = new ClientContext("https://codethinker.sharepoint.com/");
            context.Credentials = onlineCredentials;
            List oList = context.Web.Lists.GetByTitle("Friends");
            context.ExecuteQuery();
            ListItem item = oList.GetItemById(35);
            item["xm2s"] = "+91-xxx-7887-xxxx";
            item["Modified"] = DateTime.Now.AddDays(-7);
            item.SystemUpdate();
            context.ExecuteQuery();



Image 1

Earlier my record has old value for the column
Image 2
After I call the SystemUpdate method as above Image 1, It updates only the mobile not Modifield column.


Thursday, February 08, 2018

SharePoint PnP PowerShell on Windows 2008 R2

The new SharePoint PnP PowerShells for SharePoint Online is based on CSOM implementation and it can work for On-Premise versions of SharePoint 2013 and SharePoint 2016.

To install the module for SharePoint PnP, Your PowerShell engine version must be greater than 4.0.
You can use the below command to determine the current version of your PowerShell Engine.

$PSVersionTable.PSVersion

It will shows the major , minor, Builder and revision number.

If your major version is less than 4.0 , then you need to upgrade it to next major version.

You can download and install the "Windows Management Framework 5", link
https://www.microsoft.com/en-us/download/details.aspx?id=50395

In my case, I am using the Windows 2008 R2 SP1 and selected the relevant installation file from download page

Win7AndW2K8R2-KB3134760-x64.msu

Once you upgraded to next version, you need to install the Module for "SharePoint PnP PowerShell Online."

Post upgrade , I can install the SharePoint PnP PowerShell for Online.


Friday, September 08, 2017

Thank you Microsoft

Thank you so much for the free trial for 180 days on SharePoint 2013, SQL Server and Windows 2008 R2 Standard , It was really helpful to sharpen my skills in SharePoint , Office 365 technologies . Without this offer, I would n't done this much. I was about to reinstall the another installation on my machine. But I feel guilty of doing so with out saying BIG THANKS to Microsoft . 



Thanks a lot Microsoft. 



Wednesday, August 30, 2017

Office Deployment Tool XML Generator



The Office 2016 Deployment Tool allows the administrator to customize and manage Office 2016 Click-to-Run deployments.

 This tool will help administrators to manage installations sources, product/language combinations, and deployment configuration options for Office Click-to-Run.

By default, an end user can download the Office 365 pro plus Software (Office 2013 or Office 2016 desktop application) from the https://portal.office.com after validating their credential on tenancy.


If they are assigned relevant license to use the Office 365 Pro plus, they can download it on their desktop , laptop or mobile devices including tablet and smart phones including iOS, Android and Windows phone.

This approach is called "Self-provisioning", But most of organization wants to control and manage this . So IT administrative guys in your organization can create the automated script to download and install the setup on their user machine.

Download Office 2013 Deployment Tool (ODT)

Once you extracted the downloaded file you will see the setup.exe and configuration.xml file in the folder.

IT guys can update this configuration file by adding the relevant XML node with attributes.

To simplify this process, Office Dev team has developed the page where you can select and type the relevant values , upon clicking the save button the XML string will be generated. You can easily copy the XML text into configuration.xml file and then install the setup.exe.

Office 365 Pro plus Configuration XML Editor

(https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html)