Pages

Monday, November 5, 2012

Add and Remove Doc Library in SharePoint 2013


Introduction

In this article we will see how to add and remove a document library in SharePoint 2013 Sites.

Steps

We go to the site's home page and click the "Site Content" link from the quick launch menu.
Image 1.jpg

Then it'll display the list of apps we can add to our site, as in:

Image 2.jpg

There are two options for adding apps to your site.

Option 1

We can directly click the App icon or Tile to add the particular app into our site, then click the Document Library.
Image 3.jpg

Option 2

Click the "App Details" link; it'll redirect to the App Detail page and add the app.
Image 4.jpg

Both the preceding options redirects to the Document creation page, fill in the input and add the library.
Image 5.jpg

If we click the "Advanced Options", notice that the Document Library "List Template ID=101" as a query string is in the page URL. Microsoft may call it an App but still it internally maintains the basic structure.
Image 6.jpg

The same page in SharePoint 2010 looks like in the following page, it's based on Silverlight.

Image 7.jpg
Fill in the values and create a Document Library.

Image 8.jpg
 
Image 9.jpg

Now if we go to the Site Contents page, we will see the newly created Document Library.
Image 10.jpg

If we want to delete the Document Library then simply click the top-right "More info" link or click the App icon or Tile, it'll open a popup with the "Remove" option.
Image 11.jpg

Once we click the "Remove" button, we will get the following alert message and if we select OK, the document library will be deleted.
Image 12.jpg

Summary

We have learned how to add and remove a document library in a SharePoint 2013 site.
 

Windows Store App (Metro UI) Design in SharePoint 2010


Objective

We want to implement the Windows Store App (Metro UI) themes in our SharePoint 2010 pages.

Steps

We are not going develop the CSS and pages from scratch. We will try to implement the code project solution file for CSS and design.

Site Link

http://www.lifeinsharepoint.co.uk/2011/12/03/metro-ui-sharepoint-2010-masterpage-solution/

CodePlex Link

http://lifeinsharepoint.codeplex.com/releases/view/78033

First download the WSP file and install it in the SharePoint Server. We can use the PowerShell command to simplify the process.

Add Solution

Add-SPSolution c:\solutionpath\LifeInSharePoint.Metro.wsp

Deploy Solution

Install-SPSolution -Identity LifeInSharePoint.Metro.wsp -WebApplication http://myprojectsite -GACDeployment

Once it's successfully deployed, we can check the deployment files in 14 hive path as mentioned in the following path.
Install-SPSolution –Identity-LifeInSharePoint.Metro.jpg

Go To -> Site Collection Administration -> Site collection Features; we can see the installed feature with the name "SITE.LifeInSharePoint.Metro"

SITE.LifeInSharePoint.Metro.jpg

Before we activate the feature, we will see the following design for sites and pages.

activate-the-feature-Windows-Store-App.jpg

Site Collection Admin page looks like the following page:

Site-Collection-Admin-page.jpg

Activate the feature, make sure site collection's publishing feature is already activated in the site collection.

SITE.LifeInSharePoint.Metro1.jpg

As soon as the feature has activated, we will immediately make the design (UI) changes.

Site-Collection-Administrator.jpg

The entire site's design has changed to that of a Windows Store App (Metro UI):

sites-design-changed-to-Windows-Store-App.jpg

Summary

Creating a SharePoint site in Windows Store App (Metro UI) is fun. Still we are using the CodePlex tool; we will understand the basic design principles behind the scene.

UI Design Principle

http://msdn.microsoft.com/en-us/library/windows/apps/hh464920.aspx 

Hide Top Level Menu and Ribbon Programmatically in SharePoint 2010


Introduction
In this article we will see how to hide a top level menu and ribbon programmatically in SharePoint 2010.
Steps: Let's assume that we have a site page with top-level navigation menus and Ribbon Controls.
Go to a site pages and add new page.
Add-New-Page-in-SharePoint.jpg
Once the page is created, if we click the page we are able to see the page with the top-level navigation menu with ribbon controls.
Top-level-navigation-menu-with-ribbon-control-in-SharePoint.jpg
Before we edit the site page, we need to save the following code in Shared Documents.
Code
<style type="text/css">
  #s4-leftpanel-content{        display:none;}   #s4-ribbonrow
{        display:none;}   #s4-titlerow{        display:none;}   #s4-workspace  {         overflow-yhidden !important;  }</style> 
We need to save this code in the shared documents as a text file as shown in the following:
document-as-text- file-in-SharePoint.jpg
Now we can start the edit pages.
Go to à Site Actions à Edit Page.
Edit-page-in-SharePoint.jpg
Edit-page-in-SharePoint(Image4)
Once we are in Edit Page Mode, just select the two columns layout this demo.
Text-Layout-option-in-sharePoint.jpg
Just click the second column and add a content editor web part:
contend-editor-in-SharePoint.jpg
editing-tool-in-SharePoint(Image7).jpg
Once it's added, click the Edit web part and select the above share document in the content link.
editing-tool-in-SharePoint.jpg
Content-editor-in-SharePoint.jpg
That's all our page will load with the following UI Changes:

page-in-SharePoint.jpg
We will see the content editor in our page that's not required to view in page content. We will again edit the content editor web part and set the "Chrome Type" to "None".
Content-editor-Option-in-SharePoint.jpg
Finally the page looks like the following image:
page-looks-in-Sharepoint.jpg
The preceding steps need to be followed for site pages, but if added for a web part page, we will see how easy it is to hide the Ribbon and navigation controls.
Site-page-in-SharePoint.jpg
Just create a web part page template, select the options which we want and create the page.
page-template-in-SharePoint.jpg
In the web part page, we have various options to inject our HTML code.  We can add "HTML Form Web Part" or using the "Content Editor Web part". We will see both options.
Select content "HTML Form Web Part". In the Edit web part mode just copy the above code in the Source Editor and save it.
HTML-Form-Web-Part-in-Sharepoint.jpg
HTML1-Form-Web-Part-in-Sharepoint.jpg
We will set the chrome type to "None" to hide in the UI.
Select-Hide-from-crome-type-in-sharepoint.jpg
We will see the output as shown in the following image, just added the default announcements list for demo.
announcements-in-sharepoint.jpg
Let's see how we can get the same result using the "Content Editor" web part. Go to the web part page edit mode, delete HTML form editor and add the using "Content Editor" web part.
delete-HTML-Form-editor-in-sharepoint.jpg

delete1-HTML-Form-editor-in-sharepoint.jpg
In the web part page, just click the "Click here to add new content" link and select HTML and Edit HTML Source option from the ribbon.

Edit HTML Source-In-sharepoint.jpg
Now we can add our code, save the changes and refresh the page and we will get the final output.

output-In-sharepoint.jpg
Summary
We have seen various options to hide a top level menu and ribbon programmatically in SharePoint 2010. If we add the same code in a Master Page using the SharePoint 2010 Designer, we will hide controls in the entire pages.

Tuesday, October 2, 2012

SharePoint 2013 UserProfile Properties Overview

Introduction

In this article we will see the SharePoint 2013 User Profile Properties and their uses in detail.

Step 1

Once we have configured and installed the SharePoint 2013, we will go to Central Administration (CA) as shown in the following URL:

installed-the-SharePoint2013.jpg

We will select the user profiles; see the list of configured profiles as similar to the SP 2010 pages.

Step 2

Now click the "Manage User Profiles" link, it will redirect to the profile search page.

Manage-User-Profiles.jpg

Step 3

Select the user name from the result; it will load the profile page.

Select-the-user-name.jpg

Step 4

We will see all the new properties that are available in a 2013 user profile compared to SharePoint 2010.

properties-sharepoint2013.jpg

We are able to follow #Tags and posts; these #tags will update automatically in our News Feed.

Tags-and-posts.jpg

We will get the preceding validation message, if we have not enabled the "Tag Service". There is a known issue in SharePoint 2013 online version.

http://office.microsoft.com/en-us/office365-suite-help/office-365-known-issues-HA102919011.aspx?CTT=5&origin=HA102919021#_SharePoint_Online 

There is some changes in Email Notifications properties compared to SP 2010 , because in news feed we have additional social features "like", "AtMention","Follow","Reply" options.

SharePoint 2010 Email Notification optionsSharePoint 2013-Email-Notification-options.jpg

SharePoint 2013 Email Notification optionsEmail-Notifications.jpg

Related follow option we have the following options in the user profile:

options-in-user-profile.jpg

We can control the data which flows to the News Feed, the system administrator will decide which activities will appear in this List.

flow-to-News-feed.jpg


SP 2013 has the option to set the Language preferences for individual users:

SP2013-options.jpg

We can see some of the other options available in a User Profile:

other-options-in User-Profile.jpg

Summary

The preceding properties are additional or new as compared to SharePoint 2010.