SharePoint Tutorial PDF Version Quick Guide Resources Job Search Discussion This tutorial will give you an idea of how to get started with SharePoint development. Microsoft SharePoint is a browser-based collaboration, document management platform and content management system. After completing this tutorial, you will have a better understating of what SharePoint is and what are the high-level feature areas and functionalities of SharePoint. Audience This tutorial has been prepared for anyone has an urge to develop websites and Apps. After completing this tutorial you will find yourself at a moderate level of expertise in developing websites and Apps using SharePoint. Prerequisites Before you start proceeding with this tutorial, we are assuming that you are already aware about the basics of Web development. Print Page Previous Next Advertisements ”;
Category: sharepoint
SharePoint – Libraries
SharePoint – Libraries ”; Previous Next In this chapter will be covering libraries. Libraries are just a special case of a list. They inherit all the characteristics of a list. Therefore, all the characteristics we have seen so far, apply to libraries just as they do to lists. Difference between List and Library Though Lists and Libraries exhibit similar characteristics, following are the differences − The major difference is that in a library, each row is associated with a document. This document can be of any kind. For example, office documents, pictures, web pages, Word Perfect documents etc. The advantage of using Office documents is that there is an integration with the actual Office tools themselves. The other difference is more a difference in terminology rather than functionality. For example, the columns in a library mean the metadata associated with the document. Creating a Document Library In this section, we will see the basics of working with document libraries. You can create a document library in much the same way as you have created a list. Follow the steps given below. Step 1 − Go to Site Contents and then click “add an app”. Step 2 − Click Document Library. Give the library a name and click Create. Note − Here, we will learn about advanced options. Step 3 − Click the Advanced Options and name the document library, Course Documents. We also have the option to set a version here, but I suggest do not set a version because same options are not available in library settings. However, if you want the version control on, do it in the library settings, not here. Finally, we have the option to say what kind of document we want to be the default template. We will select Word, and click Create. Step 4 − Now before we add documents, we need to add a couple of columns or fields. Go to the Library option on the ribbon and click Library Settings. Step 5 − Add a new column and this column will be the course that will appear in the lookup field in the list of Courses. Click OK. Step 6 − Let us add one more column. We will name this column as Number and set the type to number. Set the minimum and maximum values i.e. 0 and 100 respectively, and click OK. You can see that the schema is ready. Add a Document to Library Now that we have the schema ready, we can add some documents. One way to add a document is to create it right here within SharePoint. Step 1 − Now let us to go to the Files tab in the ribbon. Click New Document. Step 2 − You will see that Word is open and here we are able to edit the contents of the document. Step 3 − Write some text in the open word page. The document is saved automatically, now let us go back to the site and you will see that the word document is created. Step 4 − To edit the values of the metadata fields, click the little ellipses. Select the ellipses again on Document.docx dialog box and select Rename from the options. Step 5 − Enter the required information and click Save. Another way we can add a document to a document library is to upload it. Step 6 − You can upload it using New Document here. Step 7 − You can also go to the Files tab on the Ribbon and click Upload Document. Step 8 − You will see the following dialog box. Click Choose Files. Step 9 − Select a sample file. Click Open. You will see that the sample document is added to the library list. Step 10 − If you want to upload multiple documents, you can drag and drop them. Multiple documents will be uploaded. Once the uploading is finished, you will see these documents in the list. Step 11 − Another way to set the metadata is under the Library tab, click the Quick Edit option on the ribbon. Step 12 − metadata is set, click View on the ribbon to go back to the standard list view. You will see the document files is the list as seen in the following screenshot. Print Page Previous Next Advertisements ”;
SharePoint – REST APIs
SharePoint – REST APIs ”; Previous Next In this chapter, we will be covering the REST APIs. This is not a traditional API, where we have a set of libraries that contain types and those types contain properties and methods. The REST API is implemented as Data-centric web service based on the Open Data Protocol or OData. The way these web services work, use each resource in the system is addressable by a specific URL that you pass off to the server. Let us look at this in Internet Explorer in which SharePoint site is open. Step 1 − If you are using Internet Explorer, go to Internet Explorer settings and on Content tab, select the settings for Feeds and Web Slices as shown in the screenshot below. You will see the following dialog box. Make sure feed reading view is off and click OK. Step 2 − Now let us change the URL to the site URL +/_api/web and press Enter. Now you should get a view that looks like the following screenshot. We want information about the current web or the current site. Therefore, the site URL +/_api is the base URL for the SharePoint 2013 REST API and web is our query. We want information about the current web. We get an XML document back and if we scroll down, we will get information about our current web. Next, if you want to know about the lists in the web, you can append the lists to your URL. Instead of information about an individual object, we will get a collection of information about all of the lists in the current site. When we were using the browser, we were issuing get requests to the server, which means we want to retrieve information. However, we can also do the rest of the standard CRUD operations. Retrieve Resources using REST API The SharePoint 2013 REST API does not expose metadata. Therefore, when we are working with it in Managed Code, we cannot use Visual Studio to generate a service proxy using the service reference dialog. Instead, we can use a type like the web client of the http web request object to send a request up to the server and just get the raw results back. Whether those results are returned as XML or JSON are determined by the accept header we send along with the request. If we get back XML then we can use LINQ to XML to retrieve the information out of the response we need for our application. If we get back JSON, then we can use one of the various JSON serializes to parse the JSON into .NET objects and then use that to retrieve the information we need. When working with the REST API in JavaScript, we can use jQuery or the SP.RequestExecutor object to make the call up to the service. Just as in the Managed Code example, we can control whether we get back XML or JSON using the accept header. Since, we are working in JavaScript majority of times, we are going to want to get back JSON. The one other thing to note is when you are building the URL to the service, we can use the _spPageContextInfo object to get the absolute URL from the site and then just append the service URL plus the query to it. This is because the REST API service does not expose metadata and you cannot create a service reference in Visual Studio, using the REST API in Managed Code is really a non-starter. Let us take a look at calling the REST API from JavaScript by creating a new project. Step 1 − Select App for SharePoint in middle pane and enter name for your project. Click OK. Step 2 − Enter your site URL and select the SharePoint – hosted option and click Next. Click Finish. Step 3 − Once the project is created, let us open the Default.aspx page, which is under Pages in Solution Explorer and add one button. Here is the complete implementation of the Default.aspx file. <%– The following 4 lines are ASP.NET directives needed when using SharePoint components –%> <%@ Page Inherits = ”Microsoft.SharePoint.WebPartPages.WebPartPage, Microsoft.SharePoint, Version = 15.0.0.0, Culture = neutral, PublicKeyToken = 71e9bce111e9429c” MasterPageFile = ”~masterurl/default.master” Language = ”C#” %> <%@ Register TagPrefix = ”Utilities” Namespace = ”Microsoft.SharePoint.Utilities” Assembly = ”Microsoft.SharePoint, Version = 15.0.0.0, Culture = neutral, PublicKeyToken = 71e9bce111e9429c” %> <%@ Register TagPrefix = ”WebPartPages” Namespace = ”Microsoft.SharePoint.WebPartPages” Assembly = ”Microsoft.SharePoint, Version = 15.0.0.0, Culture = neutral, PublicKeyToken = 71e9bce111e9429c” %> <%@ Register TagPrefix = ”SharePoint” Namespace = ”Microsoft.SharePoint.WebControls” Assembly = ”Microsoft.SharePoint, Version = 15.0.0.0, Culture = neutral, PublicKeyToken = 71e9bce111e9429c” %> <%– The markup and script in the following Content element will be placed in the <head> of the page –%> <asp:Content ContentPlaceHolderID = ”PlaceHolderAdditionalPageHead” runat = ”server”> <script type = ”text/javascript” src = ”../Scripts/jquery-1.9.1.min.js”></script> <SharePoint:ScriptLink name = ”sp.js” runat = ”server” OnDemand = ”true” LoadAfterUI = ”true” Localizable = ”false” /> <meta name = ”WebPartPageExpansion” content = ”full” /> <!–Add your CSS styles to the following file -> <link rel = ”Stylesheet” type = ”text/css” href = ”../Content/App.css” /> <!–Add your JavaScript to the following file -> <script type = ”text/javascript” src = ”../Scripts/App.js”></script> </asp:Content> <%– The markup in the following Content element will be placed in the TitleArea of the page –%> <asp:Content ContentPlaceHolderID = ”PlaceHolderPageTitleInTitleArea” runat = ”server”> Page Title </asp:Content> <%– The markup and script in the following Content element will be placed in the <body> of the page –%> <asp:Content ContentPlaceHolderID = ”PlaceHolderMain” runat = ”server”> <div> <p id = ”message”> <!–The following content will be replaced with the user name when you run the app – see App.js -> initializing… </p> <input id = ”loadButton” type = ”button” value = ”Load” /> </div> </asp:Content> Step 4 − Open the App.js file, which is under Script in Solution Explorer and replace it with the following code. JQuery(document).ready(function () { JQuery(“#loadButton”).click(usingLoad) }); function usingLoad()
SharePoint – Resources
SharePoint – Useful Resources ”; Previous Next The following resources contain additional information on SharePoint. Please use them to get more in-depth knowledge on this topic. Useful Video Courses SharePoint Framework SPFx from Zero to Hero | Get Hired 14 Lectures 3 hours Darwish More Detail Microsoft Teams for IT – Complete Course 23 Lectures 4 hours Fabrice Chrzanowski More Detail The Complete Microsoft SharePoint MasterClass Featured 123 Lectures 6.5 hours Jan Ekhteyari More Detail MS-900 Exam: Microsoft 365 Fundamentals Video Course 86 Lectures 11.5 hours Eshant Garg More Detail Microsoft Sharepoint – Organize Cooperation in Groups 23 Lectures 1.5 hours Sonic Performance More Detail Implementing eDiscovery in SharePoint 28 Lectures 3.5 hours Stone River ELearning More Detail Print Page Previous Next Advertisements ”;
SharePoint – Quick Guide
SharePoint – Quick Guide ”; Previous Next SharePoint – Overview This tutorial will give you an idea of how to get started with SharePoint development. Microsoft SharePoint is a browser-based collaboration, document management platform and content management system. After completing this tutorial, you will have a better understating of what SharePoint is and what are the high-level feature areas and functionalities of SharePoint. What is SharePoint SharePoint is a platform to support collaboration and content management system. It is a central web-based portal. Using SharePoint, you can manage your colleague’s and your own documents, social activities, data, and information. It allows groups to set up a centralized, password-protected space for document sharing. Documents can be stored, downloaded and edited, then uploaded for continued sharing. SharePoint offers such a wide array of features that it is very challenging for any one person to be an expert across all the workloads. Let us understand what all can we do with SharePoint. It is divided into three separate areas − Collaboration The term collaboration contains a very strong theme for SharePoint. It means bringing people together through different types of collaboration, such as enterprise content management, Web content management, social computing, discoverability of people and their skills. In SharePoint 2013, collaboration is managed through Apps. Developers can extend, customize, or build their own Apps for SharePoint as well manage collaboration on SharePoint. Interoperability SharePoint is also about bringing this collaboration together through interoperability such as − Office and web-based document integration. Capability to build and deploy secure and custom solutions that integrate line-ofbusiness data with SharePoint and Office. Integrating with wider web technologies, or deploying applications to the cloud. Platform SharePoint is also a platform that supports not only interoperability and collaboration but also extensibility, through a rich object model, a solid set of developer tools, and a growing developer community. One of the key paradigm shifts is the notion of the cloud in SharePoint. The cloud introduces new App models such as − New ways of developing, deploying, and hosting SharePoint applications. New forms of authentication through OAuth. New ways of data interoperability using OData and REST. SharePoint – Types In this chapter, we will be covering the different types and versions to start working on SharePoint. There are three main ways to install and use SharePoint − SharePoint Foundation SharePoint Server Office 365 The first two options are SharePoint on-premise, while Office 365 has emerged as a third, fully cloud-hosted model for SharePoint. SharePoint Foundation SharePoint Foundation is the essential solution for organizations that need a secure, manageable, web-based collaboration platform. SharePoint Foundation provides you with the basic collaboration features that are included within SharePoint. SharePoint Foundation ships as a free, downloadable install and represents the foundational parts of SharePoint. It includes a number of features such as security and administration, user and Team site collaboration, and a number of Apps (such as document libraries and lists). In essence, it provides a baseline set of features that enable you to get started with both using and developing for SharePoint. SharePoint Foundation requires some features to build standard collaboration and communication solutions within your organization. The primary features of SharePoint Foundation revolve around document management and collaboration. Key Features of SharePoint Foundation Following are some of the major features, which are responsible for its wide adoption in businesses. Effective document and task collaboration − Team websites offer access to information in a central location. Reduced implementation and deployment resources − SharePoint Foundation is available to Windows Server customers as a free download, with the help of which implementation time and cost are greatly reduced. Better control of your organization’s important business data − SharePoint Foundation also offers features for data and information management and security. Embrace the web for collaboration − By extending and customizing SharePoint Foundation In short, SharePoint Foundation represents the core content storage and collaboration features of SharePoint. It is the ideal edition for teams and small organizations looking to improve on their ability to work with one another in a secure, easy-to-use, collaborative workspace. SharePoint Server SharePoint Server offers a wealth of features that extend upon those offered in SharePoint Foundation. It provide a richer, more advanced collection of features that you can utilize in your organization’s solutions. Key Features of SharePoint Server Some of these additional features are described in the following list − Advanced Search − The search features and functionality features available within the Server versions offer more flexibility. They allow customized Search Results pages that you can configure with customized search Web Parts. Web Content Management − SharePoint Server supports web content creation and publishing for the internet. Enterprise Services − These services provide ways for you to build custom solutions quickly and easily using tools that are available to you within the Office product family. Business Connectivity Services − Business Connectivity Services (BCS) enables you to connect to these external data sources and display business data via Web Parts, user profiles, or SharePoint lists. Social Networking and Computing − Social networking is everywhere and has become an expected feature set of many solutions. Records management − SharePoint Server provides excellent support for the management of content throughout its entire life cycle. Office 365 Office 365 has emerged as a third, fully cloud-hosted model for SharePoint. It is the alternate option to hosting your own farm in your own on-premises Data Center. Key Features of Office 365 The options for licensing SharePoint Online through Office 365 are based on factors such as the number of users you want to add, the amount of data you need to store, and the features you need to be available. It has also become a great place where you can develop rich applications (both as SharePoint-hosted and cloud-hosted apps) and scale without the cost of managing the on-premises infrastructure. It does not have all the same services and features as SharePoint Server, but does carry with it some great development capabilities. There are .NET
SharePoint – Additional List Functionality ”; Previous Next SharePoint provides a lot of functionality for lists. It provides storage for the list data, the ability to customize the list schema, and the ability to view, add, edit, and delete list items etc. There are a lot more functionality available like creating views on list data, simple validation at both the field and list level, content approval, item versioning etc. Views Let us start working with Views on list data. Here we are back in the Authors list, and as you notice, that we have added only four items. With only four items, it is not hard to garner any information we need out of its data. As the number of items grows, say from 4 to 50 to 100, to maybe 500, it becomes increasingly more difficult to just glance at the list and quickly get the information that we need. To address this issue, SharePoint enables you to create multiple Views on lists, so that we can filter out information we do not need, such as − We can sort the field values. We can group information. We can get totals. We can also have different ways to present the information. For most lists, when you create them, you get one View by default. It is called the All Items View and that is the view we have seen in the example given above. Now let us have a look at how we can create custom views. Just as with the creation of the list schema, SharePoint gives us a couple of different ways we can use to create views. One way is to start with an existing view and change the sorting and filtering of different columns. We can get the data the way you want it to look, and then save it as a new view. You will notice that if we go to the other column headers, most of them give us a little drop-down menu we can access as shown below for Salary/Rate header. Go to the other column header- Bio. It does not have a dropdown list as it contains multiple lines of text. The other columns have this option. It gives us the ability to sort the information, or to filter it. Let us create a filter here that only shows Employees. Once we add that filter, notice there is a little icon in the column header that indicates that these field values have been filtered. Let us sort it in descending order. So now we have a new view of the data i.e. the descending order view. Now the filtering and sorting is not preserved. Therefore, we need to save the descending order view for future. If we just navigate back to the Authors list, then we will see All Items. If we want to have a view that is only Employees, sorted by Salary/Rate descending, click SAVE THIS VIEW option. We will call this view the Employees view. Select from the options given whether this view should be available to all users or just to me. Click Save. So now we have the two different views, All Items view and Employees view, we can switch between these views using the links at the top of the List view as shown in the screenshot given below. Validation We will be adding simple validation rules to fields and items in a SharePoint list. Now when we created the Authors list, we added some validation rules using the properties of the different field types. Click New Item from the Author’s list. Now, click Save. When you click Save, you will get two errors. This is because we have indicated that Name and Salary/Rate are required fields. Enter the name and Salary/Rate as Aamir Jameel and 1500 respectively. Click Save. As you can see we still have an issue with Salary/Rate, because when we created the field we indicated that its value should be between 0 and 1000, and 1500 does not satisfy that requirement. Click Cancel. Go to the List tab on the Ribbon and then click List Settings. Click Name. As you can see in the screenshot given below, it a required field, Now go back, click Salary/Rate, and scroll down. You will see that it is also a required field. Here we have also set the valid range of values. So, it is all good if the field type has these properties, but what do you do if it does not? Well, we can add in some simple custom validation. So if we scroll down to the bottom, you can see there is an area for column validation. Let us expand that. Here we can specify a formula and then give a message if the value entered by the user does not satisfy that formula. If you are not familiar with building formulas in SharePoint, there is a link which gives you help on how to do that. Now the validation that we want to add is that if you are not an employee, then your Salary/Rate indicates your hourly rate and we want to say that the maximum value for the rate is $50.00. So here, the validation depends on both the value of the Employee field and of the Salary/Rate field. Therefore, instead of adding the validation to either of those fields, we are going to add it to the item and then the way we indicate the item validation is by going to the List Settings. Click Validation Settings and set the formula as shown below. So the condition is going to be pretty simple, first, are you an employee? So if you are an employee, then we already set the valid range of salary values between 0 and 1000. Therefore, only True value is returned. If you are not an employee, then we will check if the Salary/Rate is less than or equal to 50. If this formula returns True, then the item is
SharePoint – Sandbox Solutions ”; Previous Next In this chapter, we will be covering the deployment of Sandbox Solutions. Deployment of a Sandbox Solution is quite simpler than deployment of a Farm solution. It is similar to uploading a document to a document library. When you finish your development, you are going to take the solution package and instead of giving it to your SharePoint administrator, you will give it to an end user, someone with site-collection owner privilege. Then they will take the package and upload it to the site-collection solution gallery. Just like with Farm solutions, the tools in Visual Studio automate this deployment process, during development. Let us have a look into a simple example of Sandbox Solution Deployment. It is quite simpler than Farm solution deployment. Step 1 − Here we need to create a new site collection and call it Demo 1. Step 2 − Change Contacts list name back to just Contacts in FeaturesAndElements project. Step 3 − Retract the solution by right-clicking on the project and choosing Retract. If we come back to the SharePoint system folders, you will notice that our Feature folder is absent. Next, if we go to Manage site features, we should not see Sample Feature. Step 4 − Go back to Visual Studio project, click the project in the Solution Explorer and then go to the properties window. Change Sandbox Solution from False to True. A warning dialogue is displayed. This gives us an indication that some of the items you added to the Visual Studio project will not work with Sandbox solutions and some of the SharePoint APIs. Some of the types within the SharePoint Server Object Model, are not compatible with Sandbox solutions. Click Yes to make the change. In this case, building a sandbox solution is the same as building a farm solution, but the deployment process is completely different. With the sandbox solution, instead of deploying files up into the SharePoint system folders, we deploy into the SharePoint content database. Step 5 − Go to the Site settings. Under the Web Designer Galleries, there is Solutions gallery. Step 6 − Click the Solutions link and you will see the following page where we deploy our sandbox solutions. You are done with the development. Instead of giving the solution package to the SharePoint administrator and then having them use PowerShell or Central Admin to deploy the Farm solution, you can give your package to an end user, someone with site-collection owner privilege and then they can upload the solution into the Solution gallery. Step 7 − Go back to Visual Studio, right-click and select Publish to File System. Click the Publish button to publish the New Solution Package to the package folder. You will see the package in the Package folder. Step 8 − Now go to the SharePoint site. Click the Upload Solution button option on the Ribbon. Step 9 − Browse to your FeaturesAndElements solution. Click OK. You will see the following dialogue. Step 10 − You just need to click the Activate button to activate the sandbox solution Step 11 − Go to the Manage site features. You will now see your Sample Feature and when you click Activate, you should get the same behavior as we had seen before. Print Page Previous Next Advertisements ”;
SharePoint – FeatureEvent Receiver ”; Previous Next In this chapter, we will learn to add code handle. Code handles are events that are raised when a Feature is activated or deactivated. In other words, we will be examining Feature Receivers. The Visual Studio project that we created in the last chapter had one Feature and when it was activated, it provisioned our Contacts list, our SitePage, and the link to the SitePage. However, when the Feature is deactivated, SharePoint only removes the link, the SitePage and the Contacts list still remain. We can write the code when the Feature is deactivated to remove the list and the page, if we want to. In this chapter, we will learn how to remove content and elements, when a Feature is deactivated. To handle the events for a Feature, we need a Feature Receiver. Step 1 − To get Feature receiver, right-click on the Feature in the Solution Explorer and then choose Add Event Receiver. using System; using System.Runtime.InteropServices; using System.Security.Permissions; using Microsoft.SharePoint; namespace FeaturesAndElements.Features.Sample { /// <summary> /// This class handles events raised during feature activation, deactivation, installation, uninstallation, and upgrade. /// </summary> /// <remarks> /// The GUID attached to this class may be used during packaging and should not be modified. /// </remarks> [Guid(“e873932c-d514-46f9-9d17-320bd3fbcb86”)] public class SampleEventReceiver : SPFeatureReceiver { // Uncomment the method below to handle the event raised after a feature has been activated. //public override void FeatureActivated(SPFeatureReceiverProperties properties)//{ // } // Uncomment the method below to handle the event raised before a feature is deactivated. //public override void FeatureDeactivating(SPFeatureReceiverProperties properties)// { // } // Uncomment the method below to handle the event raised after a feature has been installed. //public override void FeatureInstalled(SPFeatureReceiverProperties properties)// { // } // Uncomment the method below to handle the event raised before a feature is uninstalled. //public override void FeatureUninstalling(SPFeatureReceiverProperties properties)// { // } // Uncomment the method below to handle the event raised when a feature is upgrading. //public override void FeatureUpgrading(SPFeatureReceiverProperties properties, string upgradeActionName, System.Collections.Generic.IDictionary<string, string> parameters) // { // } } } You can see what we get is a class that inherits from SPFeatureReceiver. In SharePoint, there are different classes for different kinds of events you can handle. For example, events on lists, events on list items, events on sites. You can create a class that is derived from a specific event receiver and then you can override methods inside of that class to handle the events. The Events of a Feature are used when it is being − Activated Deactivated Installed Uninstalled Upgrading Next, you need to attach that class as the event handler for the specific item. For example, if there is an event handler that handles list events, you need to attach that class to the list. Therefore, we will handle two Features − When the feature is activated and When it is being deactivated. Step 2 − We will implement the FeatureActivated and FeatureDeactivated methods as shown below − using System; using System.Runtime.InteropServices; using System.Security.Permissions; using Microsoft.SharePoint; namespace FeaturesAndElements.Features.Sample { /// <summary> /// This class handles events raised during feature activation, deactivation, installation, uninstallation, and upgrade. /// </summary> /// <remarks> /// The GUID attached to this class may be used during packaging and should not be modified. /// </remarks> [Guid(“e873932c-d514-46f9-9d17-320bd3fbcb86”)] public class SampleEventReceiver : SPFeatureReceiver { private const string listName = “Announcements”; public override void FeatureActivated(SPFeatureReceiverProperties properties) { var web = properties.Feature.Parent as SPWeb; if (web == null) return; var list = web.Lists.TryGetList(listName); if (list != null) return; var listId = web.Lists.Add(listName, string.Empty, SPListTemplateType.Announcements); list = web.Lists[listId]; list.OnQuickLaunch = true; list.Update(); } public override void FeatureDeactivating(SPFeatureReceiverProperties properties) { var web = properties.Feature.Parent as SPWeb; if (web == null) return; var list = web.Lists.TryGetList(listName); if (list == null) return; if (list.ItemCount == 0) { list.Delete(); } } } } Note − When the feature is activated, we will create an Announcements list. When the feature is deactivated, we will check to see if the Announcements list is empty and if it is, we will delete it. Step 3 − Now right-click on the Project and choose deploy. You will see the following Deployment Conflict warning. Visual Studio is telling us that we are trying to create a list called contacts, but there is already a list in the site called Contacts. It is asking us if we want to overwrite the existing list, and in this case click Resolve. Step 4 − Go back to SharePoint and then refresh your site and go to Site Actions → Site settings → Manage site features → Sample feature. You can see that there are no announcements list in the left pane. Step 5 − Let us Activate Sample feature and you will see the Announcements list, but it is empty right now. Note − If you deactivate your Sample Feature then you will notice that the Announcements list goes away. Step 6 − Let us reactivate the feature. Go to Announcements and then Add a new announcement. We will call this Test and then click Save. You will see the Test file under Announcements. Now when you Deactivate Announcements, you will see that the Announcements list stays because it was not empty. Print Page Previous Next Advertisements ”;
SharePoint – List Functionality ”; Previous Next In this chapter, we will discuss from an end-user perspective mostly, covering Lists and some of the value-added features on top of lists like views, validation etc. When the end users create content within SharePoint, it is stored in the form of lists. Lists are really the data storage mechanism within SharePoint. It provides the user interface to be able to view the items in a list, add, edit, and delete items or view individual items. Let us have a look into a simple example in which we will add a contacts list. Step 1 − Open your SharePoint site and go to the Site Contents page. You can see the current contents, lists and libraries, and we have the ability to add new content by clicking add an app. Step 2 − So let us take a look at some of the things we can add to our site − We can create a new document library. We can create a custom list where we define the schema. There are also some lists with predefined schemas like the task list here. We can add pictures, some wiki pages, forms, a links list, announcements list, contacts list, and calendar etc. Step 3 − Let us select the contacts list. Step 4 − We will call this list- Contacts and then click the Create button. Step 5 − So now you can see here in your site contacts, you have the contacts list and you can click on that to work with the items in the list. Step 6 − One way to add a new item to this list is to click this New Item link and then add it in my content. Step 7 − Enter the Last Name and First name, and then come up to the tool bar or the Ribbon and click Save. Step 8 − We can also put the list into edit mode by clicking on the edit link. Step 9 − Next, we can add some other Contacts. Once editing is finished, click the Stop editing to get out of badge edit mode. The page will show all the contacts. A couple of other things when we are working with the list here. Step 10 − Click ITEMS to get access to the items on Ribbon. Step 11 − Click LIST here to get access to the Ribbon items related to the entire list. Print Page Previous Next Advertisements ”;
SharePoint – Setup Environment ”; Previous Next In this chapter, we will setup the development environment for SharePoint. As you already know that there are three different options of SharePoint. They are − SharePoint Foundation SharePoint Server Office 365 In this chapter, we will be using the Office 365, which is cloud-based version. Step 1 − You can easily create a free trial account here https://products.office.com/en/business/office-365-enterprise-e3-business-software. Step 2 − Click the Free trial option. A new page will open. Step 3 − Enter the required information and click Next and you will see the following page. Step 4 − Enter the username, company name and password and click Next. It will send you a verification code. Once the verification is completed then it will start creating the account. Step 5 − Once your account is created, you will see the following page. Step 6 − Click You’re ready to go and you will see the following page − Now your environment is ready and you can start share point development but you will also need to install visual studio. Microsoft provides a free version of visual studio, which also contains SQL Server and it can be downloaded from https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs.aspx. Installation Following steps will guide you to install SharePoint. Step 1 − Once downloading is complete, run the installer. The following dialog will be displayed. Step 2 − Click Install and it will start the installation process. Step 3 − Once the installation process is completed successfully, you will see the following message − Step 4 − Restart your computer if required. Now open Visual studio from the Start Menu. It will open the following dialog box and it will take some time for preparation. Step 5 − Once all is done, you will see the main window of Visual studio. You are now ready to start your application. Step 6 − Select File → New → Project menu option. Step 7 − Select Office/SharePoint in the left pane under Templates → Visual C#. Doubleclick Install Office Developer Tools. Step 8 − Click Install and close all Visual Studio instances. A new page will open. Click Next. Step 9 − A message box will appear. Click Update. Step 10 − Once it is updated, you will see the message as follows − Print Page Previous Next Advertisements ”;