Thursday, June 25, 2015

What can we do with SharePoint Designer 2013?


Following is the high level list of features and functionality that we can do using SharePoint Designer 2013
1.      Edit Site
a.      Create list/libraries/Sites
b.      Create site pages
c.      Create Web Part Pages
d.      Create/edit Master pages
f.       Copy/move/delete items
g.      Create content types/columns/external content types/site assets
h.      Site Groups
2.      Create Workflows
a.Workflow Actions
         Dictionary actions
         Coordination actions
         Task Actions
         Eventing Actions
b. List Workflow
b.      Reusable Workflow
c.      Site Workflow
d.      Package workflows
e.      Loops in Workflow



3.      Create external Data sources

5.      Call REST Web Services


Thursday, June 11, 2015

SharePoint installation types/modes

Overview

Currently, the installation types include single server with built-in database installations, single-server farm installations, and multiple-server farm installations. This document describes the advantage and disadvantage with each installations in SharePoint.

Installation mode

Multiple-server farm installations

            A farm configuration consists 2 or more server. While the farm configuration is not complex, it provides a fundamental infrastructure to implement a SharePoint solution on similar or more complex farms.
            In terms of performance, capacity, and scalability, a three-tier topology is recommended over a two-tier topology. A three-tier topology provides the most efficient physical and logical layout to support scaling out or scaling up, and provides better distribution of services across the member servers of the farm.

Single-server farm installations

            A single server farm generally consists of one server that runs both SharePoint and Microsoft SQL Server. You can deploy SharePoint in a single server farm environment if there are only few sites required for a limited number of users.  This configuration would be useful if you want to configure a farm to meet your requirements first, and then add servers to the farm at a later stage whenever required.

Single server with built-in database (Standalone)

            A single server installation consists of one server that runs both SQL Server and SharePoint. You can install and configure SharePoint on a single server if you are creating only few application for a limited number of users or if you want to create a trial or development environment. This deployment uses SQL Server Express.

Restrictions

·         You cannot use this method on a domain controller or in a workgroup environment.
  • This method is not supported for production on a domain controller.
  • If your computer is in a workgroup, you cannot install AppFabric for Windows Server.
·         This installation, using Microsoft SQL Server 2008 R2 SP1 Express Edition, the maximum database size is 10 GB
·         Cannot add another server in future
·         No Domain Service, because it is configured only in one server and it runs under local accounts like Network Service account. Also you cannot create User Profile Service for this reason.

Summary

            If you choose ‘stand-alone’ installation type, you cannot change it back to ‘Farm’ and you would then be permanently unable to add additional machines (such as a separate Web Front End, SQL etc.). You may need to do a SharePoint re-installation to convert that to Farm environment. Also database size is limited and cannot be extended for standalone installation with build in database. So the recommended installation for Web Framework would be to select between “Multiple server farm installations” or “Single server farm installation” measured against expected user activity.

Saturday, May 30, 2015

SharePoint 2013 Samples using Visual Studio 2012

Environment: Visual Studio Professional 2012, SharePoint Server 2013 Enterprise
SharePoint 2013 Code samples are available in Visual Studio 2012. There are lot of online sample available and can be retrieved from Visual Studio tool. Sample codes includes JavaScript, Visual Basic, Visual C#, Visual C++, Visual F# etc.
  1. Open Visual Studio 2012 > Help > Samples
  1. Search for SharePoint related samples online
  1. On clicking Ok button after providing the necessary information in the New Project dialog, the online sample will be downloaded to your Visual Studio.
  2. Navigate to the Installed section and select the downloaded sample to create the project

  1. Build and deploy your app to SharePoint.


Thursday, May 7, 2015

SharePoint products configuration wizard failed

Environment: SharePoint 2013 Foundation

Requirement: Uninstall existing SharePoint 2013 Enterprise and Install SharePoint 2013 Foundation

Issue: After uninstalling the existing SP2013 and successful 2013 Foundation installation, the installation failed during running SharePoint products configuration wizard. It failed at the step 8 of 9 throwing following error message.
Configuration failed.
One or more configuration settings failed. Completed configuration settings will not be rolled back. Resolve the problem and run this configuration wizard again. The following contains detailed information about the failure.
Failed to upgrade SharePoint Products
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: Failed to upgrade SharePoint Products

Resolution:

As it turns out to be insufficient SQL Server database permissions. Also noticed that the SharePoint timer job was running with Network Credentials account.

Following are the steps involved to resolve this issue.
  1. In Central Administration Web site, click Security > Configure Service Accounts.
  2. In Credential Management section, select the Web application pool for your Web application.
  3. In the Select an account for this component section, select the service account that you want to associate with this Web application pool, or click Register new managed account to associate a new service account with this application pool.
  4. Click OK
  5. Update the SharePoint timer job service to run on the same service account.

Tuesday, March 24, 2015

Enable Auditing for a specific document library and list.


Environment: SharePoint 2013 Enterprise
Requirement:
  • Enable audit for a document library to get the number of times the document is opened
  • Enable audit for a list to get the total number of times the item is edited.
Solution/Steps:
  1. Go to Document library > Settings > Library Settings
  2. Click Information management policy settings
  1. Click on Document under Content Type
  2. Provide the necessary details and select “Opening or downloading documents, viewing items in lists, or viewing item properties” under Enable Auditing
  1. Click OK
  2. Navigate to the list where you want to set the policy
  3. Click List Settings > Select Information management policy settings

  1. Select the List from the policy settings
  2. Provide the required details and select Editing items under Enable Auditing

  1. To view the report, navigate to the top level site and Site Settings
  2. Select Audit log reports under Site Collection Administration

  1. Click Run a custom report under Custom Reports section

  1. Select the required events to view the report for

  1. Click Ok
  1. Click on “Click here to view the report”


Note: Site collection administrators page views or edit are not tracked.

Wednesday, March 18, 2015

Create and associate multiple content types for a library

Environment: SharePoint 2013
Requirement: Create multiple content types for a document library to have different metadata/columns.
Introduction: The following steps are to create sample content types to store Budget and Invoice details in a document library.
Solution:
Create a site content type named ’Budget’. The parent content type can be selected based on the requirement. For example, if you are settings this for a document library then use Document Content Type as parent and if you setting this for a list, then select List content type.


Add columns that are specific to the created content type.
Create another content type named ‘Invoice’
Add columns that are specific to Invoice content type.




Navigate to the document library where you want to associate this content type.
Click Library > Library Settings > Advanced Settings and allow management of content type.


Associate the Budget and Invoice content types to the library in Library Settings page.


After associating the content types, you can see the content type column when you add a new item in the document library. The column that are created for each content type will get displayed based on the 
content type you select.


Upload document and submit metadata for different content types.