One year later and it’s time to review past predictions and set out the new ones. It was exactly 1 year ago that I wrote up my predictions for 2015. I’ll let you determine how I did, but I wrote up some of my thoughts. I’m not looking at those as I write my new [&hellip
The post SharePoint 2016 and Office 365 Predictions! appeared first on CollabShow.
Comments are in the script...
# Location of CSOM assemblies
# (from OfficeDev repo on GitHub: http://ift.tt/1MFijPt)
Set-Location "C:\Users\pchoquette\Source\Repos\PnP-Sites-Core\Assemblies\16"
# Generally required for any CSOM operations
Add-Type -Path (Resolve-Path "Microsoft.SharePoint.Client.dll")
Add-Type -Path (Resolve-Path "Microsoft.SharePoint.Client.Runtime.dll")
# Required for CSOM operations involving Document Sets
Add-Type -Path (Resolve-Path "Microsoft.SharePoint.Client.DocumentManagement.dll")
# Modify the details in this section to correspond to your Web on SPO
$ctx = New-Object Microsoft.SharePoint.Client.ClientContext("http://ift.tt/22wRMiZ")
$password = Read-Host -Prompt "Enter password" -AsSecureString
$ctx.Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials("pchoquette@starcrossed.ninja", $password)
# Modify this line with the title of your Document Library
$list = $ctx.Web.Lists.GetByTitle("Documents")
$ctx.Load($list)
# You could modify this line if you want the Document Set to go into a subfolder instead
$parentFolder = $list.RootFolder
$listContentTypes = $list.ContentTypes
$ctx.Load($listContentTypes)
# Modify this line with the Content Type ID for your Document Set
# You can get this by going into the Content Type Settings and copying it from the URL of that page
$myContentType = $listContentTypes.GetByID("0x0120D520000535852D838B324FA8890A7BB22EE31F")
$ctx.Load($myContentType)
$ctx.ExecuteQuery()
#Modify this line with the Title for your new Document Set
[Microsoft.SharePoint.Client.DocumentSet.DocumentSet]::Create($ctx, $parentFolder, "Whatever document set name you want goes here", $myContentType.Id)
$ctx.ExecuteQuery()
I know that there are lot of sites and scripts where you can find how to create bunch of folders and set permissions on them via PowerShell. But I was not able to find all in one place. For instance, how to create folder, how to add AD user or group with certain permission level, how to set permission inheritance on some folder etc.
Therefore I wrote couple of functions which will hopefully help you to configure your folder structure, as well as necessary permissions. Best thing is that you can create .csv file and create load of folders and permissions at once.
<#
.Synopsis
This function creates folder in SharePoint list
.DESCRIPTION
This function creates folder in SharePoint list
.EXAMPLE
Create-SPFolder -WebURL http://ift.tt/1MCEB4D -listName Listname -RootFolderURL Listname -FolderName MyFirstFolder -Verbose
#>
function Create-SPFolder
{
[CmdletBinding()]
Param
(
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=0)]
$WebURL,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=1)]
$listName,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=2)]
$RootFolderURL,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=2)]
$FolderName
)
Begin
{
$website = Get-SPWeb $WebURL
$list = $website.Lists[$listname]
}
Process
{
If ($website.GetFolder("$RootFolderURL/$foldername").Exists){
Write-Verbose "SharePoint folder already exists. Skiping...."
}
else{
$folder = $list.AddItem($RootFolderURL, [Microsoft.SharePoint.SPFileSystemObjectType]::Folder, "$folderName")
$folder.Update()
Write-Verbose "SharePoint folder $foldername created on location $RootFolderURL/$foldername"
}
}
End
{
$web.Dispose()
}
}
<#
.Synopsis
This function sets permissions to SharePoint folder
.DESCRIPTION
This function sets permissions to SharePoint folder; it breaks inheritance and add AD user with defined permission level
.EXAMPLE1
Set-SPFolderUserUniquePermission -WebURL http://ift.tt/1MCEB4D -listName Listname -FolderURL "Listname/MyFirstFolderName" -PermissionLevel "Contribute" -User AD\MyAccount -Verbose
.EXAMPLE2
Set-SPFolderUserUniquePermission http://ift.tt/1MCEB4D "Listname" "Listname/MyFirstFolderName" -PermissionLevel "Read" AD\MyAccount -Verbose
.EXAMPLE3
$csv = Import-Csv C:\temp\folderpermission.csv
foreach ($line in $csv){
Set-SPFolderUserUniquePermission -WebURL $line.weburl -listName $line.listName -FolderURL $line.FolderUrl -PermissionLevel $line.PermissionLevel -User $line.ADUser -Verbose
}
#>
function Set-SPFolderUserUniquePermission
{
[CmdletBinding()]
Param
(
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=0)]
$WebURL,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=1)]
$listName,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=2)]
$FolderURL,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=3)]
$PermissionLevel,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=4)]
$User
)
Begin
{
$website = Get-SPWeb $WebURL
$list = $website.Lists | Where-Object{$_.title -eq $listName}
$SPfolder = $list.Folders | Where-Object {$_.url -eq $FolderURL}
$group = $website.SiteUsers[$user];
}
Process
{
$spFolder.BreakRoleInheritance($false);
$roleAssignment = New-Object microsoft.sharepoint.SPRoleAssignment($group)
$roleDefinition = $website.RoleDefinitions[$PermissionLevel]
$roleAssignment.RoleDefinitionBindings.Add($roleDefinition)
$spFolder.RoleAssignments.Add($roleAssignment)
$spFolder.Update()
}
End
{
$website.Dispose()
}
}
<#
.Synopsis
This function set SharePoint folder permission to inherit from parent.
.DESCRIPTION
This function set SharePoint folder permission to inherit from parent.
.EXAMPLE1
Set-SPFolderInheritPermission -WebURL http://ift.tt/1MCEB4D -listName Listname -FolderURL "Listname/MyFirstFolderName"
.EXAMPLE2
$csv = Import-Csv C:\temp\folderpermission.csv
foreach ($line in $csv){
Set-SPFolderInheritPermission -WebURL $line.weburl -listName $line.listName -FolderURL $line.FolderUrl
}
#>
function Set-SPFolderInheritPermission
{
[CmdletBinding()]
Param
(
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=0)]
$WebURL,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=1)]
$listName,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=2)]
$FolderURL
)
Begin
{
$website = Get-SPWeb $WebURL
$list = $website.Lists | Where-Object{$_.title -eq $listName}
$SPfolder = $list.Folders | Where-Object {$_.url -eq $FolderURL}
}
Process
{
$spFolder.ResetRoleInheritance()
$spFolder.Update()
}
End
{
$website.Dispose()
}
}
<#
.Synopsis
This function sets permissions to SharePoint folder
.DESCRIPTION
This function sets permissions to SharePoint folder; it breaks inheritance and add SharePoint group with defined permission level
.EXAMPLE1
Set-SPFolderGroupUniquePermission -WebURL http://ift.tt/1MCEB4D -listName Listname -FolderURL "Listname/MyFirstFolderName" -PermissionLevel "Contribute" -SPGroup "HR" -Verbose
.EXAMPLE2
Set-SPFolderGroupUniquePermission http://ift.tt/1MCEB4D "Listname" "Listname/MyFirstFolderName" -PermissionLevel "Read" "HR" -Verbose
.EXAMPLE3
$csv = Import-Csv C:\temp\folderpermission.csv
foreach ($line in $csv){
Set-SPFolderGroupUniquePermission -WebURL $line.weburl -listName $line.listName -FolderURL $line.FolderUrl -PermissionLevel $line.PermissionLevel -Group $line.SPGroup -Verbose
}
#>
function Set-SPFolderGroupUniquePermission
{
[CmdletBinding()]
Param
(
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=0)]
$WebURL,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=1)]
$listName,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=2)]
$FolderURL,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=3)]
$PermissionLevel,
[Parameter(Mandatory=$true,
ValueFromPipelineByPropertyName=$true,
Position=4)]
$SPGroup
)
Begin
{
$website = Get-SPWeb $WebURL
$list = $website.Lists | Where-Object{$_.title -eq $listName}
$SPfolder = $list.Folders | Where-Object {$_.url -eq $FolderURL}
$group = $website.SiteGroups[$SPGroup];
}
Process
{
$spFolder.BreakRoleInheritance($false);
$roleAssignment = New-Object microsoft.sharepoint.SPRoleAssignment($group)
$roleDefinition = $website.RoleDefinitions[$PermissionLevel]
$roleAssignment.RoleDefinitionBindings.Add($roleDefinition)
$spFolder.RoleAssignments.Add($roleAssignment)
$spFolder.Update()
}
End
{
$website.Dispose()
}
}
$csv = Import-Csv C:\temp\folderpermission.csv
foreach ($line in $csv){
Create-SPFolder -WebURL $line.WebUrl -listName $line.ListName -RootFolderURL $line.RootFolderUrl -FolderName $line.FolderName -Verbose
}
foreach ($line in $csv){
$FolderUrl = $line.RootFolderUrl + '/' + $line.FolderName
Set-SPFolderInheritPermission -WebURL $line.WebUrl -listName $line.ListName -FolderURL $FolderUrl -Verbose
}
foreach ($line in $csv){
$FolderUrl = $line.RootFolderUrl + '/' + $line.FolderName
if($line.SPGroup){
Set-SPFolderGroupUniquePermission -WebURL $line.WebUrl -listName $line.ListName -FolderURL $FolderUrl -PermissionLevel $line.PermissionLevel -SPGroup $line.SPGroup -Verbose
Write-host $line.ADUser $line.SPGroup $FolderUrl
}
elseif($line.ADUser){
Set-SPFolderUserUniquePermission -WebURL $line.WebUrl -listName $line.ListName -FolderURL $FolderUrl -PermissionLevel $line.PermissionLevel -User $line.ADUser -Verbose
Write-host $line.ADUser $line.SPGroup $FolderUrl
}
else{
Write-Verbose "No security groups to configure. Skiping...."
}
}
I have been working with SharePoint/Office 365 for about a year and a half. We did a migration of 1500 office workers and 14,000 students. We migrated 4,5 TB of data to the cloud. The data was almost unchanged from the share the Office workers were used to work with. So no Meta data and no cleaning up the thousands of folders and files. So yes Garbage in = Garbage out. A mistake? I don't know.
We work with offce workers that are limited in their IT skills. They teach. They have had some basic training. Being a school it is maybe not the best way to do this but funds are limited and we did not know better at the time. On the other hand the users did find something in Office 365 that they knew from the shares. A folder structure they recognized.
We know work from there. Some users are starting to see the benefits of meta data. Seeing that it is better to reorganize and start over. But we needed to this in this way to make the users see it.
If we had more time and money we would have had the oppertunity to train our workers better, get them to know and love meta data and content types. What i am trying to say or ask you is that every organisation gets the migrations it deservs with the means they have. The knowledge and benefits will find its way to the users.
Is this a true statement? Feel free to comment!
How to copy all data from ExcelSheet and Paste in SharePoint List.
Create Custom List CustomerDetails3 in SharePoint with four fields (CustomerID,CustomerName,Location,MobNumber)
1. Copy your data from excel sheet (only data no headers)
2. Open CustomerDetails3 List in IE (Chrome don’t support)
3. Click edit
4. Bring cursor at CustomerID with keyUP/KeyDown (don’t use mouse)
5.Press Ctrl+V
6.Stop editing.
Verify data
Done cheers
Our company has just migrated from SharePoint 2013 to SharePoint Online, so I am wrestling with modifying all my Powershell scripts. One such scenario is around the Small Search Box. By default it searches the current site only, although you can can change the scope, and we have a search Centre site. In practice, users just type their query into the search box.
You can change the search configuration under 'Site Settings -> Search Settings' to add links, so I add in a link to the Search Centre ('Everything'), and 'this site'. This is a per-site setting, not per-site collection, so it is a pain to do manually.
So here is the scenario:
Sounds simple? not until you try and do it. I pieced this together from a number of different posts, as I got stuck on different stages. I assume you know something about CSOM , and connecting to your tenant via Powershell.
Lets load the existing nodes:
write-Host "Setting Search Urls for: " $web.Title " Url: " $web.Url
# Set the Title and Url of the two nodes we want to add
$nodeEverythingTitle = "Everything"
$nodeEverythingUrl = "/search/Pages/results.aspx"
$nodeThisSiteTitle = "this site"
$nodeThisSiteUrl = "/_layouts/15/osssearchresults.aspx"
$addEverything = $true
$addThisSite = $true
#Get the list of Search Navigation Nodes
$nav = $web.Navigation
$clientContext.Load($nav)
$clientContext.ExecuteQuery()
$srchNav = $nav.GetNodeById(1040);
[Microsoft.SharePoint.Client.NavigationNodeCollection] $sNodes = $srchNav.Children
$clientContext.Load($srchnav)
$clientContext.Load($sNodes)
$clientContext.ExecuteQuery()
Important points:
The next part checks if the Nodes exist and whether they should be deleted.
# Check the existing Nodes
# Need to iterate through rather than foreach since we may delete some Nodes
for ($nodeID=0;$nodeID -lt $sNodes.Count;$nodeID++){
$nNode = $sNodes[$nodeID];
if ($nNode.Title -eq $nodeEverythingTitle) {
if ($nNode.Url -eq $nodeEverythingUrl) {
#Node is unchanged, don't need to delete it, or add it again
write-host "Everything Node is unchanged"
$addEverything = $false
}
else {
#Node Url is different; delete this Node and add it again
write-host "Deleting Everything Node"
$nNode.DeleteObject()
}
}
if ($nNode.Title -eq $nodeThisSiteTitle) {
if ($nNode.Url -eq $nodeThisSiteUrl) {
#Node is unchanged, don't need to delete it, or add it again
write-host "This Site Node is unchanged"
$addThisSite = $false
}
else {
#Node Url is different; delete this Node and add it again
write-host "Deleting This Site Node"
$nNode.DeleteObject()
}
}
}
#Update the Client Context with the changes
$clientContext.ExecuteQuery()
Notes:
I like to load the updated Navigation Nodes again, just to make sure:
#Load the Navigation again just to be sure
$nav = $web.Navigation
$clientContext.Load($nav)
$clientContext.ExecuteQuery()
$srchNav = $nav.GetNodeById(1040);
[Microsoft.SharePoint.Client.NavigationNodeCollection] $sNodes = $srchNav.Children
$clientContext.Load($srchnav)
$clientContext.Load($sNodes)
$clientContext.ExecuteQuery()
Now we Add the Nodes:
# Add the Nodes if they are not there already
if ($addEverything) {
write-host "Adding Everything Node"
$nodeEverything = New-Object Microsoft.SharePoint.Client.NavigationNodeCreationInformation
$nodeEverything.Title = "Everything"
$nodeEverything.Url = "/search/Pages/results.aspx"
$nodeEverything.AsLastNode = $false
# IsExternal is really important or it tries to resolve the url and fails.
$nodeEverything.IsExternal = $true
$clientContext.Load($sNodes.Add($nodeEverything))
}
if ($addThisSite) {
write-host "Adding This Site Node"
$nodeThisSite = New-Object Microsoft.SharePoint.Client.NavigationNodeCreationInformation
$nodeThisSite.Title = "this site"
$nodeThisSite.Url = "/_layouts/15/osssearchresults.aspx"
$nodeThisSite.AsLastNode = $true
#IsExternal is really important or it tries to resolve the url and fails.
$nodeThisSite.IsExternal = $true
$clientContext.Load($sNodes.Add($nodeThisSite))
}
$clientContext.ExecuteQuery()
Notes:
So that is the essence of the solution, which I have in a function setSearchUrls ($web) ProcessWeb invokes this for each subsites of a given site:
function processWeb($web)
{
$clientContext.Load($web)
$clientContext.ExecuteQuery()
Write-Host "Processing Web URL is" $web.Url
setSearchUrls( $web)
#Process all sub-sites from this site
$childWebs = $web.Webs
$clientContext.Load($childWebs)
$clientContext.Load($web)
$clientContext.ExecuteQuery()
foreach ($childWeb in $childWebs)
{
processWeb($childWeb)
}
}
I then retrieve the list of Site Collections that I want to process from a text file, and process each one in turn
Get-Content C:\siteslist.txt | Foreach-Object {
write-Host "Procesing Site Url: " $_
$webUrl = $_
$clientContext = Get-Context -Url $webUrl -Credentials $credentials
#get the Starting site to set Search Urls
$rootWeb = $clientContext.Web
$clientContext.Load($rootWeb)
$clientContext.ExecuteQuery()
processWeb $rootWeb
}
This can be run if new sites are added, as it will only add the Navigation to a site where it is not already there.
Hopefully this will help someone else.
At a recent Solutions Day we gave a session on how to get a document stored and distributed to staff with DocRead and SharePoint. Once distributed, each staff member is given a reading task and a deadline to complete the task by. To ensure a user truly undestands the document (or video, image, audio, web page, web url) you can also set a quiz and pass mark.
Here's the session we gave ... you may have a need:
Stop Being Ignored by your staff! How to distribute, track, and get sign-off on your documents…
Ever been frustrated that your documents aren’t being read? Tired of losing track of who has and hasn’t read your documents, or watched your latest training video? DocRead for SharePoint makes it a breeze to upload a piece of content to SharePoint and get groups of users to read, confirm and pass a test by a deadline you set! Join this session and we will be giving away DocRead Team Editions to 5 lucky winners!
CRUD Operation Using REST API in SharePoint List with script editor.
The goal of this blog is to perform CRUD operation in SharePoint List using REST API In Script Editor Web Part.
Steps.
Create Custom List in SharePoint.
Created one Custom List named Customer with five Fields (Customer ID, First Name, Last Name, Location, Ph-Number) as below.
JQuery Library.
Have to use JQuery with REST API. So to include JQuery reference download JQuery library from here and upload to site Assets.
Script Editor.
Script Editor is web part provided in SharePoint 2013 for page level scripting.
How to add Script Editor Web Part.
GearBox-> Edit Page -> INSERT - > WebPart -> (In Categories) Media and Content -> (In Parts) -> Script Editor-> Add
Now Click Edit Snippet in Script Editor and start codding.
First add JQuery reference to Script Editor from Site Assests JQuery Library.
Copy URL and paste in scr.
<script src=”http://<site>/SiteAssets/jquery-1.11.3.min.js”></script>
Next step is to perform CRUD operation on Customer List.
Copy and Paste below code in Script Editor.
//Replace with your JQuery url
<script src="http://<your site name>/SiteAssets/jquery-1.11.3.min.js"></script>
<script>
var v1, v2, v3, v4, v5, itemid;
$(document).ready(function(){
createItem();
read();
update();
Deleted();
});
function read(){
var resturl = _spPageContextInfo.webAbsoluteUrl + "/_api/web/lists/getbytitle('Customer')/items";
$.ajax({
url: resturl,
method: "GET",
headers: { "Accept": "application/json; odata=verbose" },
success: function (data) {
var lnt = data.d.results.length;
for(var i=0; i<lnt; i++ ){
var title = data.d.results[i].Title;
var firstname = data.d.results[i].First_x0020_Name;
var lastname = data.d.results[i].Last_x0020_Name;
var phnumber = data.d.results[i].Ph_x002d_Number;
var location = data.d.results[i].Location;
var id = data.d.results[i].ID;
var tbldata = "<tr><td><input type='radio' class='addcls' name='rd1' value='"+id+"' onclick='javascript:getcheked();' /></td><td >"+title+"</td><td>"+firstname+"</td><td>"+lastname+"</td><td>"+location+"</td><td>"+phnumber+"</td></tr>"
$("#tbl2").append(tbldata);
}
},
error: function (data) {
console.log(data.responseJSON.error);
}
});
}
function addNewItem(url, data) {
$.ajax({
url: _spPageContextInfo.webAbsoluteUrl + url,
type: "POST",
headers: {
"accept": "application/json;odata=verbose",
"X-RequestDigest": $("#__REQUESTDIGEST").val(),
"content-Type": "application/json;odata=verbose"
},
data: JSON.stringify(data),
success: function (data) {
alert("Record Added");
},
error: function (error) {
console.log(JSON.stringify(error));
}
});
}
function GetItemTypeForListName(name) {
return"SP.Data." + name.charAt(0).toUpperCase() + name.slice(1) + "ListItem";
}
function createItem(){
$("#btn-add").click(function(){
var addNewItemUrl = "/_api/Lists/GetByTitle('Customer')/Items";
var itemType = GetItemTypeForListName('Customer');
var CustomerId = $("#CustomerId").val();
var CustomerFirstName = $("#CustomerFirstName").val();
var CustomerLastName = $("#CustomerLastName").val();
var CustomerLocation = $("#CustomerLocation").val();
var CustomerPhNumber = $("#CustomerPhNumber").val();
var item = {
"__metadata": { "type": itemType },
"Title": CustomerId,
"First_x0020_Name": CustomerFirstName,
"Last_x0020_Name": CustomerLastName,
"Location": CustomerLocation,
"Ph_x002d_Number": CustomerPhNumber
};
addNewItem(addNewItemUrl, item);
});
}
function update(){
$("#btndel").click(function(){
var requestUri = _spPageContextInfo.webAbsoluteUrl + "/_api/web/lists/GetByTitle('Customer')/getItemById(" + itemid + ")";
var itemType = GetItemTypeForListName('Customer');
var item = {
"__metadata": { "type": itemType },
"Title": v1,
"First_x0020_Name": v2,
"Last_x0020_Name": v3,
"Location": v4,
"Ph_x002d_Number": v5
};
UpdateData(requestUri,item);
});
}
function getcheked(){
$(".addcls").each(function(){
if($(this).is(":checked")){
var chkdata = $(this).val();
$("#hdndata").val(chkdata);
itemid =$("#hdndata").val();
var $row = $(this).closest("tr"), // Finds the closest row <tr>
$tds2 = $row.find("td:nth-child(2)");
$tds2.prop("contentEditable", "true");
$tds2.keyup(function(){
v1 = $(this).text();
});
$tds3 = $row.find("td:nth-child(3)")
$tds3.prop("contentEditable", "true");
$tds3.keyup(function(){
v2 = $(this).text();
});
$tds4 = $row.find("td:nth-child(4)");
$tds4.prop("contentEditable", "true");
$tds4.keyup(function(){
v3 = $(this).text();
});
$tds5 = $row.find("td:nth-child(5)");
$tds5.prop("contentEditable", "true");
$tds5.keyup(function(){
v4 = $(this).text();
});
$tds6 = $row.find("td:nth-child(6)");
$tds6.prop("contentEditable", "true");
$tds6.keyup(function(){
v5 = $(this).text();
});
}
})
}
function UpdateData(requestUri,item){
$.ajax({
url: requestUri,
type: "POST",
data:JSON.stringify(item),
headers: {
"accept":"application/json;odata=verbose",
"content-type": "application/json;odata=verbose",
"X-RequestDigest": $("#__REQUESTDIGEST").val(),
"X-HTTP-Method": "MERGE",
"IF-MATCH":"*"
},
success: onSuccess,
error: onError
});
}
function onSuccess(data) {
alert("Updated");
}
function onError(error) {
console.log(JSON.stringify(error));
}
function DeleteItem(deleteuri){
$.ajax({
url: deleteuri,
type: "POST",
headers: {
"accept":"application/json;odata=verbose",
"content-type": "application/json;odata=verbose",
"X-RequestDigest": $("#__REQUESTDIGEST").val(),
"X-HTTP-Method": "DELETE",
"IF-MATCH":"*"
},
success: onDeleteSuccess,
error: onDeleteError
});
}
function onDeleteSuccess(){
alert("Entry Deleted");
}
function onDeleteError(){
console.log(JSON.stringify(error));
}
function Deleted(){
$("#btndelete").click(function(){
var requestUri = _spPageContextInfo.webAbsoluteUrl + "/_api/web/lists/GetByTitle('Customer')/getItemById(" + itemid + ")";
DeleteItem(requestUri);
});
}
</script>
<div id="createData">
<table>
<tr>
<td>
<table>
<tr>
<td>Customer Id</td>
<td>
<input type="text" id="CustomerId"/>
</td>
</tr>
<tr>
<td>First Name</td>
<td>
<input type="text" id="CustomerFirstName"/>
</td>
</tr>
<tr>
<td>Last Name</td>
<td>
<input type="text" id="CustomerLastName"/>
</td>
</tr>
<tr>
<td>Location</td>
<td>
<input type="text" id="CustomerLocation" />
</td>
</tr>
<tr>
<td>Ph-Number</td>
<td>
<input type="text" id="CustomerPhNumber"/>
</td>
</tr>
<tr>
<td>
<button value="Add" id="btn-add">Add</button>
</td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div id="readData">
<div id="tbldatamain">
<table id=tbl2>
<tr><th><input type="radio"></th></input><th>Customer ID</th><th>First Name</th><th>Last Name</th><th>Location</th><th>Ph-Number</th></tr>
</table>
</div>
<input type="hidden" id="hdndata" value=""/>
<div>
<table><tr><td><button id="btndel">Update</button></td><td><button id="btndelete">Delete</button></td></tr>
</div>
</div>
<style>
#readData{
position: absolute;
top: 205px;
left: 915px;
}
</style>
After pasting code Click Insert->Check In -> Publish this draft
And visit to page. Page will look like below
To Add -> Fill data and click add.
To Update -> Checked Radio button. After checked Data field will become editable. Edit field and click update.
To Delete -> Checked Radio button and click Delete.
This is probably the last newsletter of the year, so let me start by wishing you all some amazing holidays with your friends and family, and we look forward to the fun in 2016!
*** TWO DAYS LEFT! SharePoint Community Xmas 2015 Giveaway sponsored by LearnNowOnline! ***
To continue with our tradition and commitment to others in the SharePoint community, we are happy to announce more great prizes to members who contribute and help others learn SharePoint. I am extremely pleased to announce that for our latest prize we are giving something that I am sure will help you all get something nice for the holidays, 2x 100$ Amazon.com gift cards!
*** SharePoint 2016 for IT Pros Webinar on January 21***
Start the New Year off right! Join Vlad Catrinescu, Microsoft MVP, as he helps you prepare for the coming release of SharePoint 2016. This latest version of SharePoint comes with a plethora of new features and promises greater stability and true hybrid readiness. As an IT Professional, you need to know what SharePoint 2016 has in it and how it will impact your SharePoint implementation.
*** Everything you need to know about Cloud Hybrid Search by Nico Martens***
In the past, Microsoft has attempted to provide hybrid search scenarios between your on-premises SharePoint environment and SharePoint Online. These solutions were based on query federation. In September this year, Microsoft released the new Cloud Hybrid Search Service Application. Instead of using query federation to surface results in your environment, it relies on indexing your on-premises content in Office 365
*** SPONSORED: SharePoint Add-ins to improve productivity and user adoption! ***
We all know that to get the most from any technology simplicity, ease of use and added value are the key ingredients. With the SharePoint ShortUrl and the SharePoint Document Merge Add-ins this is delivered! Check out this blog post to learn about them!
*** Want to learn PowerShell for Office 365? ***
There is a new course on Pluralsight from Office Servers and Services MVP Vlad Catrinescu on PowerShell for Office 365. This 3 hours and a half course doesn’t only focus on the list of commandlets, but also shows how you can automate boring tasks and deliver business value using the magic of PowerShell.
If you don’t got a Pluralsight subscription, get one free here: http://spvlad.com/1NxjUZo
*** Rencore Report – The State of SharePoint and Office 365 Development 2015***
The wait is finally over: Rencore just released our industry report The State of SharePoint and Office 365 Development 2015! To get your free copy of this first-of-its-kind report, check out the Rencore Site
*** Office 365 news roundup ***
Microsoft recently launched three new Office 365 plans for small and medium-sized businesses as well as Office 365 E5, the new premium plan that gives our enterprise customers access to a wide range of new features and capabilities.
As always, I don’t know where to report issues with Office 365. So here I am carping in a public channel in the hopes that the right person sees it. This also may happen with SharePoint 2013 on premises, but I can’t recall.
When I use a refiner that is based on a Lookup column, I’ll often see something like the attached image. As you can see, there are two clients listed: Anchor Glass and 29. Anchor Glass is the title of the item in the Clients list with the ID of 29, but it still doesn’t make sense (especially to those poor users). It’s as if the indexer isn’t smart enough to handle Lookup columns properly – but only some of the time.
This happens on multiple tenants, with different Lookup columns to different lists, but not consistently, or in any pattern I’ve been able to discern. Generally it’s the Title column we’re looking up into. Using a Lookup column into a list is almost always preferable to using Managed Metadata (IMO) because we can store additional data about the values in the list. For instance, in the Clients list above, we have the client contact info, who works with the client, when we started working with them, what the billings are, etc. Managed Metadata is worthless for that.
But the bug.
Has anyone else seen this? Any ideas on how to work around it?
This blog post discusses the new Cloud Hybrid Search Service Application.
Introduction
In the past, Microsoft has attempted to provide hybrid search scenarios between your on-premises SharePoint environment and SharePoint Online. These solutions were based on query federation. For instance, when you searched for a document in SharePoint Online in your on-premises environment, the query would be sent to the on-premises environment, and the results are returned back to the user in SharePoint Online. Microsoft just released a wizard to automate this: http://ift.tt/1LjKzXh
In September this year, Microsoft released the new Cloud Hybrid Search Service Application.
Instead of using query federation to surface results in your environment, it relies on indexing your on-premises content in Office 365. This takes away a lot of complexity setting it up, and makes it possible to mix results from SharePoint on-premises and Office 365 in a single result block. This new feature can be set up using SharePoint 2013 or SharePoint 2016.
Below is a representation of the "old" and the "new" Hybrid search architecture.
Old architecture
In this scenario, the user enters a query in the on-premises search center. The query is then sent to the on-premises query component and the SharePoint Online query component. This is why results cannot be mixed in this scenario, as there are separated indexes for SharePoint on-premises and SharePoint Online.
New architecture
In this scenario, the Cloud Search Service crawler crawls the content sources on-premises and sends the parsed content to the SharePoint Online Content processing component. After processing the content and doing ACL mapping - for security trimming purposes - the data is saved in the SharePoint Online index. Because the index is saved online, it is now possible to mix results in your search results and use the data in Delve.
Please note that the new Cloud Hybrid Search is still in preview, so things might change along the way!
If you want your on-premises SharePoint to show SharePoint Online results, you still have to configure the "old" outgoing hybrid search. See the following link for more information: http://ift.tt/1jxxy0G
Why Cloud Hybrid Search?
Not all companies are ready to make the move to the cloud for all their workloads. In order to help customers make the move for specific workloads, Microsoft now provides an easy way to gradually move to the cloud while maintaining a great search experience for end users.
By using the new Cloud Hybrid search solution, users are able to search content from the following sources from within SharePoint Online:
The index for all these sources is indexed in Office 365, which gives Microsoft the ability to mix results across sources based on relevancy, use the Office 365 ranking model and even include all of this in Delve!
Organizations can also scale down search infrastructure as content processing and analytics are handled by Office 365.
Prerequisites
In order to use the new Hybrid search functionality, make sure you have installed the following pre-requisites for your environment.
SharePoint on-premises
If you use SharePoint 2013, make sure you installed the August 2015 PU or later. I would recommend the latest CU without known regressions, as there have been improvements to the hybrid search.
Using the public preview of SharePoint 2016 IT Preview is also supported.
Office 365
The cloud Search service application is currently not available for customers outside the regular Office 365 multitenant service, including China data center customers and Government cloud customers.
Account synchronization
Accounts need to be synchronized to Office 365 in order to have a single identity for users. All users that want to make use of Office 365 Hybrid search need a SharePoint Online license assigned.
Below tools are supported to perform directory synchronization:
If you do not have any of the above synchronization tools deployed in your environment, I would recommend using AADConnect. It also has the possibility to configure ADFS for you, so you can enjoy the full Single-sign on experience.
Software needed during configuration of Hybrid Search
On the SharePoint server where you are performing the configuration of Hybrid Search, you will need to install the following prerequisite software in this specific order.
Onboarding script
The script can be downloaded along with documentation from the Microsoft Connect Site: http://ift.tt/1OsknQg
If you do not have access to the cloud Hybrid Search preview program, you can request access via the link http://ift.tt/1OSTanW. Please make sure you are using the latest version prior to execution.
Cloud Search Service Application
After all the prerequisites have been installed, it's now time to create the Cloud Search Service Application. The creation of the Cloud Search Service Application is pretty straightforward. You could use any script that you prefer, just add the parameter "CloudIndex $true" to the New-SPEnterpriseSearchServiceApplication cmdlet.
On the server that is running SharePoint Server 2013 or SharePoint Server 2016 Preview: Copy the sample script below and save it as CreateCloudSSA.ps1 and run it. This will create a single-server Search Service Application topology, meaning there is no high availability in your farm.
## Refer to Microsoft Connect Terms of use http://ift.tt/1QE87Pc ##
## This script is being provided as a sample for the creation of a single box cloud SSA, if you wish to create a multiple box cloud SSA, note that the -CloudIndex $true flag must be set for each hybrid SSA ##
## Gather mandatory parameters ##
## Note: SearchServiceAccount needs to already exist in Windows Active Directory as per TechNet Guidelines http://ift.tt/1OST8wh ##
Param(
[Parameter(Mandatory=$true)][string] $SearchServerName,
[Parameter(Mandatory=$true)][string] $SearchServiceAccount,
[Parameter(Mandatory=$true)][string] $SearchServiceAppName,
[Parameter(Mandatory=$true)][string] $DatabaseServerName
)
Add-PSSnapin Microsoft.SharePoint.Powershell -ea 0
## Validate if the supplied account exists in Active Directory and whether it’s supplied as domain\username
if ($SearchServiceAccount.Contains("\")) # if True then domain\username was used
{
$Account = $SearchServiceAccount.Split("\")
$Account = $Account[1]
}
else # no domain was specified at account entry
{
$Account = $SearchServiceAccount
}
$domainRoot = [ADSI]''
$dirSearcher = New-Object System.DirectoryServices.DirectorySearcher($domainRoot)
$dirSearcher.filter = "(&(objectClass=user)(sAMAccountName=$Account))"
$results = $dirSearcher.findall()
if ($results.Count -gt 0) # Test for user not found
{
Write-Output "Active Directory account $Account exists. Proceeding with configuration."
## Validate whether the supplied SearchServiceAccount is a managed account. If not make it one.
if(Get-SPManagedAccount | ?{$_.username -eq $SearchServiceAccount})
{
Write-Output "Managed account $SearchServiceAccount already exists!"
}
else
{
Write-Output "Managed account does not exist - creating it."
$ManagedCred = Get-Credential -Message "Please provide the password for $SearchServiceAccount" -UserName $SearchServiceAccount
try
{
New-SPManagedAccount -Credential $ManagedCred
}
catch
{
Write-Output "Unable to create managed account for $SearchServiceAccount. Please validate user and domain details."
break
}
}
Write-Output "Creating Application Pool."
$appPoolName=$SearchServiceAppName+"_AppPool"
$appPool = New-SPServiceApplicationPool -name $appPoolName -account $SearchServiceAccount
Write-Output "Starting Search Service Instance."
Start-SPEnterpriseSearchServiceInstance $SearchServerName
Write-Output "Creating cloud Search service application."
$searchApp = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceAppName -ApplicationPool $appPool -DatabaseServer $DatabaseServerName -CloudIndex $true
Write-Output "Configuring search administration component."
$searchInstance = Get-SPEnterpriseSearchServiceInstance $SearchServerName
$searchApp | get-SPEnterpriseSearchAdministrationComponent | set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance $searchInstance
$admin = ($searchApp | get-SPEnterpriseSearchAdministrationComponent)
Write-Output "Waiting for the search administration component to be initialized."
$timeoutTime=(Get-Date).AddMinutes(20)
do {Write-Output .;Start-Sleep 10;} while ((-not $admin.Initialized) -and ($timeoutTime -ge (Get-Date)))
if (-not $admin.Initialized) { throw 'Admin Component could not be initialized'}
Write-Output "Inspecting cloud Search service application."
$searchApp = Get-SPEnterpriseSearchServiceApplication $SearchServiceAppName
#Output some key properties of the Search service application
Write-Host "Search Service Properties"
Write-Host " Cloud SSA Name : " $searchapp.Name
Write-Host " Cloud SSA Status : " $searchapp.Status
Write-Host "Cloud Index Enabled : " $searchApp.CloudIndex
Write-Output "Configuring search topology."
$searchApp = Get-SPEnterpriseSearchServiceApplication $SearchServiceAppName
$topology = $searchApp.ActiveTopology.Clone()
$oldComponents = @($topology.GetComponents())
if (@($oldComponents | ? { $_.GetType().Name -eq "AdminComponent" }).Length -eq 0)
{
$topology.AddComponent((New-Object Microsoft.Office.Server.Search.Administration.Topology.AdminComponent $SearchServerName))
}
$topology.AddComponent((New-Object Microsoft.Office.Server.Search.Administration.Topology.CrawlComponent $SearchServerName))
$topology.AddComponent((New-Object Microsoft.Office.Server.Search.Administration.Topology.ContentProcessingComponent $SearchServerName))
$topology.AddComponent((New-Object Microsoft.Office.Server.Search.Administration.Topology.AnalyticsProcessingComponent $SearchServerName))
$topology.AddComponent((New-Object Microsoft.Office.Server.Search.Administration.Topology.QueryProcessingComponent $SearchServerName))
$topology.AddComponent((New-Object Microsoft.Office.Server.Search.Administration.Topology.IndexComponent $SearchServerName,0))
$oldComponents | ? { $_.GetType().Name -ne "AdminComponent" } | foreach { $topology.RemoveComponent($_) }
Write-Output "Activating topology."
$topology.Activate()
$timeoutTime=(Get-Date).AddMinutes(20)
do {Write-Output .;Start-Sleep 10;} while (($searchApp.GetTopology($topology.TopologyId).State -ne "Active") -and ($timeoutTime -ge (Get-Date)))
if ($searchApp.GetTopology($topology.TopologyId).State -ne "Active") { throw 'Could not activate the search topology'}
Write-Output "Creating proxy."
$searchAppProxy = new-spenterprisesearchserviceapplicationproxy -name ($SearchServiceAppName+"_proxy") -SearchApplication $searchApp
Write-Output "Cloud search service application provisioning completed successfully."
}
else # The Account Must Exist so we can proceed with the script
{
Write-Output "Account supplied for Search Service does not exist in Active Directory."
Write-Write-Output "Account supplied for Search Service does not exist in Active Directory."
Write-Output "Script is quitting. Please create the account and run again."
Break
} # End Else
The output should look similar to this:
Proxy configuration
If a proxy is used by your organization to allow Internet access, you have to configure this proxy for Hybrid Cloud Search as well. For a more in-depth article, please look at http://ift.tt/1OWNnP6, but for now we can just add the proxy settings to the machine config: “C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config”
Here's an example of what this would look like:
<system.net>
<defaultProxy>
<proxy usesystemdefault="false" proxyaddress="http://10.1.10.1:8080" bypassonlocal="true" />
</defaultProxy>
</system.net>
Place this anywhere between your <configuration> and </configuration> tag. To make it easier to find when you need it, you could place it right before the tag.
Onboarding
After successfully installing the prerequisites and configuring the Cloud Search Service Application, it is time to start the onboarding process. The onboarding process will create a trust between your SharePoint on-premises and Office 365 environment. This will allow SharePoint to move the index to Office 365 for further processing.
Run the onboarding script:
.\Onboard-CloudHybridSearch.ps1 -PortalUrl "http://ift.tt/1Mk9Rr0" -CloudSSAId "<Cloud Search Service Application name>"
Enter your Global Administrator credentials when prompted.
The output should be something like this:
The script changes quite frequently, so as you can see, the script name and the parameters have changed a bit since I ran the script. Make sure you check to see what the parameter names are when you run the script.
Configure content source
You can configure the content source in your new Cloud Search Service Application as you would in any other on-premises Search Service Application.
Enter the start addresses that you would like to crawl and start a full crawl for the content source. After the crawl is done, check the crawl log for the specific content source to see if all went well.
Make sure to check your proxy configuration (http://ift.tt/1OWNnP6) if you see 1 Top Lever Error with the following error message:
AzureServiceProxy caught Exception: *** Microsoft.Office.Server.Search.AzureSearchService.AzureException: AzurePlugin was not able to get Tenant Info from configuration server
at Microsoft.Office.Server.Search.AzureSearchService.AzureServiceProxy.GetAzureTenantInfo(String portalURL, String realm, String& returnPropertyValue, String propertyName)
at Microsoft.Office.Server.Search.AzureSearchService.AzureServiceProxy.SubmitDocuments(String azureServiceLocation, String authRealm, String SPOServiceTenantID, String SearchContentService_ContentFarmId, String portalURL, String testId, String encryptionCert, Boolean allowUnencryptedSubmit, sSubmitDocument[] documents, sDocumentResult[]& results, sAzureRequestInfo& RequestInfo) ***
Verifying results
In Office 365 search for a document and it will return results for both SharePoint Online and SharePoint on-premises if everything is configured correctly.
In this example, search shows results from the following sources:
If you want to return results only from your on-premises you can use the "isexternalcontent:1" property.
This returns only on-premises results:
That's it!
I hope this helps you use the new Hybrid Cloud Search Service Application.
