Thursday, January 28, 2016

SharePoint DateTime field REST API Time Zone Issue

We all think this is an issue, but it is not. REST API for SharePoint has its own way of handling things compared to the other APIs. There are a few things we need make note.

1. SharePoint stores date in 0000 UTC timezone. 
2. We have a different regional setting (timezone) for the SharePoint site.

Friday, January 15, 2016

WFInstanceManagementDB in Workflow Manager

WFInstanceManagementDB database plays a vital role in the SharePoint Workflow Manager workflows. This will maintain the list of instances that are being used by the Workflow Manager and associated related data. 

I could not find any recommended guidance for browsing and modifying these data in these workflows. So it is better do any operations associated with these databases with a possible risk in mind. I would not go and modify any of these databases.

But it will give an idea on how it is handled. Also it is not too complex.

Sunday, January 10, 2016

Setup SharePoint Environments on Azure for Development - Part 1

There are lot of developer platforms being moved to the Azure and other cloud platforms considering the many capabilities and benefits it has. In this article, I will be writing about how to setup a SharePoint development environment to a whole development team. This is with experience and I will be focusing considering a combination of following SharePoint Server roles as a developer environment. 

  1. A shared domain controller
  2. A shared database server
  3. A shared workflow manager farm
  4. Non-Shared SharePoint Application Server

Tuesday, January 5, 2016

Starting SharePoint Workflows with PowerShell

PowerShell is often used for many activities related to SharePoint. For any quick fixes around can be handled easily with PowerShell. Its no doubt Workflows are a vital part of SharePoint and with SharePoint 2013, they are not anymore in the SharePoint. 

Another important thing is that we often run SharePoint 2013 Management Shell as the administrator. But it is recommended not to use a SharePoint service account for running workflows. Well, it does not work. 

This makes starting a workflow tricky. We can get over with this through two tricky ways. One is granting another user with a Shell Admin permissions. But I would not recommend that. So the answer is simply impersonating a user.