http://www.sharepoint-tips.com/2007/01/how-to-add-print-list-option-to-list.html

The Per Item Dropdown (ECB) example in Lightup.xml is wrong. Delete the line containing Type="ECBItem" and it will work.

The Container element does not have an attribute named type. stsadm complains about the line and refuses to install. Removing the line fixes things.

Have you find any solution on this?

I am trying to use {ItemId} token in CustomAction for DiscussionBoard List. While {ListId} token work properly, {ItemId} not work at all.

Here my example:

feature.xml

<?xml version="1.0" encoding="utf-8" ?> 
<Feature Id="5539E0F8-8AA5-41bd-B09F-5DD7F1C99757" 

   Title="Settings button" 

   Description="Settings button ..." 

   Version="1.0.0.0" 

   Scope="Web" 

   xmlns="http://schemas.microsoft.com/sharepoint/"> 

   <ElementManifests> 

      <ElementManifest Location="elements.xml" /> 

   </ElementManifests> 

</Feature>

elements.xml:

<?xml version="1.0" encoding="utf-8" ?> 
<Elements xmlns="http://schemas.microsoft.com/sharepoint/"> 
 <CustomAction Id="IdeaBoardActionsToolbar" 
  RegistrationType="List"

  GroupId="ActionsMenu"

  Location="Microsoft.SharePoint.StandardMenu"

  Title="Item Settings"> 
  <UrlAction Url="~site/ItemSettings.aspx?item={ItemId}&amp;list={ListId}" /> 
 </CustomAction> 
</Elements>

SharePoint will not replace multiple tokens of the same type. If you have a URL that needs the SiteURL twice (say, with an InfoPath form that needs the location of the form as well as the source to return to), then the second URL token won't be generated.

I encountered the same as Brian Abram. Its a mess!! I needed the {ItemId} two times in an UrlAction. It simply does not work!!

I hope there will soon be a service pack updating all the small bugs!

Edit: I found an ugly way to bypass this flaw: <UrlAction Url="javascript:function process(){var site='{SiteUrl}';var item={ItemId};window.location.href=site+'/Lists/MyList/NewForm.aspx?ID='+item+'&amp;Source='+site+'/Lists/myOtherList/DispForm.aspx?ID='+item;};process();"/>

It would be worth exteding this article to comment that:

1. If the .aspx action page is deployed to LAYOUTS directory then code behind model is not supported (all code must be in-line)

• [Michael B writes:] I believe this is not entirely correct. See Andrew Connell's blog about this: http://www.andrewconnell.com/blog/articles/UsingCodeBehindFilesInSharePointSites.aspx

2. The {ItemId} is equivalent to ID attribute of the SPListItem ( wouldn´t it be better to use GUID instead as you do with {ListId}? )

3. Mention that {ListId} string will be encoded and that you should use System.Web.HttpUtility.UrlDecode() function in code to decode it.

4. Have a link to article that describes best practice for how to debug custom actions based on in-line aspx pages.

Adding a custom action to ActionsMenu on Microsoft.SharePoint.StandardMenu for List, the {ListId} token in Url of UrlAction gets different data depending on "where the list is".

Here is the way to find this bug:

1) create a feature and deploy it on sharepoint server. for example:

<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<CustomAction
Id="Test.ActionsMenu"
RegistrationType="List"
GroupId="ActionsMenu"
Location="Microsoft.SharePoint.StandardMenu"
ImageUrl="/_layouts/images/icon_document.gif"
Sequence="10"
Title="Test"
Description="">
<UrlAction Url="JavaScript:window.location='{SiteUrl}/_layouts/test.aspx?listid={ListId}'"/>
</CustomAction>
</Elements>
2) find a list/document library (suppose its name is ALIST), browse to its default view: ...ALIST/Forms/AllItems.aspx, from Actions menu, click the customAction you setup, note the ListID refers to ALIST listID, that is expected.

3)Create a web part page and save this page in a different document library, add a web part by finding ALIST under Lists and Libraries, from this web part's Full Toolbar, click the same actionmenu, note that ListID refers to the document library where the page is stored, not the list the web part refers to (ALIST)

4) You can also find another list/document library (BLIST), browse to its default view ...BLIST/Forms/AllItems.aspx, edit this page,

add ALIST web part, from its Full Toolbar's Actions Menu, click the custom action, please note the {ListID} now refers to BLIST

In step 2 above, where it says that you need to replace the GUID in "<Feature Id="GUID" " with a real GUID that you generate, that GUID should be in Registry Format, excluding the curly braces.

You can see this in the example on http://msdn2.microsoft.com/en-us/library/ms475601.aspx where the XML reads: Id="11111111-1111-1111-1111-11111111111"

The default site settings actions (what you see on _layouts/settings.aspx) are all defined in a Feature. Take a look at SiteSettings.xml in 12\TEMPLATE\FEATURES\SiteSettings on your MOSS 2007 server.

Has anyone gotten these custom actions to work in MOSS? The exact same code works great in WSS 3.0, but when I deploy to a MOSS 2007 server, no menus show up at all except for Site Actions | My Site Actions Button.

I need this to work in the Document Library. Specifically, I need to add a menu option to each document in the library.

As I said, works great in WSS Shared Documents, but not in MOSS Document Lib.

Any thoughts?

Thanks.

I'm trying to add an item to the ActionsMenu of a specific list. I tried adding it to the content type but this does not appear to be working.

This is what I have. The RegistrationId is the Id of my custom contenttype. The contenttype works great. But I cannot seem to add the custom Actions Menu item. Any ideas?

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<!-- Add Command to List ActionMenu -->
<CustomAction
Id="AssociatePerformanceReviews.ReviewSchedulerActionsMenu"
RegistrationType="ContentType"
RegistrationId="0x010013398AF7FC024ec3A6BC7B32B1E566FF"
ImageUrl="/_layouts/images/AssociatePerformanceReviews/AssocPerfRevs39X39.gif"
GroupId="ActionsMenu"
Location="Microsoft.Sharepoint.StandardMenu"
Sequence="199"
Title="Send Reviewer Notification Email" >
<UrlAction Url="~site/_layouts/AssociatePerformanceReviews/AssociatePerformanceReviews.aspx?ListId={ListId}"/>
</CustomAction>
</Elements>

Custom Actions in a listview Webpart
http://blog.thekid.me.uk/archive/2008/04/29/sharepoint-custom-actions-in-a-list-view-webpart.aspx

Sample custom actions
http://blog.thekid.me.uk/archive/2007/06/23/sample-editcontrolblock-customaction-for-sharepoint.aspx

There are two mistakes I found.

1. If you use the scope="Site" you cannot activate the feature on a subsite, you'll have to activate it on site collection level or use the scope="Web" in the feature.xml.

2. You cannot use the Type attribute, but this was already found by a previous poster.

Hope it helps.

I created a post about htis on my blog: http://www.dailycode.net/blog/post/Custom-sharepoint-list-item-action.aspx

Hey Guys, I completely agree with this approach. My Question is some thing else .... Can we get a similar item in the (custom action) in the ECB or Toolbar in sitemanager.aspx in Layouts folder ? If you have any idea please revert back to be ;-) Regards Amith Sasi

[tfl - 20 09 09] Hi - and thanks for your post. You should post questions like this to the MSDN Forums at http://forums.microsoft.com/msdn or the MSDN Newsgroups at

http://www.microsoft.com/communities/newsgroups/en-us/. You are much more likely get a quicker response using the forums than through the Community Content. For specific help about:
Visual Studio : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.vstudio%2C&
Windows : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.windows%2C&
SQL Server : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.sqlserver%2C&
.NET Framework : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.dotnet.framework
PowerShell : http://groups.google.com/group/microsoft.public.windows.powershell/topics?pli=1
All Public : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public%2C&