SharePoint Workflow error

Tech Trek – 2017 February

PROBLEM:
Runtime error occurs when initiating workflows, i.e. user reports that nothing happens, or failure occurs when attempting to transfer files (via OfficialFile.asmx Web service). Re-executing the workflow would result into the expected behavior.

ROOT CAUSE:
This typically happens after a SharePoint upgrade or patch has been applied. As this affects only a certain component, this behavior may not be apparent after the update has been applied.

RESOLUTION:

  1. Open SharePoint LOGS folder and check the affected log file at the time the event occurred to see if the following Unexpected error is present:
    <Error>
    <CompilerError Line=”0″ Column=”0″
    Text=”Type Microsoft.SharePoint.Workflow.SPWorkflowTaskProperties,
    Microsoft.SharePoint,
    Version=15.0.0.0,
    Culture=neutral,
    PublicKeyToken=71e9bce111e9429c is not marked as authorized in the application configuration file.” />
    </Error>
  2. Compare entry differences of the most recent web_<date/time>.BAK using a text comparison tool like WinMerge or WinDiff.
  3. Open web.config in the Web Front-end server at the following location and add/correct the affected component.
    C:\inetpub\wwwroot\wss\VirtualDirectories\<port number><System.Workflow.ComponentModel.WorkflowCompiler>
    <authorizedTypes>
    <targetFx version=”v4.0″>

    <authorizedType Assembly=”Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.Workflow” TypeName=”SPWorkflowTaskProperties” Authorized=”True” />
    </targetFx>
    </authorizedTypes>
    </System.Workflow.ComponentModel.WorkflowCompiler>
  4. Perform an iisreset.

I’ve highlighted Version=15.0.0.0 since usually this entry reverts back to 14.0.0.0 in the SharePoint web.config file which causes the unauthorized issue.

SharePoint files moved into root folder

Tech Trek – 2016 January

PROBLEM –
Users reporting that files are missing in their respective child folders, and eventually being moved into the root folder of the document library.

TROUBLESHOOTING –

  1. Identify if the affected SP 2013 site/library is being accessed via SharePoint Workspace (formerly Groove) client and your content is not over these file restrictions.
  2. Make sure that the following patch is applied for Workspace 2010 client
    SharePoint Workspace 2010 hotfix – February, 2012
    https://support.microsoft.com/en-us/kb/2597939
  3. To temporarily address the automatic transfer into the root folder –
    Set Offline Client Availability to No under Advanced Settings for the affected Document Library.Missing-Files-Offline

RESOURCES –

Drag & Drop is not working for SP2013

Tech Trek – 2015.09.28

One of the nice features of SharePoint 2013 is the ability to perform drag & drop file uploads. This is a quicker option from Upload Multiple Documents (known as Upload files using Windows Explorer instead — now that’s a mouthful).

DragAndDropError

PROBLEM –
Drag & drop function is not working for certain users in any SharePoint 2013 site even though this operation works for others. Files will not being displayed, or uploaded after file drop operation was successfully completed.

RESOLUTION –
Here are the steps to perform to resolve this issue:

  1. Make sure prerequisites are installed in the affected PC – see list below.
  2. Check if SharePoint-related extensions are enabled under Manage add-ons in Internet Explorer.
    DragAndDropAddons.png
  3. Use an alternate web browser to check if file uploads can be successful.
  4. If everything else is fails, check if the machine was previously upgraded from Office 2010 under Programs and Features of Control Panel. Perform an MS Office Repair if multiple versions exist.

SOFTWARE PREREQUISITES –

  • Internet Explorer 10 or higher
  • Internet Explorer 8 or 9 with MS Office 2013 installed
  • Latest version of Firefox or Google Chrome web browser that supports HTML 5 standards

 

SharePoint Checkbox Yes and Empty (No) values

Tech Trek – 2014.07.02

PROBLEM —
SharePoint defaults into “No” (false) value when Checkbox column is not selected. A user requested that it will be easier to isolate “Yes” (true) value when having a Checkbox column. This got me into my thinking cap, so why not?

WORKAROUND —
You can create a Choice column instead with only one item e.g. Yes, in order, to display empty values when users doesn’t select a value. Make this an optional column and leave the default value as blank. You can choose whether to use a drop down style, or checkbox to display the control.

Nice and easy …

SharePoint Send an Email when Owner is Assigned

Tech Trek – 2014.06.28

One of the nice things about SharePoint Task list is the ability to send an email notification when an ownership is assigned. Check out Advanced Settings in List Settings page as shown in the following screenshot.

Task EMail

What if your SharePoint list doesn’t fit the Task template?

But WAIT (pun intended), don’t despair! Open up your friendly SharePoint Designer and let’s build a simple workflow to address this need.

There is a SharePoint Designer action called Wait for field change in current item that we can use for this scenario. Here’s a screenshot where I have a Person/Group column called Item Owner to collect the possible owner of a list item. You can use the Send Email action to notify the user after this event has been completed. Usually, it is best practice to create conditional checks and add a history log entry to denote workflow completion.

Wait for Event

Once your custom workflow is published, you can set the Start options when a new item is created and associate the list. Voila! New entries will wait for the field to change and send an email after the Owner column is updated.

Wait for Start Options

I’d recommend having a site owner that will manage the list and assign items immediately to their respective owner. You can provide site owner notification by using the built-in SharePoint alert when new entries are added. Mission Accomplished!