Skip to main content

Message to multiple site collections


Before some months I start following the TechNet forums about SharePoint. I read every week many questions, bookmark the interesting once, answer and research the others. I find it very useful and many new things are learn in a very fast way. Of course, the price of this is a time but let’s say I have a lot of it now J

I notice one issue in tree similar questions so I decide to write a post about it.

The scenario: how to add a message on a multiple site collections.
This might be necessary when some farm maintenance is planned and the users must be notified.

The solution: Site collection feature which use the JavaScript API to display the notification. The script is injected on the page with a delegate control AdditionalPageHead.

Code Sample:   download from here 

Explanation:


SharePoint 2010 JavaScript client API has the function SP.UI.Status.addStatus which adds astatus message on a page. The code is simple:

SP.UI.Status.addStatus('the mayans:','The world will not end on 22.12.2012!',true);


This function is a part for the client site API so the sp.js javascript must be loaded on the page.

The big question here is how such javascript can be loaded on each page. One possible opinion is with changes in the master page of each site collection. But this is a heavy task. And may cause some issues.

The better approach here is the use of the delegate control AdditionalPageHead.

First, what is a delegate control – this is a region in the page that allows the content to be replaced with custom one. All master pages have the following markup which define a delegete control with ID AdditionalPageHead :
<SharePoint:DelegateControl runat="server" ControlId="AdditionalPageHead">
</SharePoint:DelegateControl>
Second, how we add our logic using this AdditionalPageHead control – with a element file that contains the following markup:

 <xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <Control Id="AdditionalPageHead" ControlSrc="~/_controltemplates/SPNotification/PageHead.ascx" Sequence="1001" />
</Elements>

here PageHead.ascx control is our custom control which contains the csutom javascript logic:

<script type="text/javascript">
    function AddNotification() {
   var sid = SP.UI.Status.addStatus('the mayans:', 'The world will not end on 22.12.2012! ', true);
    }
    ExecuteOrDelayUntilScriptLoaded(AddNotification, 'sp.js')
</script>

The final step is to use a powershell for deploying the solution and activating the feature in each site collection. Here is an example of search script. Feel free to modify it so it serve your needs:
------------------------------------------------------------------------
$snapin = Get-PSSnapin Microsoft.SharePoint.Powershell
if ($snapin -eq $null)
{
    Write-Host "Loading SharePoint Powershell Snapin"
    Add-PSSnapin "Microsoft.SharePoint.Powershell"
}

$solutionPackage = "SPNotification.wsp"
$path ="C:\something\"

# add solution
Add-SPSolution -LiteralPath ($path + $solutionPackage) -Confirm:$false
Write-Host "Adding solution" $solutionPackage
while ((Get-SPSolution | where-object {$_.Name -eq $solutionPackage}) -eq $null)
{
Start-Sleep -Seconds 3
}

#deploy solution
$solution = Get-SPSolution | where-object {$_.Name -eq $solutionPackage}
Install-SPSolution -Identity $solutionPackage -GACDeployment -Force
Write-Host -NoNewLine "Solution " $solution.Name "is deploying "
while ((Get-SPSolution | where-object {$_.Name -eq $solutionPackage}).Deployed -eq $false)
{
Start-Sleep -Seconds 3
}

#iteratio through all site collection and activate the feature
$farm = Get-SPFarm
$websvcs = $farm.Services | where -FilterScript
        {$_.GetType() -eq [Microsoft.SharePoint.Administration.SPWebService]}
foreach ($websvc in $websvcs) {
    foreach ($webapp in $websvc.WebApplications) {
        Write-Host "web app: " $webapp.Name
        foreach ($site in $webapp.Sites) {
           Write-Host "Activate feature in " $site.uRL
           Enable-SPFeature –Identity 'b6bcf98b-8f73-4c08-b4fe-32f052a8c971' –url $site.uRL
        }
    }
}
------------------------------------------------------------------------


Comments

Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed.
The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before.
There is a new control called ClientPeoplePicker.

How to use it:
1.Add this references

<%@RegisterTagPrefix="wssawc"Namespace="Microsoft.SharePoint.WebControls"Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>
2.Add the following control declaration


      <wssawc:ClientPeoplePicker Required="true" ValidationEnabled="true" ID="peoplePicker" runat="server" InitialHelpText="<%$Resources:wss,aclinv_PickerIntialHelperText%>" VisibleSuggestions="3" Rows="1" AllowMultipleEntities="false" CssClass

The column name that you entered is already in use or reserved. Choose another name.

The problem: 
You want to create column with a specific name in SharePoint but SharePoint gives you the message "The column name that you entered is already in use or reserved. Choose another name."



Why this is a problem?
Because you need to create custom columns and content types using the default SharePoint interface.
And the business users have to see properly named columns - for example "Description", not "My Description".

Solution:
It is important to know something technical about SharePoint (versions Office 365, 2013, 2010):
 - it supports columns with same Display Names.
 - you can’t have columns with same Internal names

Let’s implement the following common scenario:
You are creating a SharePoint customization and you need the following column:
   Type: Multiple lines of text
   Internal Name: MyProjectDescription
   Display Name: Description

 Here is the correct way to achieve it:
1. Create the column MyProjectDescription.
This will create column with I…

Office 365 Migration API: how to migrate the taxonomy metadata

If you wander whether the Office 365 Migration API supports migration of taxonomy metadata, the answer is YES. The API supports it but there isn't good documentation about how to modify your xml files after the command ConvertTo-SPOMigrationTargetedPackage.

In this post, I'm going to show you the approach. I assume that you have base knowledge of how to use the Migration API.

The scenario I'm going to use is simple - migrate single Document library with single document.
The document has one taxonomy column (MyTaxonomy) and three versions:

Here are the steps:

Step 1: Export the document library

Export-SPWeb "https://portal.cosingens.com/" ` -ItemUrl "/Shared Documents" ` -Path "\\cos-dev-03\export1\Export" ` -NoFileCompr -IncludeVersions 4
This command will export the document library and will create the initial package.
The command is not part of the Migration API. It is well know since SharePoint 2010 and is part of the server side obje…