Vinay S. Patil

How to Report Per-User SharePoint Online Activity

2021-11-17T18:11:00.007+05:30

Hello All,

How can I create a report for each user detailing the interaction with documents stored in SharePoint Online libraries? Very beautiful article and useful for all SharePoint Online implementer,

View Post

Thanks to, Tony Redmond

How to Convert Word Document to PDF in SharePoint Document Library using Power Automate?

2021-11-17T18:07:00.002+05:30

Hello All,

Very nice Article, for see how to convert a Word Document to PDF in SharePoint Document Library using Power Automate without using any licence version.

View Post

Thanks Chandani Prajapati.

Building a RESTful API Using Node.JS and MongoDB

2020-06-18T16:28:00.000+05:30

Without a doubt, Application Programming Interfaces or APIs play a very important role in communication and data exchange between servers and services. From computers to smartphones and Internet of Things (IoT), applications talk and exchange info via APIs. Almost every day we use or interact with an API service, and many sites use a custom API to scale up their website. As such, learning how to develop a custom API adds lots of value to your developer profile.

Motivated by the importance of APIs and the popularity of JavaScript (JS), we’d like to show you how to develop a custom RESTful API using Node.JS and MongoDB. Along the way, you will be able to leverage and improve your JS skills. Developers can also expand this tutorial by using MySQL instead of MongoDB or securing API by adding authentication call-backs.

Prerequisites:

Install Node.js by following the appropriate guidelines for your local machine given here.
You may use Node Version Manager to install multiple versions of Node.js on your local machine.
Signup for MongoDB Atlas which is a cloud database as a service. We’re using MongoDB Atlas which offers us a free sandbox environment so that we can focus on building our REST API.
Code Editor like Visual Studio Code or Sublime Text

. Project Initialization

We need to create an application folder where our application will reside. To initialize the application, we need to create a package.json file, which will hold all the metadata for the node application. The file allows npm to handle installing the package dependencies and scripts we write to handle the application.
Assuming that you’ve Node.js installed, we can initialize the application from the command line by executing the following:

1

npm init -y

The above command will create a package.json file.

2. Install Application Dependencies

We need a file that can act as command central for our application. This file will be executed first by npm when we ask it to run our application. This file can have object instances of multiple modules that we write as well as third party modules that we install from the npm directory.
These modules are dependencies of the project. We’ll install a few of these dependencies now:

1

2

touch app.js

npm install express mongodb body-parser --save

Using the above commands we created a file called app.js which will be the main entry point to the application, and we installed a few dependencies that are essential to start our application.
These dependencies are:
1. Express: This is a Node.js framework.
2. MongoDB: This is an official module provided by the MongoDB team to help our Node.js application communicate with MongoDB.
3. body-parser: This package will allow us to handle request bodies with Express.

Why use body-parser?

Let’s say you are sending an HTML form data to Node.js server i.e. you made a request to the server. HTTP sends your form data in bits and pieces which are intended to get assembled as they reach their destination. To extract these bits and pieces of data and assemble it so it is in a format that can be useful, we use a body-parser middleware.

3. Run the Application

Let’s run the code for our application –

1

2

3

4

5

6

7

8

const Express = require("express");

const BodyParser = require("body-parser");

const MongoClient = require("mongodb").MongoClient;

const ObjectId = require("mongodb").ObjectID;

var app = Express();

app.use(BodyParser.json());

app.use(BodyParser.urlencoded({ extended: true }));

app.listen(5000, () => {});

Here, we’re importing our downloaded dependencies. We initialize the express framework by utilizing the Express object that will use the express framework to start the server and run our application at a given port and configure the body-parser, which is a middleware to parse incoming chunks of data.

4. Test the Application

We can test the application by running the following:

1

node app.js

The server will be listening on port 5000 for requests according to the above boilerplate we wrote.

5. Establish Connection with MongoDB

We will need the connection string for MongoDB. This can be found in the Atlas dashboard by choosing Clusters, then the Overview tab followed by the Connect button.
We need to add the string to our app.js and make the following changes to the code

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

const Express = require("express");

const BodyParser = require("body-parser");

const MongoClient = require("mongodb").MongoClient;

const ObjectId = require("mongodb").ObjectID;

const CONNECTION_URL = ;

const DATABASE_NAME = "accounting_department";

var app = Express();

app.use(BodyParser.json());

app.use(BodyParser.urlencoded({ extended: true }));

var database, collection;

app.listen(5000, () => {

    MongoClient.connect(CONNECTION_URL, { useNewUrlParser: true }, (error, client) => {

        if(error) {

            throw error;

        }

        database = client.db(DATABASE_NAME);

        collection = database.collection("personnel");

        console.log("Connected to `" + DATABASE_NAME + "`!");

    });

});

Here, we’ve defined the connection string to use. You need to add a CONNECTION_URL property according to the connection string you received from MongoDB Atlas. We’ve also defined the database name which we wish to create (if not already present and collection).
We establish a connection once we start again the application and use globally defined variables so that they can be used in each of our endpoints.

Now let’s start designing our HTTP consumable API endpoints.

6. Build REST API Endpoints

Now we’re going to develop endpoints for creating and querying the data. Let’s create an endpoint to add the data. Add the following code to app.js:

1

2

3

4

5

6

7

8

app.post("/personnel", (request, response) => {

    collection.insert(request.body, (error, result) => {

        if(error) {

            return response.status(500).send(error);

        }

        response.send(result.result);

    });

});

We aren’t doing any data validation, but when a client makes a POST request to the /personnel endpoint, we take the body and insert it into our collection. Depending on the success or error response of the database, we return information back to the client.

7. Put Things Together

Now, things are starting to come together. Let’s test out our application.

1

2

3

4

curl -X POST \

    -H 'content-type:application/json' \

    -d '{"firstname":"John","lastname":"Doe"}' \

    http://localhost:5000/personnel

If you do not receive any errors, you’ll see the personnel record for John Doe added into MongoDB database of accounting_department and under collection personnel. Feel free to add more records to your database.

GET

Now let’s create an endpoint to retrieve all the records data. Add the following code to app.js:

1

2

3

4

5

6

7

8

 app.get("/personnel", (request, response) => {

    collection.find({}).toArray((error, result) => {

        if(error) {

            return response.status(500).send(error);

        }

        response.send(result);

    });

});

The goal here is to return all data in our collection representing people. We have no query conditions, hence the empty {} in the find command, and the results get converted into an array.
Let’s test this out using cURL, a command-line tool for transferring data and supports HTTP; a very good ad-hoc tool for testing REST services.

1

curl -X GET http://localhost:5000/personnel

GET (by ID)

By now let’s assume you’ve added more records into your database. API consumers will need to retrieve a single record according to its ID.

Write the following endpoint to your app.js:

1

2

3

4

5

6

7

8

app.get("/personnel/:id", (request, response) => {

    collection.findOne({ "_id": new ObjectId(request.params.id) }, (error, result) => {

        if(error) {

            return response.status(500).send(error);

        }

        response.send(result);

    });

});

We’re going to use a route parameter to get specific personnel information from MongoDB. Parameters are options you can pass with the endpoint (such as specifying the response format or the amount returned) to influence the response. This time around we have a route parameter called id which will represent an object id in MongoDB. Using the findOne method, we can get a single record based on the criteria included in the object. The id isn’t a string which is why we have to use the ObjectId.

Depending on the actual data in our database, we can do a cURL command similar to this:

1

curl -X GET http://localhost:5000/personnel/4b103f89403f841059524fd1

Conclusion

In this tutorial, we’ve learned how to develop a custom API and connect it with MongoDB to fetch and manipulate the data. From here, you can take different steps. For instance, you can expand this project by adding more features like data validation to it. You can also improve the API security and scalability by following Node.JS best practices.

Branding Theme for SharePoint Online

2020-05-26T16:54:00.002+05:30

Hello All,

Its very long, I have not posted blog.

Just Starting Series for SharePoint Online. To begin with lets take a look for SharePoint Online Branding.

SharePoint Online (SPO), has very limited scope for branding. SharePoint by default provide themes to brand your SPO as per your organization.

1) Microsoft provided a tool for creating theme for your SPO, Goto ThemeGenerator

2) After modification as per your requirement, go ahead and see the Output, as follows

3) Now open the SharePoint Online Management Shell, and connect to your SPO tenant.

Connect-SPOService -Url "https://tenantName-admin.sharepoint.com/" -Credential "UserName"

4) Enter user password

5) Now Get all Custom themes available in your tenant using

Get-SPOTheme

6)Now Install the Theme, copy the poweshell theme generated in step 2, and assign to one variable,

$themePalette = @{

>> "themePrimary" = "#002b4d";

>> "themeLighterAlt" = "#ceddea";

>> "themeLighter" = "#a5c1d6";

>> "themePrimary" = "#002b4d";

>> "themeLighterAlt" = "#ceddea";

>> "themeLighter" = "#a5c1d6"; >> "themeLight" = "#80a6c2";

>> "themeTertiary" = "#608daf";

>> "themeSecondary" = "#44759b";

>> "themeDarkAlt" = "#2d6087";

>> "themeDark" = "#194d74";

>> "themeDarker" = "#0b3b60";

>> "neutralLighterAlt" = "#f8f8f8";

>> "neutralLighter" = "#f4f4f4";

>> "neutralLight" = "#eaeaea";

>> "neutralQuaternaryAlt" = "#dadada";

>> "neutralQuaternary" = "#d0d0d0";

>> "neutralTertiaryAlt" = "#c8c8c8";

>> "neutralTertiary" = "#b1afaf";

>> "neutralSecondary" = "#989595";

>> "neutralPrimaryAlt" = "#7e7c7c";

>> "neutralPrimary" = "#1a1919";

>> "neutralDark" = "#4c4a4a";

>> "black" = "#333131";

>> "white" = "#ffffff";

>> "primaryBackground" = "#ffffff";

>> "primaryText" = "#1a1919";

>> "bodyBackground" = "#ffffff";

>> "bodyText" = "#1a1919";

>> "disabledBackground" = "#f4f4f4";

>> "disabledText" = "#c8c8c8";

>> }

7) Now Install theme to your tenant using

Add-SPOTheme -Name "ThemeName" -Palette $themePalette -IsInverted $false

8) Now you can go in SPO Site Collection, and change the theme, that you installed..

Hide Field in New and Edit Forms of SharePoint Online List using Powershell

2020-01-20T17:00:00.002+05:30

Hello,

Just tried to hide SharePoint List fields from New and Edit Forms, wrote a powershell script,

Connect to SharePoint
Load SharePoint List context,
Get Field to hide from forms
Use functions to hide field from SharePoint forms.

#Load SharePoint CSOM Assemblies
Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.dll"
Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.Runtime.dll"

#Config Parameters
$SiteURL= "SharePoint Site URL"
$ListName="ListName"
$FieldName = "ColumnName" #Display Name

#Setup Credentials to connect
$Cred = Get-Credential
$Cred = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($Cred.UserName,$Cred.Password)

Try {
#Setup the context
$Ctx = New-Object Microsoft.SharePoint.Client.ClientContext($SiteURL)
$Ctx.Credentials = $Cred

#Get the web, List and Field objects
$Web=$Ctx.Web
$Ctx.Load($Web);
$Ctx.ExecuteQuery()

$List=$web.Lists.GetByTitle($ListName)
$Ctx.Load($List);
$Ctx.ExecuteQuery()

$Field = $List.Fields.GetByTitle($FieldName)

$Ctx.Load($Field);
$Ctx.ExecuteQuery()

#Hide the column from New & Edit forms
$Field.SetShowInEditForm($False)
$Ctx.ExecuteQuery()
$Field.SetShowInNewForm($False)
$Ctx.ExecuteQuery()
$Field.UpdateAndPushChanges($True)
$Ctx.ExecuteQuery()

Write-host -f Green "List Field hidden Successfully!"
}
Catch {
write-host -f Red "Error hiding List Column: " $_.Exception.Message
}

Project Management SharePoint Template

2019-12-03T16:18:00.003+05:30

Hello All,

I was looking for a free template for Project Management in SharePoint on-prem. or online, After searching a lot found one good template 'BrightWork'..

It provides

PLAN AND MANAGE WITH STANDARDIZED TEMPLATE.
SHARE PROGRESS WITH AUTOMATED REPORTS
COLLABORATE WITH A TEAM-FOCUSED PROJECT SITE

Its very easy to use and can be installed in SharePoint On-Prem. or online environment.

Thanks BrightWork..

SharePoint 2016 - New Features

2017-05-09T12:55:00.000+05:30

SharePoint Server 2016 is our most reliable, scalable, secure and high-performant server release ever. With built-in Hybrid Cloud capabilities, it is the premier choice for organizations who are looking to take advantage of the latest innovations in Microsoft Cloud offerings while also maintaining critical content or custom applications on-premises. SharePoint Server 2016 will help organizations unlock breakthrough performance and resiliency as well as quickly build solutions and extend data across on-premises and Office 365 with the confidence that their data will be safe and secure.

SharePoint Server 2016 will deliver enhancements and new capabilities in three major areas:

Improved user experiences

Mobile Experience
Personalized insights
People-centric file storage and collaboration

Cloud-inspired infrastructure

Improved performance and reliability
Hybrid cloud with global reach
Support and monitoring tools

Compliance and reporting

New data protection and monitoring tools
Improved reporting and analytics
Trusted platform

Boundaries and Limitation in comparison to SharePoint Server 2013

New and improved features in SharePoint Server 2016 Release Candidate

MinRole farm topology

The role of a server is specified when you create a new farm or join a server to an existing farm. SharePoint automatically configures the services on each server based on the server role, optimizing the performance of the farm based on that topology. There are six predefined server roles that are available, as shown in the following table.

Central Administration is no longer provisioned on all servers by default

SharePoint Server 2016 Central Administration is now provisioned on the first server in a farm by default when using the SharePoint Products Configuration Wizard. Central Administration is not provisioned on additional servers in a farm by default.

Compliance features

The document deletion policy allows you to delete documents in users' OneDrive for Business sites after specific periods of time. The In-Place Hold policy allows administrators to preserve documents, email, and other files.

Document Library accessibility

The following features are now available for working in SharePoint Server 2016 Release Candidate document libraries

Landmarks to a page make it easier to navigate, and there are alt text improvements for all major navigation links.

Keyboard shortcuts
Focus improvements
Announcements for upload progress.
Improved callout reading.
Fixed use of color issues for views switcher.
Updates to the Help documentation.

Fast Site Collection Creation

This new feature provides templates that work at same level as SQL Server, which reduces the round trips required between the SharePoint and SQL servers.

File names - expanded support for special characters

SharePoint has historically blocked file names that included the &, ~, {, and } characters, file names that contained a GUID, file names with leading dots, and file names longer than 128 characters. These restrictions are removed in SharePoint Server 2016 Release Candidate and are now available to use.

Hybrid in SharePoint Server 2016 Release Candidate

In SharePoint Server 2016 Release Candidate, new hybrid features are available to enable hybrid solutions.

Hybrid sites
Hybrid sites features
Hybrid OneDrive for Business
Cloud hybrid search

Identify and search for sensitive content in both SharePoint Server 2016 Release Candidate and OneDrive documents

With this new capability, you can:

Search for sensitive content across SharePoint Server 2016 Release Candidate, SharePoint Online, and OneDrive for Business.
Leverage 51 built-in sensitive information types (credit cards, passport numbers, Social Security numbers, and more).
Use DLP Queries from the eDiscovery site collection to discover sensitive content relating to common industry regulations from the SharePoint eDiscovery Center, identify offending documents, and export a report.
Turn on DLP Policies from the Compliance Policy Center site collection to notify end users and administrators when documents with sensitive information are stored in SharePoint and automatically protect the documents from improper sharing.

App Launcher

The App Launcher provides a new navigation experience where all your apps are easily available from the top navigation bar. You can quickly launch your application, browse sites and access your personal files.

Image and video previews

Now you can see a preview by hovering the mouse over the image or video, or by clicking on them

Large file support

Previous versions of SharePoint did not support uploading or downloading files larger than 2,047 MB. SharePoint 2016 now allows you to upload or download larger files. You can configure the desired maximum file-size limit on a per-web application basis in your SharePoint farm.

Power Pivot add-in and Power View are now available to use with SharePoint Server 2016 Release Candiate

Power Pivot add-in and Power view are after the release of SQL Server 2016 CTP 3.1 available in SharePoint Server 2016.

Sharing

The following list shows the sharing improvements that are available for SharePoint Server 2016 Release Candidate:

Create and Share folder
Sharing Hint
See who the folder is shared with when viewing a folder
Members can share
Improved invitation mail
One-click email to approve or deny a request for access

SharePoint Search Service application

SharePoint Search supports indexing of up to 500 million items per Search Server application.

SMTP connection Encryption

In SharePoint 2013 & SharePoint 2010, we always leverage port 25 for any communication, now SharePoint 2016 supports STARTTLS connection encryption. In older versions of SharePoint all the communication through emails, alerts was unencrypted. In SharePoint 2016, we can run on non-default ports which encrypted communication between SharePoint and the messaging service. This can be configurable through Central Administration and PowerShell.

Authentication

SAML authentication becomes a first class citizen in SharePoint 2016.
There were multiple authentication providers in SharePoint 2013 like windows Claims, form based authentication, SAML Claims, WSFED and others to provide backward compatibility.
In SAML Claims is the default and recommended model but SharePoint 2016 will continue to support Windows Identity.

New controls for working with OneDrive for Business

You can click a control to create new Office documents, upload files, synchronize your files for offline use, and share your files.

Open Document Format (ODF) available for document libraries

The Open Document Format (ODF) enables you to create new files in a document library and save as ODF files so that users can edit the new file with a program they choose.

How to do with SharePoint Library using Powershell

2016-05-03T14:20:00.004+05:30

Hi,

I am working on PowerShell scripts to automate deployment for one of client,

Here is post :: How to do with SharePoint Library using Powershell,

# Create Document Library

# Add SharePoint Snapin to PowerShell
if((Get-PSSnapin | Where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null) {
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}
function CreateLibrary
{
    param ($LibName)
    try
    {
        $spListCollection = $OpenWeb.Lists
        $spLibrary = $spListCollection.TryGetList($LibName)
        if($spLibrary -ne $null) {
            Write-Host -f Yellow "Library $LibraryName already exists in the site"
        }
        else
        {
            $spListCollection.Add($LibName, "", $listTemplate)
            $spLibrary = $OpenWeb.GetList($OpenWeb.ServerRelativeUrl+"/"+$LibName)
            Write-Host -f Green "Created Document Library $LibName"
        }
    }
    catch [System.Exception]
    {
write-host -f red "Not set Likes Setting on " $_.Exception.ToString()
    }
}
$SiteURL = Read-Host -Prompt 'Enter Root Site URL and / @ end'
$OpenWeb = Get-SPWeb $SiteURL
$listTemplate = [Microsoft.SharePoint.SPListTemplateType]::DocumentLibrary
CreateLibrary -LibName "Department"

#enable Content Types

$spLibrary.ContentTypesEnabled = $true
$spLibrary.Update()

#Add Content Type

$ctype = "Report Data Source"
$ctToAdd = $rootSite.ContentTypes[$ctype]
$ct = $spLibrary.ContentTypes.Add($ctToAdd)

#Enable Versioning

$spLibrary.EnableVersioning = $true
$spLibrary.EnableMinorVersions = $false
$spLibrary.Update();

# Enable Versioning with Limit

$spLibrary.EnableVersioning = $true
$spLibrary.EnableMinorVersions = $false
$spLibrary.MajorVersionLimit = 3
$spLibrary.Update();

#Order Columns

$FieldOrder = New-Object System.Collections.Specialized.StringCollection
$FieldOrder.Add("ContentType")
$FieldOrder.Add("FileLeafRef")
$FieldOrder.Add("Title")
$FieldOrder.Add("CategoryDescription")
foreach ($ctype in $spLibrary.ContentTypes)
{
      if($ctype.Name -ne "Folder")
      {
           $ctype.FieldLinks.Reorder($FieldOrder);
           $ctype.Update($false);
     }
}

#Enable Moderation and Draft Version

$spLibrary.EnableModeration = $true
$spLibrary.DraftVersionVisibility = 2
$spLibrary.Update();

# Enable Rating Settings

$assembly=[System.Reflection.Assembly]::Load("Microsoft.SharePoint.Portal, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c")
$reputationHelper =$assembly.GetType("Microsoft.SharePoint.Portal.ReputationHelper");
$bindings = @("EnableReputation", "NonPublic", "Static");
[System.Reflection.BindingFlags]$flags = [System.Reflection.BindingFlags]::Static -bor [System.Reflection.BindingFlags]::NonPublic;
$methodInfo = $reputationHelper.GetMethod("EnableReputation", $flags);
$values = @($spLibrary, "Likes", $false);
$methodInfo.Invoke($null, @($values));

# Create View

$viewTitle = "Dashboard_User" #Title property
$viewFields = New-Object System.Collections.Specialized.StringCollection
$viewFields.Add("DocIcon") > $null
$viewFields.Add("LinkFilename") > $null
$viewFields.Add("CategoryDescription") > $null
$viewFields.Add("BIKeywords") > $null
$viewFields.Add("LikesCount") > $null
$viewQuery = ""
$viewRowLimit = 5
$viewPaged = $true
$viewDefaultView = $false
$newview = $spLibrary.Views.Add($viewTitle, $viewFields, $viewQuery, $viewRowLimit, $viewPaged, $viewDefaultView)

Create SharePoint Web Part Page using PowerShell

2016-03-29T12:11:00.000+05:30

Hi,

I am working on PowerShell scripts to automate deployment for one of client,

Here is post :: Create SharePoint Web Part Page using PowerShell,

# Add SharePoint Snapin to PowerShell
if((Get-PSSnapin | Where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null) {
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}

#function to create web part page in Site Pages
function CreateBlankWebpartPage

{
    Param($WebPartPageName)
    try
    {
        $pageLayout = 1
        $spListCollection = $OpenWeb.Lists
        $spLibrary = $spListCollection.TryGetList("Site Pages")
        $xml = "" + $spLibrary.ID + "NewWebPageNewWebPartPage" + $pageLayout + "true" + $WebPartPageName + ""
        $OpenWeb.ProcessBatchData($xml)
        foreach($listItem in $spLibrary.Items)
        {
            if($($listitem.URL).Contains("$WebPartPageName" + ".aspx"))
            {
                $myListItem = $listItem
                break;
            }
        }
        $pageUrl = $($myListItem.URL)
        Write-Host -f Green "New page is Created with Url - $pageUrl"
    }
    catch [System.Exception]
    {
        write-host -f red $_.Exception.ToString()
    }
}

$SiteURL = Read-Host -Prompt 'Enter Root Site URL and / @ end'

$OpenWeb = Get-SPWeb $SiteURL

CreateBlankWebpartPage -WebPartPageName "My Favorites"
CreateBlankWebpartPage -WebPartPageName "Pending Approval"
CreateBlankWebpartPage -WebPartPageName "My Tasks"
CreateBlankWebpartPage -WebPartPageName "My Reports"

SharePoint Left Navigation Using PowerShell

2016-03-29T11:45:00.003+05:30

Hi,

I am working on PowerShell scripts to automate deployment for one of client,

Here is post :: Creating SharePoint Left Navigation using PowerShell,

First step will be creating XML File as below,

<?xml version="1.0" encoding="utf-8"?>
<Navigation>
<Headings>
<Heading Title="Heading1" Url="" Description="" Permission="domain\UserGroup">

      <NavLink Title="HeadNav1" Url"/>
      <NavLink Title="HeadNav2" Url=""/>
    </Heading>
    <Heading Title="Heading2" Url="" Description="" Permission="domain\UserGroup" >
      <NavLink Title="HeadNav3" Url=""/>
      <NavLink Title="HeadNav4" Url=""/>
    </Heading>
    <Heading Title="Heading3" Url="" Description="" Permission="domain\UserGroup" >
    </Heading>
</Headings>
</Navigation>

Save the xml file, now time for PowerShell script to read the xml and build the left navigation.

PowerShell script will first clear the existing Left Navigation and then Create New left Navigation with

Heading
NavLink Under Heading
Description for Heading
URL link for Heading and NavLink
Permission (Target Audience) for Heading

# Add SharePoint Snapin to PowerShell
if((Get-PSSnapin | Where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null) {
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}

function LeftNavBar{

    $qlNav = $OpenWeb.Navigation.QuickLaunch

    #Get XML File
    $xmlFilePath = "$PSScriptRoot\.xml"
    $xmlFile = [xml](Get-Content($xmlFilePath))
    $oldWebUrl = $OpenWeb.Url
    $currentLinks = @()

    #Clear Quick Launch links
    $qlNav | ForEach-Object {
        $currentLinks = $currentLinks + $_.Id
    }
    $currentLinks | ForEach-Object {
        $currentNode = $OpenWeb.Navigation.GetNodeById($_)
        write-host -f Yellow "Deleting" $currentNode.Title "and all child navigation links..."
        $qlNav.Delete($currentNode)
    }

    #Create Quick Launch Links
    $xmlFile.Navigation.Headings.Heading | ForEach-Object {
        $headingNode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode($_.Title, $_.Url)
        #$headingNode.Properties["Description"] = $_.Description
        #$headingNode.Update();
        write-host -f Green "Creating Heading:" $_.Title
        $heading = $qlNav.AddAsLast($headingNode)
        $heading.Properties["Audience"] = $_.Permission
        $heading.Update();

        $_.NavLink | ForEach-Object {
            if($_.Title -ne $null) {
            $linkNode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode($_.Title, $_.Url)
            write-host -f Green "Creating Navigation Link:" $_.Title
            $link = $heading.Children.AddAsLast($linkNode)
            }
        }
    }


    $OpenWeb.Dispose()
}

$SiteURL = Read-Host -Prompt 'Enter Root Site URL and / @ end'

$OpenWeb = Get-SPWeb $SiteURL

LeftNavBar

SharePoint Site Column Using Powershell

2016-03-29T11:14:00.000+05:30

Hi,

I am working on PowerShell scripts to automate deployment for one of client,

Here is first post :: Create Site Columns using PowerShell,

# Add SharePoint Snapin to PowerShell
if((Get-PSSnapin | Where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null) {
Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}

#Create Multi Select Lookup Column
function CreateCategory
{
    param ($sSiteCollectionUrl)
    try
    {
        $web = Get-SPWeb $SiteURL

        #Configuration
        $lookupFieldWebGuid=$web.ID
        $lookupList = $web.Lists.TryGetList("CategoryMaster")
        $lookupListGuid = $lookupList.ID
        $fieldDisplayName="Category"
        $fieldInternalName="BICategory"
        $sitecolGroup = "OwnColumns"
        $showField = "Title"
        $fieldDescription = "'Defines content for users' search functionality. Select multiple options, if necessary.'"
        $fieldHidden="FALSE"
        $fieldReadonly = "FALSE"
        $fieldMulti = "TRUE"
        $fieldRequired = "TRUE"
        $unlimitedLength = "FALSE"
        #End of configuration

        $lookupXMLString = '
        Required="' + $fieldRequired + '" EnforceUniqueValues="FALSE" WebId="' + $lookupFieldWebGuid + '" ShowField="' + $showField + '" UnlimitedLengthInDocumentLibrary="' + $unlimitedLength + '"
        Group="' + $sitecolGroup + '" Mult="' + $fieldMulti + '" Sortable="FALSE" StaticName="' + $fieldInternalName + '" List="' + $lookupListGuid + '"
        Name="' + $fieldInternalName + '" Hidden="' + $fieldHidden + '" ReadOnly="' + $fieldReadonly + '">

'
        #Create site column from XML string
        $web.Fields.AddFieldAsXml($lookupXMLString)
        Write-Host "The Category site column has been added." -foregroundcolor green
    }
    catch [System.Exception]
    {
        write-host -f red $_.Exception.ToString()
    }
}

#Create Date Column
function CreateDate
{
    param ($sSiteCollectionUrl)
    try
    {
        $web = Get-SPWeb $SiteURL

        $fieldXML = '
        Name="Report_x0020_Date"
        Description="Report Publish Date"
        DisplayName="Report Date"
        StaticName="Report Date"
        Format="DateOnly"
        Group="OwnColumns"
        Hidden="FALSE"
        Required="FALSE"
        Sealed="FALSE"
        ShowInDisplayForm="TRUE"
        ShowInEditForm="TRUE"
        ShowInListSettings="TRUE"
        ShowInNewForm="TRUE">
'
        #Create site column from XML string
        $web.Fields.AddFieldAsXml($fieldXML)

        write-Host "Added the field Report Date to the Site" -foregroundcolor green

        #Disposing SPSite and SPWeb objects
        $web.Dispose()

    }
    catch [System.Exception]
    {
        write-host -f red $_.Exception.ToString()
    }
}

#Create Choice Column
function CreateFrequency
{
    param ($sSiteCollectionUrl,$sFieldDisplayName, $sFieldInternalName, $sFieldType)
    try
    {
        $spSite = Get-SPSite -Identity $sSiteCollectionUrl
         $spWeb = $spSite.OpenWeb()


        #We check the field type is not null
        if($sFieldType -ne '')
        {
            $spWeb.Fields.Add($sFieldInternalName,$sFieldType,$false)
            $spChoiceField=$spWeb.Fields.GetField($sFieldInternalName)
            write-Host "Added the field Frequency to the Site" -foregroundcolor green
            $spChoiceField.Group="OwnColumns"
            $spChoiceField.Choices.Add("Weekly")
            $spChoiceField.Choices.Add("Months")
            $spChoiceField.Choices.Add("Annually")
            $spChoiceField.Choices.Add("Adhoc")
            $spChoiceField.Title=$sFieldDisplayName
            $spChoiceField.DefaultValue=""
            $spChoiceField.Required = "TRUE"
            $spChoiceField.FillInChoice=$false
            $spChoiceField.Update()
        }

        #Disposing SPSite and SPWeb objects
        $spWeb.Dispose()
    }
    catch [System.Exception]
    {
        write-host -f red $_.Exception.ToString()
    }
}

#Create User Column
function CreateOwner
{
    param ($sSiteCollectionUrl)
    try
    {
        $web = Get-SPWeb $SiteURL

        $fieldXML = '
        Name="BIOwner"
        Description="Main business owner of published content."
        DisplayName="Owner"
        List="UserInfo"
        ShowField="ImnName"
        UserSelectionMode="PeopleOnly"
        UserSelectionScope="0"
        StaticName="BIOwner"
        Group="OwnColumns"
        Hidden="FALSE"
        Required="TRUE"
        Sealed="FALSE"
        ShowInDisplayForm="TRUE"
        ShowInEditForm="TRUE"
        ShowInListSettings="TRUE"
        ShowInNewForm="TRUE">
'
        #Create site column from XML string
        $web.Fields.AddFieldAsXml($fieldXML)

        write-Host "Added the field Owner to the Site" -foregroundcolor green

        #Disposing SPSite and SPWeb objects
        $web.Dispose()

    }
    catch [System.Exception]
    {
        write-host -f red $_.Exception.ToString()
    }
}

# get Site URL

$SiteURL = Read-Host -Prompt 'Enter Root Site URL and / @ end'
$rootWeb = Get-SPWeb $SiteURL
CreateCategory -sSiteCollectionUrl $SiteURL
CreateDate -sSiteCollectionUrl $SiteURL
CreateOwner -sSiteCollectionUrl $SiteURL
CreateFrequency -sSiteCollectionUrl $SiteURL -sFieldDisplayName "Frequency" -sFieldInternalName "Frequency" -sFieldType "Choice"

Highlighted in blue color can be change as per your requirement.

Thanks

First look at SharePoint Server 2016 IT Preview

2015-08-25T21:36:00.001+05:30

SharePoint 2016

2015-08-11T16:06:00.000+05:30

Today, we found a large disparity between Office 365 features and SharePoint 2013 on-premises. SharePoint 2016 aims to solve this by basically becoming the new code-base for on-premise. They are back-porting almost all the capabilities in SharePoint Online and bringing them to the on-prem builds.

Hardware Requirements for SharePoint 2016

The hardware requirements really don't change from SharePoint 2013.

Component	Specification
RAM	· 12-16 GB RAM for production · more for development
CPU	· 4 cores
Disk	· 80GB for OS

Software Requirements for SharePoint 2016

Things start to change a little when it comes to the software requirements. The minimum OS and SQL get a bump.

Component	Specification
Operating System	· Windows Server 2012 R2 · Window Server 10
Pre requisites	· Windows Management Framework · Application Server Role · Web Server IIS Role · .Net Framework 4.5.2 · Update for .Net Framework 4 · MS SQL Server 2012 Native Client · MS Identity Extension · MS Sync Framework runtime V1.0 · Windows AppFabric 1.1 · MS Identity Foundation V1.1 · MS Information Protection and Control client · MS WCF Data Service

No More SQL Server Express

The big change is that standalone / single server installs will NOT support the Windows Internal database or SQL Server Express. You MUST install and use SQL Server Standard / Enterprise / Datacenter, etc. It can be on the same server.

Upgrade Paths to SharePoint 2016

The paths are the same as from 2010 to 2013. You can either DB attach or use a 3rd-party migration tool. That hasn’t changed. But there has been speculation around if you are required to go to 2013 before 2016 or if you can skip. Bill seemed to put this to rest. You MUST upgrade to SharePoint 2013 before you can upgrade to SharePoint 2016. In addition, any site collections that use the 2010 format will have to be converted to 2013 (15) mode before upgrading to 2016.

Another huge change coming down the pipe in upcoming months is a new migration API. This has been mentioned a lot this week when looking to migrate content to Office 365. This will help facilitate easier upgrades from on-premise to SharePoint Online / OneDrive for Business scenarios.

Identity

In SharePoint 2016, SAML claims becomes a first-class citizen and the default authentication though it will still support Windows Identity over SAML claims. Basically this is aimed to set the stage for cloud integration, being cloud ready and trust Azure AD. This in essence is one authentication provider to rule them all.

Roles & Services

There are some HUGE and fundamental changes going on here. Defined roles are coming back (think 2007 WFE) to SharePoint 2016 but in a whole different way. We’ve all seen where a CU will get released; gets pulled due to regression and has to be re-released. This is because Microsoft can’t test reliability in every combination of service configuration. They have established what they call MinRoles. After you install the bits and fire up psconfig then you choose what role this server will perform in the farm.

Think of Search. When you deploy it you have to run all this PowerShell. Now SharePoint will configure the server with only the necessary bits and services for Search to run on this box and nothing else. Since SharePoint configured it, they know how it should be and can plan for and test this configuration. This is seen in new rules in the Health Analyzer and even a Fix it button in Services in Farm in Central Admin if things get out of compliance configuration wise. You can still create these in PowerShell using a new switch called –isserverrole for psconfig. Scaling an environment becomes very expected and easy: just stand up a new server; join to the farm and pick a role.

This allows for tremendously smaller update patches: from 40 installer files to 2; 18 language pack files to 1.

Boundaries and Limits

This information is fuzzier but these are the currently planned new limits in SharePoint 2016.

Component	Specification
Content Database size	· >1 terabyte
# of Site Collections per content DB	· 100,000
List threshold	· >5000
Max File size	· increased from 2GB to 10GB · removed character restrictions
Search Index	· 500 million items

Other Improvements

SharePoint 2016 real time telemetry. The User Profile Service will NOT be included in SharePoint. It will be separated and can be run independently from SharePoint
Project Server has its databases consolidated into the Content DB”
Files shared will have “durable” links. If they are moved, renamed, etc., the link will still work using resource ID
Leveraging BITS for faster download/upload of these 10GB files
Fast Site Collection creation – basically does a SQL table row copy instead of going through API (spsite.copy) in content DB
Real time telemetry
Basically much more robust dashboards and analytics from an improved health and usage database
Allow storage of ODF files in document libraries which any editing program can edit
Enhancements in compliance for document fingerprinting, classification IDs, etc.
Cloud Search Service - I will talk about this later
Extranet – some form of ability leverage Office 365 identity federation service - think external users in SharePoint Online but now in on-prem
Much easier way to configure hybrid via new UI tool

TechNet Post for Search in SharePoint 2013

2015-06-11T11:43:00.000+05:30

I come one blog post on TechNet which is deep and interesting for Search in SharePoint 2013.

Thanks to "Bella_Engen"

How to sync local Active Directory to Office 365 with DirSync

2015-05-21T12:32:00.000+05:30

Very Nice and interesting post for sync local Active directory to O 365 using DirSync..

Sync Premises Active Directory to Office-365

The remote server returned an error: (403) Forbidden while Connecting to SharePoint site with Managed CSOM

2015-04-15T12:38:00.002+05:30

While I was working with my site with Managed CSOM got below error.

System.Net.WebException: The remote server returned an error: (403) Forbidden.at System.Net.HttpWebRequest.GetResponse()at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()at Microsoft.SharePoint.Client.ClientContext.GetFormDigestInfoPrivate()at Microsoft.SharePoint.Client.ClientContext.EnsureFormDigest()at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()at SharePointConsoleApplication1.Program.ConnectSharePoint() in c:\Vinay\Projects\SharePointConsoleApplication1\SharePointConsoleApplication1\Program.cs:line56at SharePointConsoleApplication1.Program.Main(String[] args) in c:\Vinay\Projects\SharePointConsoleApplication1\SharePointConsoleApplication1\Program.cs:line31

This looks strange. After doing some research on Google I got the below solution.

private static void ConnectSharePoint()
{
try
{
using (ClientContext clientContext = new ClientContext(""))
{
clientContext.ExecutingWebRequest += clientContext_ExecutingWebRequest;
List list = clientContext.Web.Lists.GetByTitle("");
clientContext.Load(list);
clientContext.ExecuteQuery();
Console.WriteLine("Connected");
}
}
catch
{ throw; }
}

static void clientContext_ExecutingWebRequest(object sender, WebRequestEventArgs e)
{
try
{
e.WebRequestExecutor.WebRequest.Headers.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f");
}
catch
{ throw; }

}

Hope this solution will help you and save time.

How to Integrate PeopleSoft into SharePoint with Zero Development!

2015-03-23T09:49:00.001+05:30

How to Integrate PeopleSoft into SharePoint with Zero Development!

SharePoint 2010 to SharePoint 2013 Migration : Part 2

2014-03-25T10:23:00.000+05:30

:: SharePoint 2010 to SharePoint 2013 Migration : Part 2 ::

Hello

Continue for SharePoint 2010 to SharePoint 2013,

Part 2 :: Custom Code Migration to VS 2013

After migrating database of SharePoint 2010 to SharePoint 2013, if there is custom code for SharePoint 2010 then we can deply the wsp as is, but if any changes in the code then it is hard to maintain two enviornment of SharePoint, so it is better to upgrade the code to VS 2013.

Here are the steps to be consider for upgrading custom code,

1) Install VS 2013

2) Copy Solutions built in VS 2010. On SharePoint 2013.

3) Run the VS 2013 with Admin Credentials

4) Open the Solution in VS 2013, which will ask for upgrade, if solution is upgraded then it cannot be used for VS 2010, so always make copy of code.

5) After code is upgraded it will show the Upgrade reports.

6) Open the .csproj files in Solutions for all projects, and replace

<TargetFrameworkVersion>v3.5</TargetFrameworkVersion> with <TargetFrameworkVersion>v4.5</TargetFrameworkVersion>

7) Open the Packages present in the Solutions, and change the SharePoint Product Version to 15.0

8) Change the Microsoft.SharePoint Reference in non-SharePoint project,

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.dll

9) Add other third party reference used in code.

10) Change the Assembly version of SharePoint DLL as, 14.0.0.0 to 15.0.0.0
Assembly="Microsoft.SharePoint, Version=15.0.0.0,

11) Now if anything /_layouts/ or /_CONTROLTEMPLATES/ used in code change it to /_layouts/15/ or /_CONTROLTEMPLATES/15/ which will deploy the related files in 15 hive...

12) Now build the solution and if any missing reference then add the reference and solution is ready for deployment.

SharePoint 2010 to SharePoint 2013 Migration : Part 1

2014-03-25T09:21:00.000+05:30

:: SharePoint 2010 to SharePoint 2013 Migration : Part 1 ::

Hello

We cover the migration in two parts

1) Database Migration
2) Custom Code Migration to VC 2013.

Part 1 :: Database Migration

1) Go to your old SharePoint database, then copy the WSS_Content database.

2) Verify source server properties.

3) Set your destination SQL Server.

4) Select the Transfer Method, use the SQL Management Object method if you want a live migration.

5) Select a database to copy, you will only need WSS_Content.

6) Configure the properties of Destination Database.

7) Select Objects, you only need Logins here.

8) Saving the package created.

9) Run immediately, you can also schedule them.

10) Look at the summary.

11) Wait while it's performing the copy

12) Or Just Backup and Restore Database will also work for all above 10 steps.

13) Once done, go back to SharePoint 2013 Central Administration and set your SharePoint instance to use the copied WSS_Content database.

14) Go to Application Management -> Manage Web Applications. -> Create a new Web Application

15) Now you need to set that new web application to use the copied WSS_Content database, you need to do this in SharePoint 2013 Management Shell

16) Test the database you just copied over by issuing this command:

Test-SPContentDatabase -Name WSS_Content -WebApplication http://YourNewSharepointServer:portNumber
17) Now mount them by issuing this command
Mount-SPContentDatabase -Name WSS_Content -WebApplication http://YourNewSharepointServer:portNumber

18) Now that it's mounted, you need to delete the default WSS_Content database created during the installation process, choose the default WSS_Content instance, if it's a fresh install usually it's the one with zero site collection items.

Sign in as Different User in SharePoint 2013

2014-02-27T10:21:00.000+05:30

Hello,

This is my first post for SharePoint 2013, it is good to be migrate to SharePoint 2013, but some features are missing such as “Sign in as a Different User” menu command.

Many of us are missing this while testing any application,

You can add the menu item back in, but I would suggest only doing this on test or development SharePoint servers. To do this, repeat this edit on all servers in your SharePoint farm

Locate the file \15\TEMPLATE\CONTROLTEMPLATES\Welcome.ascx and open in a text editor.

Add the following element before the existing element with the id of “ID_RequestAccess”:

<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"

Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"

Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>"

MenuGroupId="100"

Sequence="100"

UseShortId="true" />

Save the file.

Now, the menu item shall be displayed:

But it is recommended not to change in any ascx in 14/15 hive.

Convert text files between character sets

2013-10-31T12:06:00.002+05:30

Hello Friends,

I was trying to upload the Bulk data from Flat text file to SQL Table, but it was required to have character sets as ANCII.. but when we manually change some data in text file it is keeping first column first value as null..

So after spending time on it, I found that file has to be converted to ANCII format..

Here is the commands for same..

On Windows with Powershell:

PS C:\> gc -en utf8 'in.txt' | Out-File -en ascii 'out.txt'

(No ISO-8859-15 support though; it says that supported charsets are unicode, utf7, utf8, utf32, ascii, bigendianunicode, default, and oem.)

CsCvt - Kalytta's Character Set Converter (http://www.cscvt.de) is another great command line based conversion tool for Windows.

Enjoy...

Display Item Attachments in SharePoint List View

2013-09-19T14:27:00.000+05:30

It is very easy to display list item attachments
in List View and also manipulate the display of attachment, like if attachment is
image, we can display image not just a link.

1. Open List View in SharePoint Desinger

2. Add new column titled "Attachments".

3. Select TD tag of New column.

4. Replace selected code with below code.


 <td id="ItemAttchment" class="ms-vb">
          <xsl:element name="SharePoint:AttachmentsField">
          <xsl:attribute name="runat">server</xsl:attribute>
          <xsl:attribute name="FieldName">Attachments</xsl:attribute>
          <xsl:attribute name="ControlMode">Display</xsl:attribute>
          <xsl:attribute name="Visible">true</xsl:attribute>
          <xsl:attribute name="ItemId">
          <xsl:value-of select="@ID"/>
          </xsl:attribute>
          </xsl:element>
</td>

and also add

<xsl:value-of select="$thisNode/@ID"></xsl:value-of>

5. View with Attachments

Enjoy !!!

SharePoint Bulk Delete List Items Programatically

2013-08-07T14:44:00.002+05:30

While working on a custom SharePoint solution, I had a requirement to delete multiple list items one time rather than deleting one by one.

Example: Delete only the items from a list which doesn't have value for a custom column.

When i think of the solution i couldn't make new SPListItemCollection object out of the items which needs to be deleted, which is possible in regular c# application development.
However in SharePoint we can do the batch delete of list items using CAML script.
The CAML script needs to be generated for the items which needs to be deleted as below.

Get the list items:
SPListItemCollection items = spList.Items;

Generate CAML Script:

StringBuilder methodBuilder = new StringBuilder();
string batchFormat = "" +
"{0}"; //{0}-methodFormat
string methodFormat = "" + //{0}-Unique Value for each Item
"{1}" + //{1}-List Guid
"{2}" + //{2}-List ItemID
"Delete" +
"";

// Build the CAML delete command script.
foreach (SPListItem item in items)
{
    //get the custom column value
    string customColumnValue = string.Empty;
    if (null != item["CustomColumnName"])
        customColumnValue = item["CustomColumnName"].ToString();

    //check whether custom column is empty
    if (string.IsNullOrEmpty(customColumnValue))
    {
        methodBuilder.AppendFormat(methodFormat, item.ID, item.ParentList.ID, item.ID);
    }
}

//batch delete script.
string batchDeleteScript = string.Format(batchFormat, methodBuilder.ToString());

Execute CAML Script:

spWeb.ProcessBatchData(batchDeleteScript);

SharePoint Bulk Update List Items Programatically

2013-08-07T14:38:00.004+05:30

While working on a custom SharePoint solution, I had a requirement to update multiple list items one time rather than updating one by one.

Example: Update only the items in a list which doesn't have value for a custom column (update with some value).

When i think of the solution i couldn't make new SPListItemCollection object out of the items which needs to be updated, which is possible in regular c# application development.

However in SharePoint we can do the batch update of list items using CAML script.
The CAML script needs to be generated for the items which needs to be updated as below.

Get the list items:

SPListItemCollection items = spList.Items;
Generate CAML Script:

StringBuilder methodBuilder = new StringBuilder();
string batchFormat = "" +
"{0}"; //{0}-methodFormat
string methodFormat = "" + //{0}-Unique Value for each Item
"{1}" + //{1}-List Guid
"Save" +
"{2}" + //{2}-List ItemID
"{4}" + //{3}-Column Name, {4}-Column Value
"";

// Build the CAML update command script.
foreach (SPListItem item in items)
{
    //get the custom column value
    string customColumnValue = string.Empty;
    if (null != item["CustomColumnName"])
        customColumnValue = item["CustomColumnName"].ToString();

    //check whether custom column is empty
    if (string.IsNullOrEmpty(customColumnValue))
    {
        methodBuilder.AppendFormat(methodFormat, item.ID, item.ParentList.ID, item.ID, "CustomColumnName", "New Updated Value");
    }
}

//batch update script.
string batchUpdateScript = string.Format(batchFormat, methodBuilder.ToString());

Execute CAML Script:

spWeb.ProcessBatchData(batchUpdateScript);

Orphan Event Receiver

2013-07-11T12:23:00.000+05:30

I was wokring on to remove 'Orphan Event Receiver' without affecting the exitsting application, I research a lot and found one workaround,

Steps to Remove orphan event receiver,

1) Use SharePoint Manager Utility, to check is there any event receiver present or not, if present remove the event receiver using SharePoint Manager Utility

2) Execute following power shell script,

function Remove-SPFeatureFromContentDB($ContentDb, $FeatureId, [switch]$ReportOnly)
{
    $db = Get-SPDatabase | where { $_.Name -eq $ContentDb }
    [bool]$report = $false
    if ($ReportOnly) { $report = $true }

    $db.Sites | ForEach-Object {

        Remove-SPFeature -obj $_ -objName "site collection" -featId $FeatureId -report $report

        $_ | Get-SPWeb -Limit all | ForEach-Object {

            Remove-SPFeature -obj $_ -objName "site" -featId $FeatureId -report $report
        }
    }
}

function Remove-SPFeature($obj, $objName, $featId, [bool]$report)
{
    $feature = $obj.Features[$featId]
    if ($feature -ne $null) {
        if ($report) {
            write-host "Feature found in" $objName ":" $obj.Url -foregroundcolor Red
        }
        else
        {
            try {
                $obj.Features.Remove($feature.DefinitionId, $true)
                write-host "Feature successfully removed from" $objName ":" $obj.Url -foregroundcolor Red
            }
            catch {
                write-host "There has been an error trying to remove the feature:" $_
            }
        }
    }
    else {
        #write-host "Feature ID specified does not exist in" $objName ":" $obj.Url
    }
}

Remove-SPFeatureFromContentDB -ContentDB "ContentDBName" -FeatureId "FeatureID" –ReportOnly

This Command will report the Feature is present in DB or not.

Remove-SPFeatureFromContentDB-ContentDB "ContentDBName"-FeatureId "FeatureID"

This command will remove the Feature from DB

After that check the featuer still existing using 'SharePoint Manager' and if still exisit delete using 'SharePoint Manager'

And reinstall the fearture...

Thanks... if you found any better solution please post.