Thursday, May 5, 2016

SharePoint Framework for developers

Let me start with simply stating this is the best news I heard about SharePoint as a developer. As it is announced at the Future of SharePoint, SharePoint Framework is a Page and Part model that enables fully supported client-side development. This means the client-side development models on SharePoint just got even better. 

Microsoft has been very busy providing new APIs frequently for supporting multiple technology stacks throughout the past few years and they kept trying making these APIs platform independent with the JavaScript and REST API support. This is made even simpler and understandable with the support of the Microsoft Graph API though it is still at a level of gaining the best maturity when accessing Office 365 components. 

Friday, April 29, 2016

Speaking at Collab365 Summit 2016

In case if you do not know yet, Collab365 is huge this time. Its going to be Online from 10th to 12th May 2016 live from Microsoft HQ. If you are not registered yet, go and Register through the following link.

http://collab365.events/collab365-summit-2016/

With 12 more days to go I thought of writing up something about the session I am yet do deliver. I will be speaking on "Workflow Manager Troubleshooting and Experience". This will include some of the experience we had by building a considerably large workflow management system and automating several business processes.

Friday, April 22, 2016

Getting over with the Lookup field unavailability issue

I have been facing this issue quite sometime when creating a lookup field of a SharePoint list. The main suspect was the title field. 

As we create a lookup to a list we tend to use the title field as the lookup field. Also we are tend to rename it in order to easily get the field with link and actions. 

For example, lets assume we rename the title field as "Name" with the "MasterList". Still its internal name will be Title.

Now in the child list, we need to lookup the "Master List". What we need to do is simply lookup that name field. We can simply do it through the C# code. But SharePoint creates this within the internal name. So it expects the Title field to be there. 

The best way to avoid is setting up internal name when creating the lookup. This prevents any issues with the lookup. 

If you are ever mistaken with that and have used the display name, you can simply go to the column settings and save it even without any changes. This is a tricky way to get over there.

Regardless of trick, its always good to use the internal name.

Monday, April 18, 2016

SharePoint CSOMs for Customizations

One of the biggest questions that you may encounter if you are using the Managed Client Side Object Model for SharePoint development these days is picking up the correct version of the dll. Here is one of the screenshots captured through my dev environment.


As you can see in the above image, there are two versions of dlls available for each dll under different version numbers. 

Monday, April 4, 2016

C# Associating a Workflow Manager Workflow to a SharePoint list

Workflow Manager workflows are different to the prior versions as it follows a subscription based model for creating associations for the Workflow Manager. In this article I am planning to showcase the code snippet which allows associating a workflow to a SharePoint list as it is not much famous and mentioned at many places.


Friday, March 25, 2016

SharePoint PowerShell CSOM send email

In my previous article I explained about reading a SharePoint list using SharePoint PowerShell CSOM. In this article I will simply explain how to send an email using SharePoint PowerShell CSOM. 

In order to do this, you need to have the PowerShell CSOM setup done as I have explained in my previous article

An email can be simply sent using the SendMail method of the Utility class through the following code.

$email = [String[]]($email_receiver)
$emailProperties = New-Object Microsoft.SharePoint.Client.Utilities.EmailProperties
$emailProperties.To = $email
$emailProperties.Subject = $email_subject
$emailProperties.Body = $Body
[Microsoft.SharePoint.Client.Utilities.Utility]::SendEmail($Context,$emailProperties)

Thursday, March 24, 2016

Client-side SharePoint PowerShell CSOM Read list

SharePoint PowerShell API provides the capability to connect to SharePoint 2010, 2013 and Online. The major advantage is that these can be run from a remote machine. The API is available in CodePlex.

I will focus on how to use the API and read a SharePoint list in this article.

First we need to download the source from CodePlex and extract it to a directory with necessary permissions. I am using 'C:\SPPS\Source' as the location for extraction.

Next we need to get a client context as in a normal CSOM.