Skip to main content

Custom Item in 'Sned To' menu

In my previous post I show how to put some javascript to all pages in a site collection using the delegate control. This is pretty common scenario and the approach with the AdditionalPageHead control works great.

In this post I will use again the approach to solve another issue.

The scenario:  Add a custom item in the ‘Send To’ section in the contextual menu for document. 

The solution: Overwriting the default javascript function in core.js. The javascript function renders the new idem. A delegate control is used to bring the customizations on the pages in a particular web. 

Code Sample: download from here

In such tasks the most normal approach will be using a custom action which most difficult part is to find the correct value for the Location property.

The problem in our scenario is the fact that the Send To menu items are rendered only by javascript. There is no way to use custom action for it so the only option is to find a way to overwrite javascript.

The file CORE.debug.js is located in the \14\TEMPLATE\LAYOUTS\1033 folder. Inside it is the definition of the function AddSendSubMenu which renders the items. The easiest way for overwriting a function in javascript is loading a function with the same name after the original function.

Overwriting of the AddSendSubMenu method defined in the default scripts can be done in the following way:
AddSendSubMenu = function (m, ctx) { }
    function resetAddSendSubMenu() {
         AddSendSubMenu = function (m, ctx) {
            ULSsa6:;            // new logic        }    }
_spBodyOnLoadFunctionNames is an array which contains the names of the functions which are executed when page is loaded. / _spBodyOnLoadFunctionNames is very useful, if you still don’t know it, please explore some posts about it ! /
Another important moment is how to render the new item. After exploring the original code the following code can be extracted:
 if (ctx.listTemplate == 101) { // document library        var itemId = GetAttributeFromItemTable(itemTable, "ItemId", "Id");
        var listId = ctx.listName;
        var source = window.location + "";
        strAction = "STSNavigate('" + ctx.HttpRoot + "/_layouts/SendToItem/SendToPage.aspx?ItemId=" + itemId + "&ListId=" + listId + "&Source=" + source + "')";
        strImagePath = ctx.imagesPath + "sendOtherLoc.gif";
        menuOption = CAMOpt(sm, "My Custom Item", strAction, strImagePath);
        CUIInfo(menuOption, "MyCustomItem", ["MyCustomItem"]); = "ID_MyCustomItem";
This code should be located in the correct place in the function so the items are rendered in the correct order.


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=, 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".

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 "" ` -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…