Posts tagged cheap europe sharepoint 2013 hosting

SharePoint 2013 Hosting :: How To Remove Empty Folders In Sharepoint Library Using PnP Powershell

Jun 21st

Posted by Peter in European SharePoint 2013 Hosting

A SharePoint library is a location on a site where you can upload, create, update, and collaborate on files with team members. To remove an empty folder from the library is difficult since we need to go to each and every library and identify whether it is empty or not. Then, we have to remove it from the library. To automate this process, I used Powershell scripting because it is easy to parse through each and every library using PNP library. So it is easy to identify and remove the empty folders in SharePoint library

Prerequisite

Before you begin utilizing PowerShell to oversee SharePoint Online, ensure that the SharePoint Online Management Shell is installed. You can install the SharePoint Online Management Shell by downloading and running the SharePoint Online Management Shell. You only need to do this once for each computer from which you are running SharePoint Online PowerShell commands.

Connect to Site

Connect to SharePoint site using Connect-PnPOnline cmdlet. The required parameters are,

-Url

The SharePoint site URL (Eg: https://hubflysoft.sharepoint.com/sites/Hubfly)

The following code snippet helps to connect SharePoint sites.

$siteurl="https://<tenant-name>.sharepoint.com"    
   
Connect-PnPOnline -Url $siteurl

$siteurl="https://<tenant-name>.sharepoint.com"

Connect-PnPOnline -Url $siteurl

Get Web Instance using Get-PnPWeb

$web = Get-PnPWeb

The Get-PnPWeb cmdlet actually has its own Recurse option, and you could use that if you want to rather than doing your own recursion.

Get User Context using Get-PnPContext

$context = Get-PnPContext

The Get-PnPContext returns a Client Side Object Model context. This command is very handy and it returns the current context. You might need context because it might be the case you need to save the current context. By switching between two sites you need this.

Get folders from the library using Get-PnPFolder

$folder = Get-PnPFolder -RelativeUrl "Shared Documents"

1	$folder = Get-PnPFolder -RelativeUrl "Shared Documents"

The Get-PnPFolder returns the folder called ‘Shared Documents’ which is located in the root of the current web.

Get all subfolders and remove empty folders

Using the context we need to load all files, folders, and Parent folder like below code snippet

$files = $folder.Files
$context.Load($folder.Files)
$context.Load($folder.Folders)
$context.Load($folder.ParentFolder)
$context.ExecuteQuery()

We can find the folder is empty by the following conditions,

Check if the files count is equal to zero
Check if the folders count is equal to zero

And remove the empty folders using below PS script

Remove - PnPFolder  
if ($folder.Files.Count - eq 0 - and $folder.Folders.Count - eq 0 - and(($folder.Name - notmatch 'Document') - and($folder.Name - notmatch $libraryName)))  
{  
    $path = $folder.ParentFolder.ServerRelativeUrl.Substring($web.ServerRelativeUrl.Length)  
    Write - Host "Removing folder "  
    $folder.ServerRelativeUrl.Substring($web.ServerRelativeUrl.Length)  
    Remove - PnPFolder - Folder $path - Name $folder.Name - Recycle - Force  
    $folders_list += $folder.Name + ", " + $folder.ServerRelativeUrl  
}  
Write - Host "Searching for empty folders. Please wait..."  
$folders_list = GetAllSubFolders $folder $context  
Write - Host $libraryName 'Completed'

Remove - PnPFolder

if ($folder.Files.Count - eq 0 - and $folder.Folders.Count - eq 0 - and(($folder.Name - notmatch 'Document') - and($folder.Name - notmatch $libraryName)))

{

$path = $folder.ParentFolder.ServerRelativeUrl.Substring($web.ServerRelativeUrl.Length)

Write - Host "Removing folder "

$folder.ServerRelativeUrl.Substring($web.ServerRelativeUrl.Length)

Remove - PnPFolder - Folder $path - Name $folder.Name - Recycle - Force

$folders_list += $folder.Name + ", " + $folder.ServerRelativeUrl

}

Write - Host "Searching for empty folders. Please wait..."

$folders_list = GetAllSubFolders $folder $context

Write - Host $libraryName 'Completed'

I hope you learned how to remove empty folders and files in the SharePoint library programmatically using PnP PowerShell scripting. The operations mentioned above are tested on SharePoint Online environment. Feel free to leave a comment below, if you need any assistance.

SharePoint 2013 Hosting :: How to Configure existing URL located in the Top Navigation Bar?

Jun 7th

Posted by Peter in European SharePoint 2013 Hosting

No comments

In this tutorial, I will explain you how to to Configure existing URL located in the Top Navigation Bar as the referenced site URL has changed in SharePoint 2013.

The top link bar helps users of your site navigate to alternative sites within the site collection by displaying a row of tabs at the top of pages in the site. the top link bar is additionally referred to as global navigation, as a result of it can be the same across all of the web sites in a site collection. However, subsites can be configured to not show in the top link bar of the parent site. the options offered to you for configuring your top link bar will vary depending on whether or not the publishing features are enabled for your site collection.

I want to change this hyperlink to all sites inside the Web App: more than 1800 Site Collection. And I use the following code:

$Webs = Get-SPSite -WebApplication "http://SharePoint.Contoso.com"  -limit ALL | Get-SPWeb -limit all

Foreach($Web in $Webs)
{
$TN = $Web.Navigation.TopNavigationBar | Where-Object {$_.Title -eq "Landing Page & Wiki"}
if ($TN.url -like "http://hostforlife.eu*")
{
   write-host "Updating $($Web.url)"
  “Updating $($Web.url), $($TN.Url)” | out-file D:\temp\LandingPageUpdate.csv   -append
    $TN.Url = "http://NewSharePoint.Contoso.com/Pages/LandingPageWikiDefault.aspx"
    $TN.update()
}
}
#----------------------------------------------------------------------

$Webs = Get-SPSite -WebApplication "http://SharePoint.Contoso.com" -limit ALL | Get-SPWeb -limit all

Foreach($Web in $Webs)

{

$TN = $Web.Navigation.TopNavigationBar | Where-Object {$_.Title -eq "Landing Page & Wiki"}

if ($TN.url -like "http://hostforlife.eu*")

{

write-host "Updating $($Web.url)"

“Updating $($Web.url), $($TN.Url)” | out-file D:\temp\LandingPageUpdate.csv -append

$TN.Url = "http://NewSharePoint.Contoso.com/Pages/LandingPageWikiDefault.aspx"

$TN.update()

}

#----------------------------------------------------------------------

Also, in parallel, I had to modify the template used to create the new sites into this Web App. Doing this will avoid having to run this script periodically to correct the changes.

SharePoint 2013 Hosting Recommendation

HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options

SharePoint 2013 Hosting :: How to Configure existing URL located in the Top Navigation Bar?

May 31st

Posted by Peter in European SharePoint 2013 Hosting

No comments

In this tutorial, I will explain you how to to Configure existing URL located in the Top Navigation Bar as the referenced site URL has changed in SharePoint 2013.

I want to change this hyperlink to all sites inside the Web App: more than 1800 Site Collection. And I use the following code:

$Webs = Get-SPSite -WebApplication "http://SharePoint.Contoso.com"  -limit ALL | Get-SPWeb -limit all

Foreach($Web in $Webs)
{
$TN = $Web.Navigation.TopNavigationBar | Where-Object {$_.Title -eq "Landing Page & Wiki"}
if ($TN.url -like "http://hostforlife.eu*")
{
   write-host "Updating $($Web.url)"
  “Updating $($Web.url), $($TN.Url)” | out-file D:\temp\LandingPageUpdate.csv   -append
    $TN.Url = "http://NewSharePoint.Contoso.com/Pages/LandingPageWikiDefault.aspx"
    $TN.update()
}
}
#----------------------------------------------------------------------

$Webs = Get-SPSite -WebApplication "http://SharePoint.Contoso.com" -limit ALL | Get-SPWeb -limit all

Foreach($Web in $Webs)

{

$TN = $Web.Navigation.TopNavigationBar | Where-Object {$_.Title -eq "Landing Page & Wiki"}

if ($TN.url -like "http://hostforlife.eu*")

{

write-host "Updating $($Web.url)"

“Updating $($Web.url), $($TN.Url)” | out-file D:\temp\LandingPageUpdate.csv -append

$TN.Url = "http://NewSharePoint.Contoso.com/Pages/LandingPageWikiDefault.aspx"

$TN.update()

}

#----------------------------------------------------------------------

Also, in parallel, I had to modify the template used to create the new sites into this Web App. Doing this will avoid having to run this script periodically to correct the changes.

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Uploading Large Files In SharePoint Online?

Feb 23rd

Posted by Peter in European SharePoint 2013 Hosting

No comments

By default, client-side scripting has some restrictions while posting large sizes of data in different browsers.

While using Angular HTTP post to upload a file, I’m facing an issue — more than a 100MB file upload breaks in some of the browsers like Chrome, Firefox, etc.

Now, I’m using file chunking to post the file as split chunks by SharePoint REST API.
Angular + SharePoint Large file upload

Follow the below-listed steps to upload the large files.

Step1
Create a “File upload” component template like below.

   <input class="upload form-control" id="DocUploader" placeholder="Upload file" type="file" (change)="UploadFile($event)">

1	<input class="upload form-control" id="DocUploader" placeholder="Upload file" type="file" (change)="UploadFile($event)">

Step2
Below is the TypeScript code for the file upload component.

    import {  
        Component  
    } from '@angular/core';  
    @Component({  
        selector: 'app-fileupload',  
        templateUrl: './fileupload.component.html',  
    })  
    export class FileUploadComponent {  
        UploadFile(event: any) {  
            let fileList: FileList = event.target.files;  
            if (fileList.length != 0) {  
                this.fileUploadService.fileUpload(fileList[0].name, "Documents", fileList[0].name).then(addFileToFolder => {  
                    console.log("File Uploaded Successfully");  
                }).catch(addFileToFolderError => {  
                    console.log(addFileToFolderError);  
                });  
            }  
        }  
    }

import {

Component

} from '@angular/core';

@Component({

selector: 'app-fileupload',

templateUrl: './fileupload.component.html',

})

export class FileUploadComponent {

UploadFile(event: any) {

let fileList: FileList = event.target.files;

if (fileList.length != 0) {

this.fileUploadService.fileUpload(fileList[0].name, "Documents", fileList[0].name).then(addFileToFolder => {

console.log("File Uploaded Successfully");

}).catch(addFileToFolderError => {

console.log(addFileToFolderError);

});

}

Step3
The important part of chunk based file upload implementation is Angular service. FileUploadService code is mentioned below.

    import {  
        Injectable,  
        EventEmitter  
    } from '@angular/core';  
    declare  
    var _spPageContextInfo: any;  
    declare  
    var SP: any;  
    @Injectable()  
    export class FileUploadService {  
        public siteUrl: string = _spPageContextInfo.webAbsoluteUrl;  
        public siteRelativeUrl: string = _spPageContextInfo.webServerRelativeUrl != "/" ? _spPageContextInfo.webServerRelativeUrl : "";  
        public fileUpload(file: any, documentLibrary: string, fileName: string) {  
            return new Promise((resolve, reject) => {  
                this.createDummyFile(fileName, documentLibrary).then(result => {  
                    let fr = new FileReader();  
                    let offset = 0;  
                    // the total file size in bytes...  
                    let total = file.size;  
                    // 1MB Chunks as represented in bytes (if the file is less than a MB, seperate it into two chunks of 80% and 20% the size)...  
                    let length = parseInt(1000000) > total ? Math.round(total * 0.8) : parseInt(1000000);  
                    let chunks = [];  
                    //reads in the file using the fileReader HTML5 API (as an ArrayBuffer) - readAsBinaryString is not available in IE!  
                    fr.readAsArrayBuffer(file);  
                    fr.onload = (evt: any) => {  
                        while (offset < total) {  
                            //if we are dealing with the final chunk, we need to know...  
                            if (offset + length > total) {  
                                length = total - offset;  
                            }  
                            //work out the chunks that need to be processed and the associated REST method (start, continue or finish)  
                            chunks.push({  
                                offset,  
                                length,  
                                method: this.getUploadMethod(offset, length, total)  
                            });  
                            offset += length;  
                        }  
                        //each chunk is worth a percentage of the total size of the file...  
                        const chunkPercentage = (total / chunks.length) / total * 100;  
                        if (chunks.length > 0) {  
                            //the unique guid identifier to be used throughout the upload session  
                            const id = this.guid();  
                            //Start the upload - send the data to S  
                            this.uploadFile(evt.target.result, id, documentLibrary, fileName, chunks, 0, 0, chunkPercentage, resolve, reject);  
                        }  
                    };  
                })  
            });  
        }  
        createDummyFile(fileName, libraryName) {  
            return new Promise((resolve, reject) => {  
                // Construct the endpoint - The GetList method is available for SharePoint Online only.  
                var serverRelativeUrlToFolder = "decodedurl='" + this.siteRelativeUrl + "/" + libraryName + "'";  
                var endpoint = this.siteUrl + "/_api/Web/GetFolderByServerRelativePath(" + serverRelativeUrlToFolder + ")/files" + "/add(overwrite=true, url='" + fileName + "')"  
                const headers = {  
                    "accept": "application/json;odata=verbose"  
                };  
                this.executeAsync(endpoint, this.convertDataBinaryString(2), headers).then(file => resolve(true)).catch(err => reject(err));  
            });  
        }  
        // Base64 - this method converts the blob arrayBuffer into a binary string to send in the REST request  
        convertDataBinaryString(data) {  
            let fileData = '';  
            let byteArray = new Uint8Array(data);  
            for (var i = 0; i < byteArray.byteLength; i++) {  
                fileData += String.fromCharCode(byteArray[i]);  
            }  
            return fileData;  
        }  
        executeAsync(endPointUrl, data, requestHeaders) {  
            return new Promise((resolve, reject) => {  
                // using a utils function we would get the APP WEB url value and pass it into the constructor...  
                let executor = new SP.RequestExecutor(this.siteUrl);  
                // Send the request.  
                executor.executeAsync({  
                    url: endPointUrl,  
                    method: "POST",  
                    body: data,  
                    binaryStringRequestBody: true,  
                    headers: requestHeaders,  
                    success: offset => resolve(offset),  
                    error: err => reject(err.responseText)  
                });  
            });  
        }  
        //this method sets up the REST request and then sends the chunk of file along with the unique indentifier (uploadId)  
        uploadFileChunk(id, libraryPath, fileName, chunk, data, byteOffset) {  
            return new Promise((resolve, reject) => {  
                let offset = chunk.offset === 0 ? '' : ',fileOffset=' + chunk.offset;  
                //parameterising the components of this endpoint avoids the max url length problem in SP (Querystring parameters are not included in this length)  
                let endpoint = this.siteUrl + "/_api/web/getfilebyserverrelativeurl('" + this.siteRelativeUrl + "/" + libraryPath + "/" + fileName + "')/" + chunk.method + "(uploadId=guid'" + id + "'" + offset + ")";  
                const headers = {  
                    "Accept": "application/json; odata=verbose",  
                    "Content-Type": "application/octet-stream"  
                };  
                this.executeAsync(endpoint, data, headers).then(offset => resolve(offset)).catch(err => reject(err));  
            });  
        }  
        //the primary method that resursively calls to get the chunks and upload them to the library (to make the complete file)  
        uploadFile(result, id, libraryPath, fileName, chunks, index, byteOffset, chunkPercentage, resolve, reject) {  
            //we slice the file blob into the chunk we need to send in this request (byteOffset tells us the start position)  
            const data = this.convertFileToBlobChunks(result, byteOffset, chunks[index]);  
            //upload the chunk to the server using REST, using the unique upload guid as the identifier  
            this.uploadFileChunk(id, libraryPath, fileName, chunks[index], data, byteOffset).then(value => {  
                const isFinished = index === chunks.length - 1;  
                index += 1;  
                const percentageComplete = isFinished ? 100 : Math.round((index * chunkPercentage));  
                //More chunks to process before the file is finished, continue  
                if (index < chunks.length) {  
                    this.uploadFile(result, id, libraryPath, fileName, chunks, index, byteOffset, chunkPercentage, resolve, reject);  
                } else {  
                    resolve(value);  
                }  
            }).catch(err => {  
                console.log('Error in uploadFileChunk! ' + err);  
                reject(err);  
            });  
        }  
        //Helper method - depending on what chunk of data we are dealing with, we need to use the correct REST method...  
        getUploadMethod(offset, length, total) {  
            if (offset + length + 1 > total) {  
                return 'finishupload';  
            } else if (offset === 0) {  
                return 'startupload';  
            } else if (offset < total) {  
                return 'continueupload';  
            }  
            return null;  
        }  
        //this method slices the blob array buffer to the appropriate chunk and then calls off to get the BinaryString of that chunk  
        convertFileToBlobChunks(result, byteOffset, chunkInfo) {  
            let arrayBuffer = result.slice(chunkInfo.offset, chunkInfo.offset + chunkInfo.length);  
            return this.convertDataBinaryString(arrayBuffer);  
        }  
        guid() {  
            function s4() {  
                return Math.floor((1 + Math.random()) * 0x10000).toString(16).substring(1);  
            }  
            return s4() + s4() + '-' + s4() + '-' + s4() + '-' + s4() + '-' + s4() + s4() + s4();  
        }  
    }

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

import {

Injectable,

EventEmitter

} from '@angular/core';

declare

var _spPageContextInfo: any;

declare

var SP: any;

@Injectable()

export class FileUploadService {

public siteUrl: string = _spPageContextInfo.webAbsoluteUrl;

public siteRelativeUrl: string = _spPageContextInfo.webServerRelativeUrl != "/" ? _spPageContextInfo.webServerRelativeUrl : "";

public fileUpload(file: any, documentLibrary: string, fileName: string) {

return new Promise((resolve, reject) => {

this.createDummyFile(fileName, documentLibrary).then(result => {

let fr = new FileReader();

let offset = 0;

// the total file size in bytes...

let total = file.size;

// 1MB Chunks as represented in bytes (if the file is less than a MB, seperate it into two chunks of 80% and 20% the size)...

let length = parseInt(1000000) > total ? Math.round(total * 0.8) : parseInt(1000000);

let chunks = [];

//reads in the file using the fileReader HTML5 API (as an ArrayBuffer) - readAsBinaryString is not available in IE!

fr.readAsArrayBuffer(file);

fr.onload = (evt: any) => {

while (offset < total) {

//if we are dealing with the final chunk, we need to know...

if (offset + length > total) {

length = total - offset;

}

//work out the chunks that need to be processed and the associated REST method (start, continue or finish)

chunks.push({

offset,

length,

method: this.getUploadMethod(offset, length, total)

});

offset += length;

}

//each chunk is worth a percentage of the total size of the file...

const chunkPercentage = (total / chunks.length) / total * 100;

if (chunks.length > 0) {

//the unique guid identifier to be used throughout the upload session

const id = this.guid();

//Start the upload - send the data to S

this.uploadFile(evt.target.result, id, documentLibrary, fileName, chunks, 0, 0, chunkPercentage, resolve, reject);

}

};

})

});

}

createDummyFile(fileName, libraryName) {

return new Promise((resolve, reject) => {

// Construct the endpoint - The GetList method is available for SharePoint Online only.

var serverRelativeUrlToFolder = "decodedurl='" + this.siteRelativeUrl + "/" + libraryName + "'";

var endpoint = this.siteUrl + "/_api/Web/GetFolderByServerRelativePath(" + serverRelativeUrlToFolder + ")/files" + "/add(overwrite=true, url='" + fileName + "')"

const headers = {

"accept": "application/json;odata=verbose"

};

this.executeAsync(endpoint, this.convertDataBinaryString(2), headers).then(file => resolve(true)).catch(err => reject(err));

});

}

// Base64 - this method converts the blob arrayBuffer into a binary string to send in the REST request

convertDataBinaryString(data) {

let fileData = '';

let byteArray = new Uint8Array(data);

for (var i = 0; i < byteArray.byteLength; i++) {

fileData += String.fromCharCode(byteArray[i]);

}

return fileData;

}

executeAsync(endPointUrl, data, requestHeaders) {

return new Promise((resolve, reject) => {

// using a utils function we would get the APP WEB url value and pass it into the constructor...

let executor = new SP.RequestExecutor(this.siteUrl);

// Send the request.

executor.executeAsync({

url: endPointUrl,

method: "POST",

body: data,

binaryStringRequestBody: true,

headers: requestHeaders,

success: offset => resolve(offset),

error: err => reject(err.responseText)

});

}

//this method sets up the REST request and then sends the chunk of file along with the unique indentifier (uploadId)

uploadFileChunk(id, libraryPath, fileName, chunk, data, byteOffset) {

return new Promise((resolve, reject) => {

let offset = chunk.offset === 0 ? '' : ',fileOffset=' + chunk.offset;

//parameterising the components of this endpoint avoids the max url length problem in SP (Querystring parameters are not included in this length)

let endpoint = this.siteUrl + "/_api/web/getfilebyserverrelativeurl('" + this.siteRelativeUrl + "/" + libraryPath + "/" + fileName + "')/" + chunk.method + "(uploadId=guid'" + id + "'" + offset + ")";

const headers = {

"Accept": "application/json; odata=verbose",

"Content-Type": "application/octet-stream"

};

this.executeAsync(endpoint, data, headers).then(offset => resolve(offset)).catch(err => reject(err));

});

}

//the primary method that resursively calls to get the chunks and upload them to the library (to make the complete file)

uploadFile(result, id, libraryPath, fileName, chunks, index, byteOffset, chunkPercentage, resolve, reject) {

//we slice the file blob into the chunk we need to send in this request (byteOffset tells us the start position)

const data = this.convertFileToBlobChunks(result, byteOffset, chunks[index]);

//upload the chunk to the server using REST, using the unique upload guid as the identifier

this.uploadFileChunk(id, libraryPath, fileName, chunks[index], data, byteOffset).then(value => {

const isFinished = index === chunks.length - 1;

index += 1;

const percentageComplete = isFinished ? 100 : Math.round((index * chunkPercentage));

//More chunks to process before the file is finished, continue

if (index < chunks.length) {

this.uploadFile(result, id, libraryPath, fileName, chunks, index, byteOffset, chunkPercentage, resolve, reject);

} else {

resolve(value);

}

}).catch(err => {

console.log('Error in uploadFileChunk! ' + err);

reject(err);

});

}

//Helper method - depending on what chunk of data we are dealing with, we need to use the correct REST method...

getUploadMethod(offset, length, total) {

if (offset + length + 1 > total) {

return 'finishupload';

} else if (offset === 0) {

return 'startupload';

} else if (offset < total) {

return 'continueupload';

}

return null;

}

//this method slices the blob array buffer to the appropriate chunk and then calls off to get the BinaryString of that chunk

convertFileToBlobChunks(result, byteOffset, chunkInfo) {

let arrayBuffer = result.slice(chunkInfo.offset, chunkInfo.offset + chunkInfo.length);

return this.convertDataBinaryString(arrayBuffer);

}

guid() {

function s4() {

return Math.floor((1 + Math.random()) * 0x10000).toString(16).substring(1);

}

return s4() + s4() + '-' + s4() + '-' + s4() + '-' + s4() + '-' + s4() + s4() + s4();

}

Step4
We should refer the SP.js and SP.RequestExecutor.js in deployed .aspx (or .html) pages to use default SharePoint service request executor to post file.

Output
Finally, the uploaded file will be available in SharePoint Documents Library.

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Allow Access Requests Email Settings In SharePoint Site Using PnP PowerShell?

Feb 22nd

Posted by Peter in European SharePoint 2013 Hosting

No comments

When new users get access denied to the site, they use the access request feature to inform the Site Owner to grant them the access.

From the Site Permissions -> Access Requests Settings -> Allow Access Requests feature has the option for setting the email. So, whenever a user requests access to the site/ file/folder, an email will be sent to notify the user to provide them the access.

If we remove the email from the “Allow Access Requests” settings, this feature gets disabled and the new user won’t notify the user when they need access.

To enable this email setting and send the notification to the owner, use the below PnP PowerShell snippets . $cred = Get-Credential

    Connect-PnPOnline -Url https://<tenant>.sharepoint.com -Credential $cred    
    Set-PnPRequestAccessEmails -Emails ktskumar@<tenant>.onmicrosoft.com

1 2	Connect-PnPOnline -Url https://<tenant>.sharepoint.com -Credential $cred Set-PnPRequestAccessEmails -Emails ktskumar@<tenant>.onmicrosoft.com

To add multiple emails to the settings, use the below cmdlet.

    Set-PnPRequestAccessEmails -Emails @( ktskumar@<tenant>.onmicrosoft.com; user1@<tenant>.onmicrosoft.com )

1	Set-PnPRequestAccessEmails -Emails @( ktskumar@<tenant>.onmicrosoft.com; user1@<tenant>.onmicrosoft.com )

The below PnP Powershell snippet is used to get the emails associated to allow access requests settings. $cred = Get-Credential

    Connect-PnPOnline -Url https://<tenant>.sharepoint.com -Credential $cred      
    Get-PnPRequestAccessEmails

1 2	Connect-PnPOnline -Url https://<tenant>.sharepoint.com -Credential $cred Get-PnPRequestAccessEmails

SharePoint 2013 Hosting – HostForLIFE.eu :: How To Manage Policy And Procedure Documents In SharePoint?

Feb 15th

Posted by Peter in European SharePoint 2013 Hosting

No comments

Nowadays, SharePoint is the most popular and productive document management system. It offers users ample opportunities, and it’s the best solution to manage policies and procedures.

Store Policies in Document Libraries (not on the file system)

SharePoint document libraries have numerous benefits for storing policies.

customizable views
ability to filter and sort
addition of new columns / metadata
ability to trigger workflows
it allows documents to be managed and versioned

NOTE

A SharePoint workflow is made up of automated steps where a document gets approved by one or more people in the organization.

Store multiple versions of a Policy or Procedure and SharePoint Alerts

SharePoint document libraries can be configured to turn on “version management”. It allows the users to find the previous version of a document without latest changes or compare changes with the most current copy.

Also, users can check for new updates by SharePoint Alerts. It allows users to get notifications about any changes in policies or others event in SharePoint,

SharePoint Workspace

This application allows synchronizing the assets (such as policies) between a desktop and SharePoint. Users work with local copies of documents where there is no connection to SharePoint without browser access.

Next time a user connects to SharePoint, the Workspace synchronizes the assets again between a desktop and SharePoint.

Security model SharePoint

The security model allows users to control who can view, edit, or delete something. Moreover, this model grants permissions to the groups and allocates them among users.

Document ID Service

The Document ID Service in SharePoint has two major benefits.

Users can identify each document in a site collection with a unique id of a document. It allows you to reduce the risk of ambiguity where two documents are named the same or similarly.
Users have access to the document via a URL without location-specific information. It allows the link to remain intact despite the document moves.

Posts tagged cheap europe sharepoint 2013 hosting

SharePoint 2013 Hosting :: How To Remove Empty Folders In Sharepoint Library Using PnP Powershell

SharePoint 2013 Hosting :: How to Configure existing URL located in the Top Navigation Bar?

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting :: How to Configure existing URL located in the Top Navigation Bar?

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Uploading Large Files In SharePoint Online?

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Allow Access Requests Email Settings In SharePoint Site Using PnP PowerShell?

SharePoint 2013 Hosting – HostForLIFE.eu :: How To Manage Policy And Procedure Documents In SharePoint?

BLOGROLL

Featured On

Posts tagged cheap europe sharepoint 2013 hosting

SharePoint 2013 Hosting :: How To Remove Empty Folders In Sharepoint Library Using PnP Powershell

SharePoint 2013 Hosting :: How to Configure existing URL located in the Top Navigation Bar?

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting :: How to Configure existing URL located in the Top Navigation Bar?

SharePoint 2013 Hosting Recommendation

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Uploading Large Files In SharePoint Online?

SharePoint 2013 Hosting – HostForLIFE.eu :: How to Allow Access Requests Email Settings In SharePoint Site Using PnP PowerShell?

SharePoint 2013 Hosting – HostForLIFE.eu :: How To Manage Policy And Procedure Documents In SharePoint?

BLOGROLL

Featured On

Tags