Showing posts with label SharePoint 2010. Show all posts
Showing posts with label SharePoint 2010. Show all posts

Wednesday, June 29, 2011

SharePoint 2010: Add button to Ribbon with SharePoint designer

Sometimes you may need to add buttons to SharePoint 2010 ribbon. You can take one of two approaches: You can write code to add the button. Another approach is to use SharePoint Designer to add button to Ribbon. Today I’ll show you how to add button to Ribbon using SharePoint Designer. However, when you’ll use SharePoint Designer to add button to Ribbon and if you do  so in Development or Staging server, then think about how to do the same in Production server.

Add Button to List/Library forms (AllItems.aspx, DispForm.aspx, EditForm.aspx, NewForm.aspx)

Let’s say you have a list and you want to add a new Ribbon button in the AllItems.aspx page.
1. First open the site in SharePoint Designer.
2. Then click “List and Libraries” link from the left-hand menu and then click the target list from the details page on the right hand side as shown below:
image
Figure 1: Select List/Libraries in SharePoint Designer

3. Once you click the list name you’ll be landed to the list/library settings page. In this page you can edit four forms (AllItems.aspx, DispForm.aspx, EditForm.aspx and NewForm.aspx) and you can add button to the page’s ribbon. The page is shown below:
image
Figure 2: Four built-in Forms

4. From the ‘List Settings’ tab on the top, select ‘Custom Action’ as shown below:
image
Figure 3: Add custom Action

5. Say you want to add button to ‘NewFom.aspx’. For this click ‘New Form Ribbon’ from the Custom Action. You’ll get the ‘Create Custom Action’ window where you can add custom action to the Ribbon. From the window below you can chose one of three different actions: Navigate to form, Initiate workflow, Navigate to Url. If you need more custom action then SharePoint Designer will not be helpful. You need to write code to extend Ribbon button actions.
image
Figure 4: Custom Action Properties



Find Ribbon Location:

In the List/Library form, the button are placed in groups. As shown in the image below, the new form has three sections:
image
Figure 5: Buttons are placed in Groups/Sections in form
Now you may want to place your button in a particular group and for that you need know the location id so that you can put the id in the ‘Ribbon Location’ in the custom action properties in SharePoint Designer. Using Firebug extension of Mozilla Firefox, I have found the ribbon location id as shown below:
image
Figure 6: Ribbon group/section id (detected using Firebug extension of Firefox)
So now you can put the ribbon location id in the custom action properties. For example to put the ‘Show Me’ button in the ‘Commit’ section I have put the ribbon button location to ‘Ribbon.ListForm.Edit.Commit.Controls._children’. Here the ‘.Controls._children’ is added to the ribbon id. The following figure show two windows side by side:
image
Figure 7: Custom Action windows (On Left) and New Item Form (On right) with ‘Show Me’ button


Decide when to show the Ribbon Button

Sometimes you don’t want to show the button for all users. Rather you want to show for users having a set of permissions. The ‘Rights mask’ option allow us to meet this requirements. The available values can be found on MSDN. You can put more than one values in the Rights Mask text box separated by semicolons as shown below:
image
Figure 8: Rights mask


Source: http://ranaictiu-technicalblog.blogspot.com/2010/06/sharepoint-2010-add-button-to-ribbon.html

Monday, May 30, 2011

SharePoint 2010: Specified value is not supported for the parameter

Make sure AD is accessible. If you are not connected to domain directly, make sure you have VPN connected.

Tuesday, April 26, 2011

What features do I absolutely need in SharePoint Scanning?

I keep getting this question emailed over and over, and thought I would throw a post up about what I see as absolutely necessary for a SharePoint Scanning and Capture application:
  1. The solution needs to be hardware agnostic.   There are quite a few applications out there that are tied to a single hardware platform.  Kodak is one that comes to mind.  Your capture application needs to support TWAIN, ISIS and VRS drivers for all different manufacturers.  Out of the box, it also needs to support image file import for PDF, TIFF, JPG, etc.  You want to be able to choose your own scanning hardware.
  2. Franken-capture is a bad thing.  Find one capture application that provides all the necessary pieces for your organization.   Don’t pile together 5 different apps to support all your needs, your support nightmare will become a reality.
  3. Advanced Data Extraction (ADE) is absolutely necessary.  ADE is the ability to automatically extract information from a document, regardless of where it lies on the page.  This is key to automation and efficiency.  Many manufacturers in the SharePoint space partner with others to make this happen…go with someone who has it built in to the product.
  4. Require support for multiple back-end repositories.  Don’t go with a pure SharePoint solution.  90% of the organizations I deal with need to send documents and metadata to something other than SharePoint.  Make sure this is out of the box functionality, and don’t settle for “we can build that”.
  5. Routing sheets are the hot new thing.   Make sure that the solution supports 2D barcodes and Optical Mark Recognition (OMR).  These technologies are highly used in distributed capture for SharePoint and are absolutely necessary for any implementation.
  6. Document Harvesting will save you time and effort.  Find a solution that can ingest folder directories and use folder names/file names as metadata.
  7. Dynamic Library, folder names and file naming in SharePoint is required.  Many solutions will create random naming schemes for folders and file names.  People still love their folders, and standardized naming is absolutely required.
Just a short list of features I find customers require in their organizations.

http://scanningwithsharepoint.wordpress.com/2010/11/22/what-features-do-i-absolutely-need-in-sharepoint-scanning/ 

Tuesday, June 8, 2010

SharePoint 2010 Licensing

SharePoint Foundation Server 2010  is the free offering replacing WSS 3.0. and will have the usual limits of SQL Express and Search Express.
The Standard  SharePoint functions will be base around Collaboration, Enterprise Search, Document and Content Management, Social Computing (Wikis, My Sites), Digital Asset Management (including Silverlight) and Records Management. Basically unstructured data.
The Enterprise  functionality is a long list:
  • Excel Services
  • Performance Point Services
  • Advanced Charting
  • Visio Services
  • Access Services
  • InfoPath Form Services
  • Client line of business integration and web parts
  • Custom Reports
In addition server licences can be upgraded to use FAST search.
Speaking of server licenses these break into Standard and Enterprise as before but this time there are both intranet and internet versions. Added to this is the aforementioned FAST server license which comes in both flavours too. So when you add this to the Foundation Server you have a total of seven types of SharePoint (a title for a post if ever I scribbled one).
Note that the SharePoint for Internet 2010 Standard Edition is designed for small to medium concerns and will retail at about half the price of the current MOSS for internet. But, and its a big but, it will be artificially throttled possibly round content size (the Microsoft boys were a bit hazy on this).
For intranet solutions the Client Access Model remains with the need to buy both a Standard  and Enterprise CAL  to access Enterprise features. For FAST although the license upgrade is for the server users utilising it will need an  Enterprise CAL.
Still with me?
Ok – SharePoint 2010 Online for intranet will continue with the current User Subscription License based on Enterprise, Standard and Deskless (read and form filling only). It will also have an Internet and Partner Access versions. Partner Access is effectively an extranet option.
For related technology:
SharePoint Workspace (the app formerly known as Groove) comes with Office 2010 PRO+ (which sounds like a caffeine tablet)
Office Web Apps – Office 2010 but do need SharePoint Foundation 2010  to work.
Project Server 2010 – needs a Project CAL  and a SharePoint Enterprise CAL
SQL Server Power Pivot  - SQL Enterprise Edition  if exposed only in office then an Office 2010 to be surfaced in SharePoint an Enterprise CAL  is required. 
Just for completeness there is also a non SharePoint version of FAST - Fast Search Server 2010 for Internet Business.


http://blogs.charteris.com/blogs/colinn/archive/2009/10/21/sharepoint-2010-licensing.aspx

Wednesday, December 30, 2009

Install SharePoint 2010

Hello All,

Welcome to my blog this is my first post here, and I am going to post about SharePoint 2010 Installation.

Installation Environment:

Windows Server Enterprise 2008 x64 bit, SP2.
SQL Server 2008 Enterprise 64, SP1.
SQLServer2008-KB976761-x64

Run the Installation file and start with installing Pre-requisists and you may face error installing the powershell; if so, uninstall the existing one and run the installer again, this worked with me



Then start installing compalete installation or standalone, I've installed it complete server farm.



after comleting the installation run the configuration wizard and I didn't find changes in the config wizard from 2007



and start playing with the central administration :)