About Sharepoint 2010

Wednesday, 20 February 2013

AUTO GENERATE SERIAL NUMBER

USE [DatabaseName]

/****** Object: StoredProcedure [dbo].[SP_GENERATE_SLNO] Script Date: 02/20/2013 17:27:42 ******/

SET ANSI_NULLS ON

SET QUOTED_IDENTIFIER ON

-- =============================================

-- Author: <DEEP>

-- Create date: <FEB 02 2013>

-- Description: <Genrate Serial No >

-- =============================================

Create PROCEDURE [dbo].[TABLE_GENERATE_SLNO](

-- Add the parameters for the stored procedure here

@appName as varchar(10))

---exec [GUESTHOUSE_GENERATE_SLNO] 'GH'

BEGIN

SET NOCOUNT ON;

DECLARE @SLGEN VARCHAR(50);

DECLARE @SLRESLT VARCHAR(50);

DECLARE @DATEFRMT VARCHAR(50);

SET @DATEFRMT=(SELECT REPLACE(CONVERT(VARCHAR(8), GETDATE(), 4) ,'.','')AS [DD.MM.YY])

INSERT INTO GENERATE_SLNO (TEMP_INS_CHAR) VALUES(1)

SET @SLGEN=@@IDENTITY;

DELETE FROM GENERATE_SLNO WHERE TEMP_AUTO=@@IDENTITY

SET @SLGEN=(SELECT REPLACE(STR(@SLGEN, 5), SPACE(1), '0'))

IF @@IDENTITY>=99999

BEGIN

TRUNCATE TABLE GENERATE_SLNO

END

SET @SLRESLT=@appName+'-'+@DATEFRMT+'-'+cast(@SLGEN as varchar(50))

END

SELECT @SLRESLT

Thursday, 18 October 2012

Anonymous Access to post comment on Blog SubSite in sharepoint 2010

When we build an internet-facing website using SharePoint, the first question that arises is the accessibility of this site to anonymous users. SharePoint takes care of this feature too, the only thing we need to do is enable the anonymous access to our site.

How do we enable anonymous access?

Enabling anonymous access has two stages. First, this has to be enabled in Central Administration for the respective Web-Application. Then it has to be set for the respective Site (site collection).

Navigate to the central administration page.

Click on Application Management ->Manage Web Applications. Select the web application and click on ‘Authentication providers’

A pop-up window opens, from which you need to select your authentication provider as shown in the image below. Click on ‘Default’

This opens up the edit window of the selected authentication provider. In this window CHECK the “Enable Anonymous Access” field and click on ‘Save’

The above process sets anonymous access at CA level. We still have to set the anonymous access for a single site-collection or for a root site.

Enabling Anonymous Access for a Site

Go to the respective site, for which anonymous access has to be enabled.

Navigate to Sites->Site Permissions. You will notice a new option ‘Anonymous Access’ in the ribbon.

Click on Anonymous Access and select the required option. Selecting ‘Entire Web site’ gives read-only permissions to all users who visit the site.

The process described above is how we enable Read-Only access to anonymous users. But there are also few scenarios where we need to give limited Write/Edit permissions to anonymous users.

For example, when we create a blog site in SharePoint we need to give permissions for all users to add comments to the (published) posts.

(**Note: A SharePoint blog site has three lists – Categories, Posts and Comments—which are created by default. Categories and Posts can be ‘Read only’ lists. But when Comments are taken into consideration, we need to allow anonymous users to write/enter their comments.)

Enabling Anonymous Users to Add Comments to Blog Posts

Navigate to your blog site. Click on, Sites->Site Settings. There in the left menu bar find all the available lists in the blog site. Select ‘Comments’

Now all the available comments will be shown.

In the ribbon select, List Tools->List->List Permissions

Here, we can set permissions for anonymous users to add comments by stopping ‘Inherit permissions’ and giving permissions exclusively for this list. Click on ‘Stop Inheriting Permissions’, this stops inheriting permission from parent site.

When we stop inheriting permissions from parent site, ‘Anonymous Access’ appears in the ribbon menu. Click on this and select ‘Add Items- Add items to lists’

You are done and any user can add comments to your blog posts!!!

But wait, this may not work in cases where BLOG is set as a sub site under a publishing site.

This is because site collection is based on publishing portal and have a ‘ViewFromPagesLockdown’ feature. This feature prevents anonymous users from gaining access to certain areas of site. So, first check if ‘ViewFromPagesLockdown’ feature is enabled for the site.

To determine if a site has ‘ViewFromPagesLockdown’ enabled run the following in Powershell:

get-spfeature -site http://sitecollectionURL

If ViewFormPagesLockDown is listed, it’s enabled.

To toggle lockdown mode to off:

$lockdown = get-spfeature viewformpageslockdown

disable-spfeature $lockdown -url

Now re-set the anonymous access and try to add comments to a blog post without signing in. You can add comments!!!!

Thursday, 27 September 2012

Compare DateTime in XSLT

<xsl:template name="Webinar" match="Row[@Style='Webinar']" mode="itemstyle">


         <xsl:variable name="ACEndDate">
             <xsl:value-of select="ddwrt:FormatDateTime(@ToDate, 2057, 'yyyyMMddhhmmss')"/>
         </xsl:variable>

             <xsl:variable name="CurrentDate">
      <xsl:value-of select="ddwrt:FormatDateTime(string(ddwrt:Today()), 2057, 'yyyyMMddhhmmss')"/>
       </xsl:variable>

    <xsl:if test="$CurrentDate < $ACEndDate">

/////// do here for your data

</xsl:if>

</xsl:template>

Monday, 3 September 2012

SP Services (GetListItems , UpdateListItems )

How to hide Sharepoint 2010 ListItem fields in pages

Hide Sharepoint 2010 ListItem fields in pages

Add a link to Latest version of J Query to your page and add this script.

<script type="text/javascript" language="javascript">
$(document).ready(function() {
$("nobr:contains('My Field To Hide')").
parent('h3').parent('td').parent('tr').hide();
});

</script>

where "My Field To Hide" is the field name displayed in the form.

Converting Word Documents to PDF using SharePoint Server 2010 and Word Services

SharePoint 2010 Word Automation Services available with SharePoint Server 2010 supports converting Word documents to other formats. This includes PDF. This article describes using a document library list item event receiver to call Word Automation Services to convert Word documents to PDF when they are added to the list. The event receiver checks whether the list item added is a Word document. If so, it creates a conversion job to create a PDF version of the Word document and pushes the conversion job to the Word Automation Services conversion job queue.

This article describes the following steps to show how to call the Word Automation Services to convert a document:

Creating a SharePoint 2010 list definition application solution in Visual Studio 2010.
Adding a reference to the Microsoft.Office.Word.Server assembly.
Adding an event receiver.
Adding the sample code to the solution.

Creating a SharePoint 2010 List Definition Application in Visual Studio 2010

This article uses a SharePoint 2010 list definition application for the sample code.

To create a SharePoint 2010 list definition application in Visual Studio 2010

Start Microsoft Visual Studio 2010 as an administrator.
From the File Menu, point to the Project menu and then click New.
In the New Project dialog box select the Visual C# SharePoint 2010 template type in the Project Templates pane.
Select List Definition in the Templates pane.
Name the project and solution ConvertWordToPDF.

Figure 1. Creating the Solution
To create the solution, click OK.
Select a site to use for debugging and deployment.

Select the site to use for debugging and the trust level for the SharePoint solution.

Note:
Make sure to select the trust level Deploy as a farm solution. If you deploy as a sandboxed solution, it does not work because the solution uses the Microsoft.Office.Word.Server assembly. This assembly does not allow for calls from partially trusted callers.

Figure 2. Selecting the trust level

Creating the solution

To finish creating the solution, click Finish.

Adding a Reference to the Microsoft Office Word Server Assembly

To use Word Automation Services, you must add a reference to the Microsoft.Office.Word.Server to the solution.

To add a reference to the Microsoft Office Word Server Assembly

In Visual Studio, from the Project menu, select Add Reference.
Locate the assembly. By using the Browse tab, locate the assembly. The Microsoft.Office.Word.Server assembly is located in the SharePoint 2010 ISAPI folder. This is usually located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI. After the assembly is located, click OK to add the reference.

Figure 3. Adding the Reference

Adding an Event Receiver

This article uses an event receiver that uses the Microsoft.Office.Word.Server assembly to create document conversion jobs and add them to the Word Automation Services conversion job queue.

To add an event receiver

In Visual Studio, on the Project menu, click Add New Item.
In the Add New Item dialog box, in the Project Templates pane, click the Visual C# SharePoint 2010 template.
In the Templates pane, click Event Receiver.
Name the event receiver ConvertWordToPDFEventReceiver and then click Add.

Figure 4. Adding an Event Receiver
The event receiver converts Word Documents after they are added to the List. Select the An item was added item from the list of events that can be handled.

Figure 5. Choosing Event Receiver Settings
Click Finish to add the event receiver to the project.

Adding the Sample Code to the Solution

Replace the contents of the ConvertWordToPDFEventReceiver.cs source file with the following code.

using System;
using System.Security.Permissions;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Security;
using Microsoft.SharePoint.Utilities;
using Microsoft.SharePoint.Workflow;

using Microsoft.Office.Word.Server.Conversions;

namespace ConvertWordToPDF.ConvertWordToPDFEventReceiver
{
  /// <summary>
  /// List Item Events
  /// </summary>
  public class ConvertWordToPDFEventReceiver : SPItemEventReceiver
  {
    /// <summary>
    /// An item was added.
    /// </summary>
    public override void ItemAdded(SPItemEventProperties properties)
    {
      base.ItemAdded(properties);

      // Verify the document added is a Word document
      // before starting the conversion.
      if (properties.ListItem.Name.Contains(".docx") 
        || properties.ListItem.Name.Contains(".doc"))
      {
        //Variables used by the sample code.
        ConversionJobSettings jobSettings;
        ConversionJob pdfConversion;
        string wordFile;
        string pdfFile;

        // Initialize the conversion settings.
        jobSettings = new ConversionJobSettings();
        jobSettings.OutputFormat = SaveFormat.PDF;

        // Create the conversion job using the settings.
        pdfConversion = 
          new ConversionJob("Word Automation Services", jobSettings);

        // Set the credentials to use when running the conversion job.
        pdfConversion.UserToken = properties.Web.CurrentUser.UserToken;

        // Set the file names to use for the source Word document
        // and the destination PDF document.
        wordFile = properties.WebUrl + "/" + properties.ListItem.Url;
        if (properties.ListItem.Name.Contains(".docx"))
        {
          pdfFile = wordFile.Replace(".docx", ".pdf");
        }
        else
        {
          pdfFile = wordFile.Replace(".doc", ".pdf");
        }

        // Add the file conversion to the conversion job.
        pdfConversion.AddFile(wordFile, pdfFile);

        // Add the conversion job to the Word Automation Services 
        // conversion job queue. The conversion does not occur
        // immediately but is processed during the next run of
        // the document conversion job.
        pdfConversion.Start();

      }
    }
  }
}

Word Automation Services provided with SharePoint Server 2010 enables you to create server-based document solutions. Combining the functionality that is provided by Word Automation Services with the document content manipulation support provided with the Open XML SDK enables you to create rich document solutions that execute on the server that do not require Automation of the Word client application.

Examples of the kinds of operations supported by Word Automation Services are as follows:

Converting between document formats (e.g. DOC to DOCX)
Converting to fixed formats (e.g. PDF or XPS)
Updating fields
Importing "alternate format chunks"

This article contains sample code that shows how to create a SharePoint list event handler that can create Word Automation Services conversion jobs in response to Word documents being added to the list. This section uses code examples taken from the complete, working sample code provided earlier in this article to describe the approach taken by this article.

The ItemAdded event handler in the list event handler first verifies that the item added to the document library list is a Word document by checking the name of the document for the .doc or .docx file name extension.

// Verify the document added is a Word document
// before starting the conversion.
if (properties.ListItem.Name.Contains(".docx") 
    || properties.ListItem.Name.Contains(".doc"))
{

If the item is a Word document then the code creates and initializes ConversionJobSettings and ConversionJob objects to convert the document to the PDF format.

//Variables used by the sample code.
ConversionJobSettings jobSettings;
ConversionJob pdfConversion;
string wordFile;
string pdfFile;

// Initialize the conversion settings.
jobSettings = new ConversionJobSettings();
jobSettings.OutputFormat = SaveFormat.PDF;

// Create the conversion job using the settings.
pdfConversion = 
  new ConversionJob("Word Automation Services", jobSettings);

// Set the credentials to use when running the conversion job.
pdfConversion.UserToken = properties.Web.CurrentUser.UserToken;

The Word document to be converted and the name of the PDF document to be created are added to the ConversionJob.

// Set the file names to use for the source Word document
// and the destination PDF document.
wordFile = properties.WebUrl + "/" + properties.ListItem.Url;
if (properties.ListItem.Name.Contains(".docx"))
{
  pdfFile = wordFile.Replace(".docx", ".pdf");
}
else
{
  pdfFile = wordFile.Replace(".doc", ".pdf");
}

// Add the file conversion to the Conversion Job.
pdfConversion.AddFile(wordFile, pdfFile);

Finally the ConversionJob is added to the Word Automation Services conversion job queue.

// Add the conversion job to the Word Automation Services 
// conversion job queue. The conversion does not occur
// immediately but is processed during the next run of
// the document conversion job.
pdfConversion.Start();

The solution cannot be removed when a job is scheduled or running

The solution cannot be removed when a job is scheduled or running
Cancel Deployment when a error is occured like
The solution cannot be removed when a job is scheduled or running

Open command prompt and enumerate the running deployments by executing this command:
stsadm -o enumdeployments

then iisreset

Now, we obtain the jobid and cancel this deployement as follows:
stsadm -o canceldeployment -id 2529c788-971c-46a3-b69f-a2a0a1fcc851
That's it. We can then retract and delete the solution.