Read Custom User Property created in Central Admin using JavaScript

Hi All,

I have faced recently one problem. Created a custom user property in Central Admin and reading property using JSOM as below.
/**** Code Start****/
$(document).ready(function(){
SP.SOD.executeFunc('sp.js', 'SP.ClientContext', CallClientOM);
});
function CallClientOM()
{
var context = new SP.ClientContext.get_current();
this.website = context.get_web();
this.currentUser = website.get_currentUser();
context.load(currentUser);
context.executeQueryAsync(Function.createDelegate(this, this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed));
}
function onQuerySucceeded(sender, args)
{  
  get_user_profile_by_login(currentUser.get_loginName());
}

function get_user_profile_by_login(login) {
$().SPServices({
 operation: "GetUserProfileByName",
 async: false,
 AccountName: login,
 completefunc: function (xData, Status) {
Supervisor = getUPValue(xData.responseXML, "Supervisor");
$("input[title='Supervisor']").val(Supervisor);
  }
});
}
function getUPValue(x, p) {
  var thisValue = $(x).SPFilterNode("PropertyData").filter(function() {
    return $(this).find("Name").text() == p;
  }).find("Values").text();
  return thisValue;
}
/**** Code End****/

Problem: Here I have created Supervisor field as custom user property, but I am not able to read
from the code(as a non admin). I was set as, Policy Settings -> Default Privacy Setting -> Only Me.
Solution: While creating the property set as below:
Policy Settings -> Default Privacy Setting -> Everyone.
Then it worked!!!

SharePoint Timer Job Run Mechanisms

If you want to run it every TEN MINUTES,use SPMinuteSchedule class to configure:
SPMinuteSchedule minSchedule = new SPMinuteSchedule();
minSchedule.BeginSecond = 0;
minSchedule.EndSecond = 5;
minSchedule.Interval = 10;
tempJob.Schedule = minSchedule;
tempJob.Update();


If you want to run it at 11:05 PM every day, use SPDailySchedule class to configure:
SPDailySchedule tempSchedule = new SPDailySchedule();
tempSchedule.BeginHour = 23;
tempSchedule.BeginMinute=5;
tempSchedule.BeginSecond = 0;
tempSchedule.EndSecond = 15;
tempSchedule.EndMinute = 5;
tempSchedule.EndHour = 23;
tempJob.Schedule = schedule;
tempJob.Update();


If you want to run it on the 1st of every month between 1:15am to 1:30am, use SPMonthlySchedule
SPMonthlySchedule schedule = new SPMonthlySchedule();
schedule.BeginDay = 1;
schedule.EndDay = 1;
schedule.BeginHour = 1;
schedule.EndHour = 1;
schedule.BeginMinute = 15;
schedule.EndMinute = 30;
tempJob.Schedule = schedule;
tempJob.Update();

If you want to run on Monday every week between 2:01:00 am to 2:01:05 am, use SPWeeklySchedule
SPWeeklySchedule schedule = new SPWeeklySchedule();
schedule.BeginDayOfWeek = DayOfWeek.Monday;
schedule.BeginHour = 2;
schedule.BeginMinute = 1;
schedule.BeginSecond = 0;
schedule.EndSecond = 5;
schedule.EndMinute = 1;
schedule.EndHour = 2;
schedule.EndDayOfWeek = DayOfWeek.Monday;
tempJob.Schedule = schedule;
tempJob.Update();


If you want to run it every year on Jan 23 at 9:05AM, use SPYearlySchedule
SPYearlySchedule JobSchedule = new SPYearlySchedule();
JobSchedule.BeginMonth = 1;
JobSchedule.EndMonth = 1;
JobSchedule.BeginDay = 23;
JobSchedule.EndDay = 23;
JobSchedule.BeginHour = 9;
JobSchedule.EndHour = 9;
JobSchedule.BeginMinute = 5;
JobSchedule.EndMinute = 5;
JobSchedule.BeginSecond = 0;
JobSchedule.EndSecond = 5;
tempJob.Schedule = schedule;
tempJob.Update();

Owstimer.exe is the worker process to debug the code.

Error occurred in deployment step ‘Activate Features’: Attempted to perform an unauthorized operation

I have created a SharePoint empty project and added visual webpart into it.

When I try to deploy the solution, ended up with below error.

"Error occurred in deployment step "Activate Features" attempted to perform an unauthorized operation"

Reason:

The account which you are trying to deploy the solution may not have permission to specific webapplication/SiteCollection.

Solution:

• Open SharePoint 2013 Central Administration.
• Navigate to Application Management and choose Change site collection administrations
• Select the site collection where deployment should happen
• Add you windows account[Account which you are trying to deploy] as the primary (or) secondary site collection administrator.

Also check account has permission to access database, if not please add into Security section of SQL Server.

Hope this helps!!!

How to update URL field in SharePoint List using JSOM

 Here is the code to update URL field.
URL will have two properties. One is url and other is description.
Code below is using JSOM.
======================================================
var itemCreateInfo = new SP.ListItemCreationInformation();
var rootUrl = window.location.protocol + "//" + window.location.host + _spPageContextInfo.siteServerRelativeUrl;
itemCreateInfo.set_folderUrl(rootUrl + "/Lists/PROJECTS/Folder");//Create item folder inside list
this.oListItem = oList.addItem(itemCreateInfo);
oListItem.set_item('NUMBER', "23");
     var fvalue = new SP.FieldUrlValue();                  
    fvalue.set_url("http://google.com");
    fvalue.set_description("GoogleLink");
oListItem.set_item('URL', fvalue);

oListItem.update();
======================================================

Hope this helps!!!

Change the URL of the SharePoint List - Create 2010 Tasks list

Problem:
Sometimes when we create the sharepoint task list with 2013 Tasks template(171). We may not open that task and it results to error to open webparts maintenence page.

Resolution:
To resolve this, create Task list with 107 template id which is available with sharepoint 2010.
To do that, Open designer and create 2010 workflow and create task list with that workflow. It will create 107 template id task list.
But name of the task list will be created with the name Tasks and prefixed with workflow name.
ex: WorkflowNameTasks
To rename, we can open the list in sharepoint and edit the name. But it will not change the url. Url still refers old name, only display name changed now.
To change URL also, open the sharepoint site in explorer view and choose the list and rename. This completes URL change also.
Change the list internal name with the url in sharepoint by opening the site in explorer view and rename the list.

Hope it helps!!!

The workflow contains errors, but they are not visible in the current view

Hi,

Sometimes when you work on workflows in SharePoint Designer you can not publish it, because the Check for Errors fails with the following message: “The workflow contains errors, but they are not visible in the current view”

Usually in this case you really can’t see the place where the error is and it seems like everything is OK.

I spent some time to understand where the error is when I saw this error for the first time. Most likely it is an issue in SPD. However, it is rather simple to overcome it and force SPD to show the place the error is.

The solution: you just have to save your workflow (by pressing Save button in the ribbon), close it and open it again (by selecting it in the Navigation\Workflows and pressing the “Edit workflow” link).

After that you should be able to see what fields are set incorrectly:

You can press Check for Errors button to highlight all the errors with the red color:

I stumbled into this moment several times after copying-pasting my workflow. It seems like this new feature works well in the most parts of the workflow, except the Transition to stage part. At least, in my cases after pasting I had to repair fields in the Transition to stage part only.

Reference Url:

http://sp2013.pro/2013/04/solution-the-workflow-contains-errors-but-they-are-not-visible-in-the-current-view/

Manage Site Content and Structure in SharePoint 2013 Missing?

Recently, when I am searching for Manage Content and Structure, I couldn't find in Sharepoint 2013 env, where as it was available in Sharepoint 2010.

But It's not removed - just moved to Site Settings > Site Administration

Hope this helps!!!

SharePoint 2013: Start Workflow with JavaScript Client Object Model

//dialog element to show during processing
var dlg = null;      

//Subscription id - Workflow subscription id
//list item id for which to start workflow. If site workflow, then send null for itemId
function StartWorkflow(subscriptionId, itemId) {
   showInProgressDialog();
   var ctx = SP.ClientContext.get_current();
   var wfManager = SP.WorkflowServices.WorkflowServicesManager.newObject(ctx, ctx.get_web());
   var subscription = wfManager.getWorkflowSubscriptionService().getSubscription(subscriptionId);
   ctx.load(subscription, 'PropertyDefinitions');
   ctx.executeQueryAsync(
       function (sender, args) {
           var params= new Object();
           //Find initiation data to be passed to workflow.
           var formData = subscription.get_propertyDefinitions()["FormData"];
           if (formData != null && formData != 'undefined' && formData != "") {
               var assocParams = formData.split(";#");
               for (var i = 0; i < assocParams.length; i++) {
                   params[assocParams[i]] = subscription.get_propertyDefinitions()[assocParams[i]];
               }
           }
           if (itemId) {
               wfManager.getWorkflowInstanceService().startWorkflowOnListItem(subscription, itemId, params);
           }
           else {
               wfManager.getWorkflowInstanceService().startWorkflow(subscription, params);
           }
           ctx.executeQueryAsync(
               function (sender, args) {
                   closeInProgressDialog();
               },
               function (sender, args) {
                   closeInProgressDialog();
                   alert('Failed to run workflow');
               }
           );
       },
       function (sender, args) {
           closeInProgressDialog();
           alert('Failed to run workflow');
       }
   );
 }

function closeInProgressDialog() {
   if (dlg != null) {
       dlg.close();
   }
}
 

function showInProgressDialog() {
   if (dlg == null) {
       dlg = SP.UI.ModalDialog.showWaitScreenWithNoClose("Please wait...", "Waiting for workflow...", null, null);
   }
}

Code Snippet 1: Start workflow

As shown in the above code example, you need to pass subscription id and item id. Everytime you associate workflow with list or site, you will get an association id for this association.To get an association id, go to the workflow settings page and then right click on workflow name and from the URL, you can find the subscription id as shown below:

Figure 1: Get the Workflow Association Id from Workflow Settings Page

If your workflow is Site Workflow (for your information, SharePoint 2013 workflow can run on a list item or for site), then pass null value for itemId. ‘FormData’ retrieved from workflow Subscription, will be passed to workflow initiation. But if you would like to pass your own additional parameters, you can do so as shown below:

var params= new Object();
//Find initiation data to be passed to workflow.
var formData = subscription.get_propertyDefinitions()["FormData"];
if (formData != null && formData != 'undefined' && formData != "") {
    var assocParams = formData.split(";#");
    for (var i = 0; i < assocParams.length; i++) {
        params[assocParams[i]] = subscription.get_propertyDefinitions()[assocParams[i]];
    }
}

//your custom parameters
params['mykey']='this is custom value';

Code Snippet 2: Passing workflow initiation parameters

Reference URL: http://ranaictiu-technicalblog.blogspot.ae/2013/06/sharepoint-2013-start-workflow-with.html

SharePoint 2013 Workflows Deployment Steps

Understanding how to package and deploy workflow in SharePoint 2013

In this article Overview of the workflow packaging capabilities of SharePoint Designer 2013 Packaging a workflow by using SharePoint Designer 2013 Deploying a workflow package to SharePoint 2013

Overview of the workflow packaging capabilities of SharePoint Designer 2013

SharePoint Designer 2013 provides the capability to save a workflow as a template. Saving a workflow as a template is also known as packaging the workflow. After the workflow is saved as a template, it can then be imported into other SharePoint Server 2013 environments and used without the need to redevelop the workflow. Not all workflow types can be saved as a template. The following matrix shows the workflow types that can be saved as a template.

Support, by platform, for saving a workflow as a template

Workflow type	SharePoint 2010 Workflow platform	SharePoint 2013 Workflow platform
List Workflow	No	Yes
Site Workflow	No	Yes
Reusable Workflow	Yes	Yes

Note
SharePoint Server 2013 contains two different workflow platforms: the SharePoint 2010 Workflow platform and the SharePoint 2013 Workflow platform. Both platforms are available in SharePoint Server 2013. For more information about the two workflow, see Getting started with SharePoint Server 2013 workflow.

Packaging a workflow by using SharePoint Designer 2013

The process for packaging a workflow involves saving the workflow to a template file by using SharePoint Designer 2013. A workflow package is in the form of a Web Solution Package (WSP) file and has a .wsp extension. To package a workflow follow these steps.

Package a workflow

1. Open an existing workflow, or develop a new workflow, in SharePoint Designer 2013.
2. On the Workflow Settings tab in the ribbon, click the Save as Template button in the Manage section as shown in the figure.
   Figure: Save workflow as template
   
   
3. An informational dialog box appears to let you know the template has been saved to the Site Assets library.
4. Click the Site Assets library to view the workflow template as shown in the figure.
   Figure: A workflow template in Site Assets
   
   

Tip
A workflow template automatically saves to the Site Assets library of the site collection in which the workflow resides.

Deploying a workflow package to SharePoint 2013

You can deploy a workflow package to a SharePoint farm or site that is different from the farm or site in which it was developed. In order for a workflow deployment to be successful two items must be fulfilled:

• All workflow dependencies such as lists, libraries, columns, and content types must already exist on the new site.
• Each dependency must have the exact name of the source dependency.

If a workflow is deployed and the exact dependencies do not exist then the result will be an error.

Before you can deploy a workflow you must first export the workflow template from the source SharePoint Server 2013 farm. To export a workflow template, follow this procedure.

Export a workflow template

1. Open SharePoint Designer 2013 and navigate to the Site Assets library where the template is located.
2. Select the workflow template you want to export by clicking it.
3. Click the Export File button to save the template file to your local computer or a network drive, as shown in the figure.
   Figure: Export workflow template from SharePoint Designer 2013
   
   

To deploy a workflow package follow this procedure.

Deploy a workflow solution

1. Open Internet Explorer and navigate to the SharePoint Server 2013 site collection where you want to deploy the workflow.
2. Click Site Actions and select Site Settings.
3. In the Web Design Galleries section click Solutions.

   Note
   You must be on the Site Settings page for the site collection in order to see the Solutions gallery. If you are on the Site Settings page for a sub-site then the Solutions gallery is not visible.

4. Click the Upload Solution button to upload the solution as shown in the figure.
   Figure: Upload Solution button
   
   
5. Activate the solution by clicking the Activate button as shown in the figure.
   Figure: Activate Solution dialog and button
   
   

After a workflow solution has been activated for a site collection, it is available as a feature for all sub-sites. To activate the workflow feature for a sub-site, follow this procedure.

Activate the workflow feature

1. Open Site Settings on the site where you wish to activate the workflow feature.
2. In the Site Actions group, click Manage site features.
3. Click Activate next to the workflow feature as shown in the figure.

Figure: Activate workflow feature for site

Reference Url:

https://msdn.microsoft.com/en-us/library/office/jj819316.aspx

Create a workflow with elevated permissions by using the SharePoint 2013 Workflow platform

To allow workflow to use app permissions

1. Click the Settings icon as shown in the figure.
   
   Figure: Opening the Site Settings page
   
   
2. Go to Site Settings.
3. In the Site Actions section, select Manage site features.
4. Locate the feature called Workflows can use app permissions, as shown in the figure, and then click Activate.
   

   Caution
   This feature will not activate unless you have properly configured the SharePoint 2013 Workflow platform and also apps for SharePoint.

   Figure: The site feature, 'Workflows can use app permissions'
   
   

Granting full control permission to a workflow

In order for the workflow to function properly it must be granted full control in the site. The following procedure grants the full control permission to the workflow.

Important
The procedure assumes the following: The procedure must be completed by a user that has Site Owner permissions. The workflow must already be published to the SharePoint Server 2013 site.

To grant full control permission to a workflow

1. Click the Settings icon as shown in the figure.
   
   Figure: Opening the Site Settings page
   
   
2. Go to Site Settings.
3. In the Users and Permissions section, select Site app permissions.
4. Copy the client section of the App Identifier. This is the identifier between the last "|" and the "@" sign, as shown in the figure.
   
   Figure: Selecting the App Identifier
   
   
5. Navigate to the Grant permission to an app page. This must be done by browsing to the appinv.aspx page of the site.
   Example: http://{hostname}/{catalog site}/_layouts/15/appinv.aspx.
   The following figure shows an example.
   
   Figure: The appinv.aspx page and URL example
   
   
6. Paste the client id in the App Id field and then click Lookup, as shown in the figure.
7. Paste the following Permissions Request XML to grant full control permission.
   
   Copy

   <AppPermissionRequests>
       <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="FullControl" />
   </AppPermissionRequests>
   
   

   Caution
   There are no placeholders in the Scope value above. It is a literal value. Enter it exactly as it appears here.

   The following figure shows an example of the completed page.
   
   Figure: Looking up an App Id
   
   
8. Click Create.
9. You will then be asked to trust the Workflow app, as shown in the figure. Click Trust It.
   
   Figure: Trust the Workflow app
   
   

Reference link:
https://msdn.microsoft.com/en-us/library/office/jj822159.aspx

Error : Sideloading of apps is not enabled on this site

Hi All,

I have started working on sharepoint app development recently. When I started developing app in visual studio and deployed, got the following errror:
"Sideloading of apps is not enabled on this site".

Reason: I am not using Developer Site Collection

Solution: Two ways we can fix this issue.
1. Create Developer Site Collection and deploy apps.
2. If you are using different site collection other than "Developer Site Template", active the feature as below:

Enable-SPFeature e374875e-06b6-11e0-b0fa-57f5dfd72085 –url "Site Collection URL"

Here we have to activate "Side Loading feature" for non-developer site collections.

What is "App Side Loading"?

App sideloading is the ability to install a SharePoint 2013 App directly into a site to explicitly bypass the regular governance controls of SharePoint. It is a developer/test feature not intended for production use. It is not recommended to sideload apps regularly, or keep app sideloading enabled for longer than you are actively using the feature!

The developer site is designed for app developers to install and test apps before they are ready to release/publish on store.

Hope this helps!!!

Microsoft SharePoint is not supported in 32-bit process. Please verify that you are running in a 64-bit executable.

Error: Platform not supported exception

Description:

I was writing a console application using Visual Studio 2012 to use SPSite object of SharePoint 2013.When I ran the application I was getting the following error.

Microsoft SharePoint is not supported in 32-bit process. Please verify that you are running in a 64-bit executable.

Solution:

In the solution explorer right click on the project and then click on Properties. Click on Build tab. Check whether Platform Target is selected as Any CPU. Make sure Prefer-32 bit is not selected.

How to login as different user in SharePoint 2013?

Hi All,

You might face an issue while trying to do sign in as different user in SharePoint 2013.

Here is the url to do :

http//<sharepoint site_url>/_layouts/closeConnection.aspx?loginasanotheruser=true

Hope this helps!!!

Creating an list Item inside the folder using JSOM

Hello All,

Below code will help you to create an item inside the Folder.

Here is the code:

var clientContext = SP.ClientContext.get_current();
var list = clientContext.get_web().get_lists().getByTitle('Master');

var itemCreateInfo = new SP.ListItemCreationInformation();
itemCreateInfo.set_folderUrl('/Lists/Master/FolderName');

var listItem = list.addItem(itemCreateInfo);
listItem.set_item('Title', 'Hello!');
listItem.update();

clientContext.load(listItem);
clientContext.executeQueryAsync(function (sender, arges) {
    alert('Added');
}, function (sender, arges) {
    alert(arges.get_message());
});

Hope this helps!!!

SharePoint 2013 List Templates

New list template type that are exposed in SharePoint 2013 using Object Model with respect to SharePoint 2010 List Templates. Here is the quick comparison chart.

SP List Template Type	Description	SP 2013	SP 2010
AccessRequest	Access Request List. Value = 160.	Yes	No
AdminTasks	Administrator Tasks. Value = 1200.	Yes	Yes
Agenda	Agenda (Meeting). Value = 201.	Yes	Yes
Announcements	Announcements. Value = 104.	Yes	Yes
AppDataCatalog		Yes	No
CallTrack	Call Track. Value = 404	Yes	Yes
Categories	Categories (Blog). Value = 303.	Yes	Yes
Circulation	Circulation. Value = 405	Yes	Yes
Comments	Comments (Blog). Value = 302.	Yes	Yes
Contacts	Contacts. Value = 105.	Yes	Yes
CustomGrid	Custom grid for a list. Value = 120.	Yes	Yes
DataConnectionLibrary	Data connection library for sharing information about external data connections. Value = 130.	Yes	Yes
DataSources	Data sources for a site. Value = 110.	Yes	Yes
Decision	Decisions (Meeting). Value = 204.	Yes	Yes
DesignCatalog		Yes	No
DeveloperSiteDraftApps	Draft Apps library in Developer Site. Value = 1230	Yes	No
DiscussionBoard	Discussion board. Value = 108.	Yes	Yes
DocumentLibrary	Document library. Value = 101.	Yes	Yes
Events	Calendar. Value = 106.	Yes	Yes
ExternalList	External. Value = 600	Yes	Yes
Facility	Facility. Value = 402	Yes	Yes
GanttTasks	Project Tasks. Value = 150.	Yes	Yes
GenericList	Custom list. Value = 100.	Yes	Yes
HealthReports	Health Reports. Value = 1221	Yes	Yes
HealthRules	Health Rules. Value = 1220	Yes	Yes
HelpLibrary	Help Library. Value = 151.	Yes	No
Holidays	Holidays. Value = 421	Yes	Yes
HomePageLibrary	Workspace Pages (Meeting). Value = 212.	Yes	Yes
IMEDic	IME (Input Method Editor) Dictionary. Value = 499	Yes	Yes
InvalidType	Not used. Value = -1.	Yes	Yes
IssueTracking	Issue tracking. Value = 1100.	Yes	Yes
Links	Links. Value = 103.	Yes	Yes
ListTemplateCatalog	List Template gallery. Value = 114.	Yes	Yes
MaintenanceLogs	Maintenance Logs Library. Value = 175.	Yes	No
MasterPageCatalog	Master Page gallery. Value = 116.	Yes	Yes
MeetingObjective	Objectives (Meeting). Value = 207.	Yes	Yes
Meetings	Meeting Series (Meeting). Value = 200.	Yes	Yes
MeetingUser	Attendees (Meeting). Value = 202.	Yes	Yes
MySiteDocumentLibrary		Yes	No
NoCodePublic	No Code Public Workflow. Value = 122	Yes	Yes
NoCodeWorkflows	No Code Workflows. Value = 117.	Yes	Yes
NoListTemplate	unspecified list type. Value = 0	Yes	Yes
PictureLibrary	Picture library. Value = 109.	Yes	Yes
Posts	Posts (Blog). Value = 301.	Yes	Yes
SolutionCatalog	Solutions. Value = 121	Yes	Yes
Survey	Survey. Value = 102.	Yes	Yes
Tasks	Tasks. Value = 107.	Yes	Yes
TasksWithTimelineAndHierarchy	Tasks with Timeline and Hierarchy. Value = 171.	Yes	No
TextBox	Text Box (Meeting). Value = 210.	Yes	Yes
ThemeCatalog	Themes. Value = 123	Yes	Yes
ThingsToBring	Things To Bring (Meeting). Value = 211.	Yes	Yes
Timecard	Timecard. Value = 420	Yes	Yes
UserInformation	User Information. Value = 112.	Yes	Yes
WebPageLibrary	Wiki Page Library. Value = 119.	Yes	Yes
WebPartCatalog	Web Part gallery. Value = 113.	Yes	Yes
WebTemplateCatalog	Site template gallery. Value = 111.	Yes	Yes
Whereabouts	Whereabouts. Value = 403	Yes	Yes
WorkflowHistory	Workflow History. Value = 140.	Yes	Yes
WorkflowProcess	Custom Workflow Process. Value = 118.	Yes	Yes
XMLForm	XML Form library. Value = 115.	Yes	Yes

Get If-Else Condition in SharePoint Designer 2013 Workflow

Here is simple requirement in Sharepoint designer, we may need if else condition while developing 

workflows. Auto-population will work with the If condition, but Else wont work. We may see below error. 

The "Else" branch is not available from the auto complete.

To Overcome this issue we need to follow below steps.

1. It is available by the menu bar at the top.
2. If you are inside the if block, use keyboard shortcut (Alt + W + B)

Hope this helps!!!

How to get rid of default emails from task list

Hello All,

I have a requirement while creating the custom workflow. Here I am sending custom emails by configuring email settings in the task process. However, I am getting two emails one is custom and other is default.

To overcome this situation. I followed below steps.

1. Go to List Settings(Task List)
2. Go to Advanced settings
3. Modify Email settings to "No"

4. Click "OK" to Save Settings.
It solved my problem.

Thanks!!!