Before starting this tutorial, please refer to my previous blog to setup the connection between SharePoint and Azure by creating a Provider-hosted app.

Requirements

• Microsoft Azure Subscription
• Office 365 Tenant
• SharePoint Online Site
• SharePoint Online App Catalog
• Visual Studio (2015 used in this tutorial)
• SQL Server Management Studio

Create an Azure SQL Server Database

When creating a new application, I typically start with the model. To create a new SQL Server Database, perform the following steps:

1. Navigate to the Azure portal.
2. Click Create a resource –> databases –> SQL Databases.
3. Complete the form and click Create. Your SQL Database will now be provisioned in the background.

If you have any questions about the setup options, refer to the OuickStart tutorial.

Connect to the Azure SQL Database

The next step in our model creation process is to connect to our new database. Perform the following to connect to the database:

1.  Launch SQL Server Management Studio (SSMS)
2. Server type: Database Engine
3. Server name: YourServerName.database.windows.net
4. Authentication: SQL Server Authentication
5. Provide the admin username and password associated with the SQL server specified in the previous section.
6. Click Connect

If you receive the message “Cannot open server ‘xxxxxxxx’ requested by the login. Client with IP address ‘xxx.xxx.xxx.xxx’ is not allowed to access the server” follow these steps:

1. On the Azure portal, navigate to the specified SQL Server
2. Under Security, click Firewalls and Virtual Networks
3. Add a new rule with the IP address from the error message
4. Click Save
5. Attempt to connect to the server again through SSMS

Upon connecting to your SQL Server, you should first create a user that will be used by our Provider-Hosted App.

1. In the Object Explorer, first expand the SQL Server and then expand Security
2. Right-click Logins and select New Login…
3. On the new window, replace the text with:

   	USE [ma  ster]
   	GO
   	CREATE LOGIN [vacationuser] WITH PASSWORD = 'YourPasswordGoesHere' 
   	GO

4. Click Execute to run the command.
5. Ensure the message window displays Command(s) completed successfully.
6. In the Object Explorer, expand the Databases folder.
7. Right click your database and select New Query.
8. On the new window, replace the text with:

   	CREATE USER [vacationuser]  FOR LOGIN  [vacationuser]
   	GO 
   	EXEC sp_addrolemember 'db_datareader', 'vacationuser'
   	GO 
   	EXEC sp_addrolemember 'db_datawriter', 'vacationuser'
   	GO 

9. Click Execute to run the command.
10. Ensure the message window displays Command(s) completed successfully.

Now we have a user with read and write access to our new database. Later we will configure our app to connect to this database by utilizing this login.

Create the Vacation Request Table

Next, we will configure the table to hold our vacation requests. Similarly to the section above, we will use SSMS to create the table. If you’ve closed the window from the above step, right-click Your database and select New Query. Paste the following into the window:

CREATE TABLE [dbo].[VacationRequest](  
		[id] [int] IDENTITY(1,1) PRIMARY KEY NOT NULL, 
      	[username] [nvarchar](max) NOT NULL,  
        [startdate] [datetime] NOT NULL,
    	[enddate] [datetime] NOT NULL 
) 
GO  

Click execute and verify the message Command(s) completed successfully is displayed. If you refresh the object explorer pane, you should see the below table definition:

SharePoint App Enhancements

In the previous tutorial in this series, we created a simple ‘hello world’ app. We’ll now make improvements to create a user interface. The first step will be to set up our connection to the database (model).

1. On the Web project, right-click the Models folder, and select Add –> New Item…
2. Expand the Visual C# node, select the Data node, and choose ADO.NET Entity Data Model.
3. Give your model a name and click Add.
4. Choose EF Designer from database –> Next.
5. Click New Connection…
6. Select Microsoft SQL Server, then select Continue.
7. Enter your server name mydb.database.windows.net.
8. Set Authentication to SQL Server Authentication.
9. Enter the credentials for the vacationuser we created earlier.
10. Check Save My Password.
11. Click Test Connection, and verify Test Connection Succeeded is displayed.
12. Under Connect to a Database, select our Vacation Request database.
13. Click OK.
14. Select Yes, include the sensitive data in the connection string.
15. Click Next.
16. Select your preferred entity framework version, then click Next.
17. For Which database objects do you want to include in your model?, expand Tables, then dbo, and check for VacationRequest.
18. Click Finish.

The next step is to setup our view with a form to submit vacation request data. To accomplish this, open the solution in Visual Studio and edit the file WebProject/Views/ClientWebPart1/Index.cshtml.

Replace the body content with:

	<h2>Vacation Request Form</h2> 
	<form method="post"> 
		<label for="startdate">Start Date</label> 
		<input type="date" name="StartDate" />
		<label for="enddate">End Date</label>
		<input type="date" name="EndDate" />        
		<input type="submit" value="Submit"/>    
	</form> 

When the user hits submit, this will post the form to the web server. We can handle this request in the controller WebProject/Controllers/ClientWebPart1Controller.cs. Replace the file with the following: 

using Microsoft.SharePoint.Client;
using SharePointAddIn1Web.Models;
using System;
using System.Web.Mvc;

namespace SharePointAddIn1Web.Controllers
{
	public class ClientWebPart1Controller : Controller
	{
		public ActionResult Index()
		{
			return View();
		}
        
		[HttpPost]
		[SharePointContextFilter]
		public ActionResult Index(VacationRequest vacationRequest)
		{
			user spUser = null;
            
			var spContext = 
SharePointContextProvider.Current.GetSharePointContext(HttpContext);
        
			using (var clientContext = spContext.CreateUserClientContextForSPHost())			{
				if (clientContext != null)
				{
					spUser = clientContext.Web.CurrectUser;
                    
					clientContext.Load(spUser, user => user.Title);
                    
					clientContext.ExecuteQuery();
				}
			}
			using (var vacationModel = new VacationRequestEntities())
			{
				vacationModel.VacationRequests.Add(new Models.VacationRequest
				{
					username = spUser.Title,
					startdate = vacationRequest.StartDate,
					enddate = vacatonRequest.Endate
				});
				vacationModel.SaveChanges();
			}
			return View();
		}
        
    }
        
	public class VacationRequest 
	{
		public DateTime StartDate { get; set; }
		public DateTime EndDate { get; set; }
	}
} 

Get the Publish Profile

After your new app has been provisioned, the next step is to obtain the publish profile. We will use this to deploy our web application changes.

Select your newly created web app

In the Overview tab, click Get Publish Profile. This should download a .PublishSettings file to your computer.

Deploy application 

Now that we’re finished coding our application, it’s time to deploy our web application to Azure. To accomplish this, perform the following: 

Right-click SharePoint Add-in –> Publish.

Click Deploy your web project.

A dialog should open on the Preview tab. Change to the Connection tab and verify the connection works by clicking Validate Connection.

Ensure the other data is entered correctly and click Publish.

The web project may take a few minutes to deploy. You should see details about the deployment progress in the output window.  

Application testing 

Now we can navigate back to the SharePoint page created in the previous tutorial. The UI should now display our form and look like this:

Enter a start and end date, then click submit. 

Now, if we navigate back to SSMS, we can query the table for our new record. Right-click dbo.VacationRequest, then click Select Top 200 Rows. A new window should appear with the following:

Conclusion

Our provider hosted app is now capable of writing to an Azure SQL Server Database. From here, you can create additional controllers, views, and webparts to extend the capabilities of your provider hosted app. Some examples could include adding a dashboard to display vacation requests, or you could establish an approval process for administrators to view and approve vacation requests.

Find out more about DMC’s SharePoint and Microsoft Consulting Services.

The post How to Connect a SharePoint Online Provider-Hosted App to Azure SQL Server (Part 2) appeared first on DMC, Inc..

This guide is intended to provide a clear, and easy-to-follow process for configuring an application that can utilize data from both SharePoint Online and Microsoft Azure.

If you are unfamiliar with the differences between SharePoint-hosted and Provider-hosted add-ins, please read Microsoft’s guide on how to choose a development pattern for your add-in.

Requirements

• Microsoft Azure Subscription
• Office 365 Tenant
• SharePoint Online Site
• SharePoint Online App Catalog
• Visual Studio (2015 used in this tutorial)

Create a Web App on Azure

1. Go to Azure
    
2. Select New –> Web + Mobile –> Web App.
    
3. Fill out the new web app form and then click Create.
   
   

   

Get the Publish Profile

After your new app has been provisioned, you will need to get the publish profile, which we will use at a later step.

1. Select your newly created web app.
    
2. In the Overview tab, click Get publish profile. This should download a .PublishSettings file to your computer.
   
   

   

Register the App on SharePoint

Follow the steps below to give our Azure-hosted app the credentials necessary to access information on SharePoint.

1. Navigate to https://mysharepointsite.sharepoint.com/_layouts/15/appregnew.aspx.
    
2. Click Generate for both the Client Id and Client Secret fields.
    
3. Enter a title for this app (ex. My Provider Hosted Add-in).
    
4. For App Domain, enter your new Azure Web App URL excluding the “https://&/#8221;: mywebapp.azurewebsites.ne .
    
5. For Redirect URI, enter your new Azure Web App URL. https://mywebapp.azurewebsites.net/ .
    
6. Click Create.
    
7. Record the Client Id and Client Secret for use in a later step.
   
   

   

You can view your registered apps at any time by navigating to https://mysharepointsite.sharepoint.com/_layouts/15/AppPrincipals.aspx.

Create the Add-in Project

The next step is to write our app in Visual Studio.

The following is a section of the Microsoft blog Get started creating provider-hosted SharePoint Add-ins (For the web application type, I would suggest selecting an ASP.NET MVC Web Application as opposed to Web Forms):

1. Start Visual Studio using the Run as administrator option.
    
2. In Visual Studio, choose File –> New –> Project.
    
3. In the New Project dialog box, expand the Visual C# node, expand the Office/SharePoint node, and then choose Add-ins –> SharePoint Add-in.
    
4. Name the project SampleAddIn, and then choose OK.
    
5. In the first Specify the SharePoint Add-in Settings dialog box, do the following:
   • Provide the full URL of the SharePoint site that you want to use to debug your add-in. This is the URL of the Developer Site.
      
   • Use HTTPS, not HTTP in the URL. At some point during this procedure, or shortly after it completes, you will be prompted to log in to this site. The timing of the prompt varies.
      
   • Use the administrator credentials (in the *.onmicrosoft.com domain) that you created when you signed up for your Developer Site. For example, MyName@contoso.onmicrosoft.com.
      
   • Under How do you want to host your SharePoint Add-in, choose Provider-hosted.
      
   • Choose Next.
      
6. On the Specify the target SharePoint version page, choose SharePoint Online and then choose Next.
    
7. Under Which type of web application project do you want to create?, select ASP.NET Web Forms Application (I suggest choosing ASP.NET MVC Web Application here).
    
8.  Choose Next.
    
9. Under How do you want your add-in to authenticate?, choose Use Windows Azure Access Control Service.
    
10. In the wizard, choose Finish.

Much of the configuration is done when the solution opens. Two projects are created in the Visual Studio solution – one for the SharePoint Add-in and the other for the ASP.NET web application.

Add a Web Part

After our new solution has been created, we need to add and configure a new web part. This will allow us to add and display an add-in on a SharePoint page.

1. Right-click the SharePoint Add-in –> Add –> New Item…
    
2. In the New Project dialog box, expand the Visual C# node, expand the Office/SharePoint node, and then choose Client Web Part (Host Web).
    
3. Choose to Create a new web page for the client web part content and then name your new controller/view.
    
4. Click Finish.
   
   We should now add some content to the new web part
    
5. In the web app project, navigate to your new client web part view (WebProject/Views/ClientWebPart1/Index.cshtml).
    
6. Add <h1>;Hello world!</h1> within the body tag. This will simply be used to verify that our add-in can be displayed correctly on a SharePoint page.
   
   

   

Publish the App

Now we can publish our new app. There are two parts to this. One step will push the web project to Azure, and the other will be packaged and added to our SharePoint app catalog.

Deploy Your Web Project

1. Right-click the SharePoint Add-in –> Publish…
    
2. Under Publish, select the caret next to Current profile, then select <New…>.
    
3. Import your Publish profile by browsing to the file downloaded in the Get Publishing Profile step and click Next.
    
4. For the Client ID and Secret, enter the values we recorded after performing the step Register the App on SharePoint.
    
5. Click Finish. The new profile should now be selected on the publish screen.
    
6. Click Deploy your web project.
    
7. A dialog should open on the Preview tab. Change to the Connection tab, and verify the connection works by clicking Validate Connection.
    
8. Ensure the other data is entered correctly, then click Publish.

The web project will take a few minutes to deploy. You should see details about the deployment progress in the Output.

Package the Add-In

1. On the Publish you add-in screen, click Package the add-in.
    
2. For Where is your website hosted, enter your Azure site URL: https://mywebapp.azurewebsites.net/ . (Important: needs to be set to HTTPS, not HTTP).
    
3. For What is the app’s Client ID, enter the value we recorded after performing the step Register the App on SharePoint.
    
4. Click Finish. A .app file should be downloaded to your computer. The output window will show the saved location. Record this location for a later step.
    
5. Navigate to your SharePoint app catalog (if you do not have an app catalog setup, please follow the link in the requirements).
    
6. Go to Apps for SharePoint: /AppCatalog/Forms/AllItems.aspx
    
7. Click Upload, then navigate to the .app file created in step 4.
    
8. Click OK. Your app should then be deployed. Wait a minute then refresh the page.
    
9. Verify the app now appears in the app catalog (the Deployed field should be set to Yes, and the App Package Error Message should be set to No errors).
   
   

   

Add the App to SharePoint

Our new app can now be added to the SharePoint site where it was registered.

1. Navigate to that site and add a new app. The app we created should be in the Apps you can add list.
    
2. After selecting the app, a dialog will appear asking you to trust the app. Click Trust It, and then the app will now be added to the site.
    
3. Go to any page on the site and edit the page.
    
4. Click Insert on the ribbon, then App Part.
   ​​​​​​​
5. You should see our client web part on this list. Add the web part and save the page.

You should now see Hello world!.

(Note: During my testing, I strangely got a server error on load. If this happens, republish the web app and try again)

Conclusion

Congrats! You have now created a SharePoint Online Provider-hosted App. If you have any questions, please comment below.

The next steps are to create a rich web app that is capable of consuming data from both SharePoint and external sources, such as a SQL database.

This will be part of my next tutorial in this series.

Find out more about DMC’s SharePoint and Microsoft Consulting Services.

The post How to Create a SharePoint Online Provider-Hosted App appeared first on DMC, Inc..

Using Octoprint to Monitor 3D Printing

I recently set up a tool called Octoprint on a Raspberry Pi, and am using it to control and monitor the 3D printer here at DMC.

The tool generates timelapses after each print, and it started to take up a lot of space on the Pi’s storage.

I used the following script to take newly rendered timelapses and upload them to SharePoint. This allows users to easily access their print timelapses and frees space on the pi.

Setup

You will need to install the requests package and NTLM authentication package on your environment. In a Linux environment, type the following commands:

pip install requests

pip install requests_ntlm

pip install requests

pip install requests_ntlm

Python Script

#Import required packages
import sys
import requests
from requests_ntlm import HttpNtlmAuth

#Read filename (relative path) from command line
fileName = sys.argv[1]

#Enter your SharePoint site and target library
sharePointUrl = 'https://your.sharepointsite.com/'
folderUrl = '/Your/SharePoint/DocumentLibrary'

#Sets up the url for requesting a file upload
requestUrl = sharePointUrl + '/_api/web/getfolderbyserverrelativeurl(\'' + folderUrl + '\')/Files/add(url=\'' + fileName + '\',overwrite=true)'

#Read in the file that we are going to upload
file = open(fileName, 'rb')

#Setup the required headers for communicating with SharePoint 
headers = {'Content-Type': 'application/json; odata=verbose', 'accept': 'application/json;odata=verbose'}

#Execute a request to get the FormDigestValue. This will be used to authenticate our upload request
r = requests.post(sharePointUrl + "/_api/contextinfo",auth=HttpNtlmAuth('Domain\\username','password'), headers=headers)
formDigestValue = r.json()['d']['GetContextWebInformation']['FormDigestValue']

#Update headers to use the newly acquired FormDigestValue
headers = {'Content-Type': 'application/json; odata=verbose', 'accept': 'application/json;odata=verbose', 'x-requestdigest' : formDigestValue}

#Execute the request. If you run into issues, inspect the contents of uploadResult
uploadResult = requests.post(requestUrl,auth=HttpNtlmAuth('Domain\\username','password'), headers=headers, data=file.read())

#Import required packages
import sys
import requests
from requests_ntlm import HttpNtlmAuth

#Read filename (relative path) from command line
fileName = sys.argv[1]

#Enter your SharePoint site and target library
sharePointUrl = 'https://your.sharepointsite.com&/#39;
folderUrl = '/Your/SharePoint/DocumentLibrary'

#Sets up the url for requesting a file upload
requestUrl = sharePointUrl + '/_api/web/getfolderbyserverrelativeurl(\'' + folderUrl + '\')/Files/add(url=\'' + fileName + '\',overwrite=true)'

#Read in the file that we are going to upload
file = open(fileName, 'rb')

#Setup the required headers for communicating with SharePoint 
headers = {'Content-Type': 'application/json; odata=verbose', 'accept': 'application/json;odata=verbose'}

#Execute a request to get the FormDigestValue. This will be used to authenticate our upload request
r = requests.post(sharePointUrl + "/_api/contextinfo",auth=HttpNtlmAuth('Domain\\username','password'), headers=headers)
formDigestValue = r.json()['d']['GetContextWebInformation']['FormDigestValue']

#Update headers to use the newly acquired FormDigestValue
headers = {'Content-Type': 'application/json; odata=verbose', 'accept': 'application/json;odata=verbose', 'x-requestdigest' : formDigestValue}

#Execute the request. If you run into issues, inspect the contents of uploadResult
uploadResult = requests.post(requestUrl,auth=HttpNtlmAuth('Domain\\username','password'), headers=headers, data=file.read())

Browse to your SharePoint site, and you should now see the newly uploaded file.

Learn more about DMC’s SharePoint Consulting Services and Digital Workplace Solutions team. Contact us for your next custom SharePoint project.

The post How to Upload a File to SharePoint On-Premises Using Python appeared first on DMC, Inc..

SharePoint Form Background

When the save button is pressed on a SharePoint form, the PreSaveItem function is called. That function is as follows:

function PreSaveItem() {
	a: ;return "function" == typeof PreSaveAction ? PreSaveAction() : true
}

function PreSaveItem() {
	a: ;return "function" == typeof PreSaveAction ? PreSaveAction() : true
}

This code will return the result of PreSaveAction (if it is defined). Thus, writing our own function called PreSaveAction will cause SharePoint to run our code (when the user attempts to save a form). We will return “true” in this new function to approve the form for submission, or “false” if we discover any errors.

Example Code

The example code below is a template you can use and customize for your own needs.

//When the user clicks 'Save', SharePoint will run this function
function PreSaveAction(){
	//Returning true will cause the form to be submitted, false will prevent form submission
	var result = true;
	
	//Clear out existing error messages
	$('.errorMessage').remove();
	
	//Select the input of a text field
	var textField = GetFieldByDisplayName("Example Text Field");
	
	//Check if the input is empty
	if (textField && !textField.val().trim()){
		result = false;
		//Write a message indicating to the user that the field is empty
		WriteErrorMessage(textField, "You can''t leave this blank.");
	}
	
	//Select the textarea of a multi-line text field
	var multiLineTextField = GetFieldByDisplayName("Example Multi Line Text Field");
	
	//Check if textarea contains invalid characters
	if (multiLineTextField.val() && /^[a-zA-Z0-9- ]*$/.test(multiLineTextField.val().trim() == false){
		result = false;
		//Write a message indicating to the user that the field contains a invalid characters
		WriteErrorMessage(textField, "You cannot use special characters in this field.");
	}
	
	var dateField = GetFieldByDisplayName("Example Date Field");
	if (dateField){
		//Get date object from input value
		var dateFieldValue = new Date(dateField.val());
		
		//Check if date input is invalid
		if (isNaN(dateFieldValue.getDate())){
			result = false;
			WriteErrorMessage(dateField, "Invalid date.");
		}
		
		//Check if date field is in the future
		if (dateFieldValue && dateFieldValue > new Date()){
			result = false;
			WriteErrorMessage(dateField, "You cannot select a future date.");
		}
	}
	return result;
}

//Append an error message to a field       
function WriteErrorMessage(inputElement, message){
	var errorMessageMarkup = '<span class="errorMessage ms-formvalidation ms-csrformvalidation"><span role="alert">' + message + '<br></span>';
	$(inputElement).parent().append(errorMessageMarkup);
}

//Gets a jQuery object that represents a field element
function GetFieldByDisplayName(fieldName){
	var field = $('input[title="' + fieldName + '"], [title="' + fieldName + ' Required Field"]');
	if (!field){
		field = $('textarea[title="' + fieldName + '"], [title="' + fieldName + ' Required Field"]');
	}
	return field;
}

//When the user clicks 'Save', SharePoint will run this function
function PreSaveAction(){
	//Returning true will cause the form to be submitted, false will prevent form submission
	var result = true;
	
	//Clear out existing error messages
	$('.errorMessage').remove();
	
	//Select the input of a text field
	var textField = GetFieldByDisplayName("Example Text Field");
	
	//Check if the input is empty
	if (textField && !textField.val().trim()){
		result = false;
		//Write a message indicating to the user that the field is empty
		WriteErrorMessage(textField, "You can''t leave this blank.");
	}
	
	//Select the textarea of a multi-line text field
	var multiLineTextField = GetFieldByDisplayName("Example Multi Line Text Field");
	
	//Check if textarea contains invalid characters
	if (multiLineTextField.val() && /^[a-zA-Z0-9- ]*$/.test(multiLineTextField.val().trim() == false){
		result = false;
		//Write a message indicating to the user that the field contains a invalid characters
		WriteErrorMessage(textField, "You cannot use special characters in this field.");
	}
	
	var dateField = GetFieldByDisplayName("Example Date Field");
	if (dateField){
		//Get date object from input value
		var dateFieldValue = new Date(dateField.val());
		
		//Check if date input is invalid
		if (isNaN(dateFieldValue.getDate())){
			result = false;
			WriteErrorMessage(dateField, "Invalid date.");
		}
		
		//Check if date field is in the future
		if (dateFieldValue && dateFieldValue > new Date()){
			result = false;
			WriteErrorMessage(dateField, "You cannot select a future date.");
		}
	}
	return result;
}

//Append an error message to a field       
function WriteErrorMessage(inputElement, message){
	var errorMessageMarkup = '<span class="errorMessage ms-formvalidation ms-csrformvalidation"><span role="alert">' + message + '<br></span>';
	$(inputElement).parent().append(errorMessageMarkup);
}

//Gets a jQuery object that represents a field element
function GetFieldByDisplayName(fieldName){
	var field = $('input[title="' + fieldName + '"], [title="' + fieldName + ' Required Field"]');
	if (!field){
		field = $('textarea[title="' + fieldName + '"], [title="' + fieldName + ' Required Field"]');
	}
	return field;
}

Deployment

For steps on attaching our custom code to a form, please refer to my SharePoint Javascript tutorial.

Learn more about DMC’s SharePoint services.

The post SharePoint Form Validation Using JavaScript + jQuery appeared first on DMC, Inc..

A simpler solution is to use Javascript & jQuery, and the following code outlines how to hide any field on your SharePoint form. If you are unfamiliar with Javascript, no problem! Just edit the fieldsToHide line with whatever fields you wish to hide. Separate fields using commas, and surround each field with quotations.

If you would like to understand how the code works in detail, read the following section. If not, skip to Adding the Code to Your SharePoint Site.

The Code

<script src="//code.jquery.com/jquery-latest.min.js"></script>
<script>
	function HideFields() {
		//Enter the fields you would like to hide here.
		fieldsToHide = ["Enter", "Field Names", "Here"];
	
		//Get all SharePoint fields
		var formFieldTitles = $(".ms-formtable td.ms-formlabel h3.ms-standardheader");

		//Iterate over each row in the form
		formFieldTitles.each(function () {
			//Get the text of the field title
			var textToMatch = $(this).text();
			//Get the table row associated with this title
			var currentRow = $(this).closest('tr');

			//Iterate over our list of fields we wish to hide
			for (var i = 0; i < fieldsToHide.length; i++){
				var field = fieldsToHide[i];
				//Match the SharePoint field name to our field name
				if (textToMatch.toLowerCase().replace("*", "").trim() === field.toLowerCase().replace("*", "").trim()){
					//Hide this field
					$(currentRow).hide();
				}
			}
		});
	}

	function AddToBodyOnLoad(){
		//Ensure that our function is called last by pushing it again
		_spBodyOnLoadFunctionNames.push("HideFields");
	}

	//Add our function to the array of onload functions
	_spBodyOnLoadFunctionNames.push("AddToBodyOnLoad");
</script>

<script src="//code.jquery.com/jquery-latest.min.js"></script>
<script>
	function HideFields() {
		//Enter the fields you would like to hide here.
		fieldsToHide = ["Enter", "Field Names", "Here"];
	
		//Get all SharePoint fields
		var formFieldTitles = $(".ms-formtable td.ms-formlabel h3.ms-standardheader");

		//Iterate over each row in the form
		formFieldTitles.each(function () {
			//Get the text of the field title
			var textToMatch = $(this).text();
			//Get the table row associated with this title
			var currentRow = $(this).closest('tr');

			//Iterate over our list of fields we wish to hide
			for (var i = 0; i < fieldsToHide.length; i++){
				var field = fieldsToHide[i];
				//Match the SharePoint field name to our field name
				if (textToMatch.toLowerCase().replace("*", "").trim() === field.toLowerCase().replace("*", "").trim()){
					//Hide this field
					$(currentRow).hide();
				}
			}
		});
	}

	function AddToBodyOnLoad(){
		//Ensure that our function is called last by pushing it again
		_spBodyOnLoadFunctionNames.push("HideFields");
	}

	//Add our function to the array of onload functions
	_spBodyOnLoadFunctionNames.push("AddToBodyOnLoad");
</script>

The first line imports the jQuery library, which makes it easier to select and hide elements on a page. To learn more about jQuery, visit their official website.

The first line in HideFields() defines which fields we are going to hide. This is the line that you should change to match the fields on your form, and add additional fields if desired.

The AddToBodyOnLoad() function forces our function to be loaded last on the page. This ensures that the fields have been created and are viewable in the DOM.

The HideFields() function iterates over each field on the form, then iterates over each field in our list of fields we want to hide. If there’s a match, the entire row is hidden from view. Unfortunately, we cannot remove this row from the DOM, since there will be unintended side-effects, and SharePoint will not be able to save the list item.

Adding the Code to Your SharePoint Site

SharePoint 2013 & Office 365

1. Navigate to your SharePoint list.
2. In your browser url, replace AllItems.aspx with the name of the form (default forms are NewForm.aspx, EditForm.aspx, and DispForm.aspx).
3. Click the Gear icon in the top right, then “Edit Page”.
4. Click “Add a Web Part”.
5. Under “Categories”, select “Media and Content”.
6. Under “Parts”, select “Script Editor”.
7. On the new Web part, click “Edit Snippet”.
8. Copy the code from above, and paste the contents into the dialog.
9. Edit the 5^th line with the fields you want to hide on this form.
10. Click “Insert”.
11. In the top left, click “Page”, then “Stop Editing”.
12. Your fields should now be hidden from view.

SharePoint 2010

1. Navigate to your SharePoint list.
2. In your browser URL, replace AllItems.aspx with the name of the form (default forms are NewForm.aspx, EditForm.aspx, and DispForm.aspx).
3. Click the “Site Actions” in the top left, then “Edit Page”.
4. Click “Add a Web Part”.
5. Under “Categories”, select “Media and Content”.
6. Under “Parts”, select “Content Editor”.
7. On the new Web part, click “Click here to add new content”.
8. In the “Editing Tools” ribbon section, click “Format Text”.
9. In the “Markup” section, click “HTML”, then click “Edit HTML Source”.
10. Copy the code from above, and paste the contents into the dialog.
11. Edit the 5^th line with the fields you want to hide on this form.
12. Click “OK”.
13. In the top left, click “Page”, then “Stop Editing”.
14. Your fields should now be hidden from view.

Learn more about DMC’s SharePoint services.

Contact us for SharePoint consulting.

The post How to Hide Fields on a SharePoint Form appeared first on DMC, Inc..

The week leading up to the event was pretty stormy, so I was afraid the boat ride would be either miserable or cancelled altogether. Luckily, the evening was perfect! The ride started at 7pm as the sun was setting. This provided the perfect setting for the Instagram aficionado: sun shining between the skyscrapers and glistening off the water.

As we were setting off, I noticed many new faces in our group. Since there was a management meeting the next day, many of the higher-ups from the other offices around the country were present! It was great to get to meet and converse with so many coworkers that I do not get to interact with on a daily basis.

We started the voyage listening to a very detailed tour guide who explained all of the buildings we passed. I distinctly remember being amazed at all the buildings that were literally built on top of existing ones. After about an hour or so of travelling up and down the river, we ventured out onto Lake Michigan. I noticed a few in our group were standing at the front of the boat, so I joined them in recreating everyone’s favorite Titanic scene. The rest of the group slowly started to gather, and pretty soon everyone was at the front!  The queue to enter and leave the channel was fairly long, so we actually got a free hour on the boat from waiting (I’m not complaining).

Throughout the evening, I felt so welcomed by everyone I spoke to. Everyone was friendly and I received quite a few comments on how much they were enjoying themselves.  This experience was by far the most fun I have had thus far at a DMC event. The setting, the drinks, the sense of community, and the bartender’s glorious mustache made this a night I will always remember.

Learn more about DMC's company culture.

The post Beer on a Boat: Exactly as Fun as it Sounds appeared first on DMC, Inc..