dSHIFT Blog

HomeBlog

Page 1 of 8 12345...»

Copy and paste feature issues SharePoint Designer 2013 text-based workflow designer

Posted by:

Even though we tried to enable frequently used features found within most editing tools, the following are some limitations:

  • Can’t use Undo (Ctrl+Z).
  • Can’t select multiple objects by clicking and dragging.
  • Can’t move selected items by clicking and dragging objects.
  • Can’t use Shift+Left Mouse Click to select multiple constructs such as Stage, Step, or Parallel Block but can be used for multi-selection of actions.
  • Don’t support copy-and-paste across the different workflow platform types.
  • Clipboard isn’t fully integrated with copy and paste of workflow actions in the ...
Continue Reading →

Categories: Blog

Tags: , , , , ,

Workflow form changed from InfoPath form to ASPX form

Posted by:

For the workflow based on SharePoint Designer 2013 and Windows Azure Workflow, SharePoint Designer creates ASPX forms instead of InfoPath forms that were created by SharePoint 2010 workflows. If you want to customize the form, you can click it from the forms slab in workflow summary page to show a generic ASPX page editor.

Workaround    No workaround is currently available.

Continue Reading →

Categories: Blog

Tags: , , , , , , , ,

Task Process actions can’t be inserted when two instances of SharePoint Designer are running

Posted by:

SharePoint Designer 2010 workflow actions, such as Start Approval process and Start Feedback process, can’t be inserted into the workflow designer when two instances of SharePoint Designer are running at the same time.

Workaround    Work with one instance of SharePoint Designer when you work with SharePoint Designer 2010 workflow actions.

Continue Reading →

Categories: Blog

Tags: , , , , ,

Fields SharePoint Designer workflows don’t support for lookup

Posted by:

Some fields in SharePoint lists and document libraries aren’t supported for lookup in SharePoint Designer 2013 and when those lookup fields are read from the workflow, that workflow will be canceled. Those fields are all Lookup type fields and mainly references to the global (hidden) list, and some fields are Lookup type to the fields in the same list.

  • [Fields in List]
  • App Created By
  • App Modified By
  • Client Id
  • Discussion Title
  • Folder Child Count
  • Item Child Count
  • Item Type
  • Parent Item ID
  • Path
  • Replies
  • Shortest Thread-Index Id Lookup
  • Sort Type
  • URL Path
  • [Fields in ...
Continue Reading →

Categories: Blog

Tags: , , , , , ,

“is empty” operation can’t be used with “If” condition when comparing person type fields

Posted by:

When you compare a person type field in an If conditional statement, we don’t provide an “is empty” operation that we supported in SharePoint Designer 2010.

Workaround    Store person data to string type variable (using coercion) and compare it with other string that has ID or account name in it.

Storing person data to integer type variable also doesn’t work if this field is empty, so using string type is safest way.

Continue Reading →

Categories: Blog

Tags: , , ,

Some of workflow actions/conditions aren’t available in SharePoint Designer 2013

Posted by:

Some of workflow actions/conditions aren’t available. Major reason for this disparity is because of the change in the workflow platform, which are shifting to SharePoint Designer 2013 (WF4) based from SharePoint Designer 2010 (WF3).

Here’s a detailed list of deprecated actions/conditions and deprecated features.

Actions

  • Stop Workflow
  • Capture a version of the Document Set
  • Send Document Set to Repository
  • Set Content Approval Status for the Document Set
  • Start Document Set Approval Process
  • Declare Record
  • Set Content Approval Status
  • Undeclare Record
  • Add List Item Permissions
  • Inherit List Item Parent Permissions
  • Remove List Item Permissions
  • Replace ...
Continue Reading →

Categories: Blog

Tags: , , , ,

Workflow fails when ‘{‘ or ‘}’ is used with Lookup in Email editor and String Builder designer type

Posted by:

SharePoint 2013 workflow fails when ‘{‘ or ‘}’ is used with Lookup in Email editor and String Builder designer type.

Workaround    Store ‘{‘ or ‘}’ in a different string variable and use it with lookup.

Continue Reading →

Categories: Blog

Tags: , , ,

Quick Step cant use SharePoint 2013 workflow

Posted by:

When you click Quick Step on the ribbon menu of a list in SharePoint Server 2013, you are redirected to SharePoint Designer 2013 but you can’t use SharePoint 2013 workflow.

Workaround    Use SharePoint 2010 workflow for quick step.

Continue Reading →

Categories: Blog

Tags: , , , , , , , ,

Visual Designer might not be available even if Visio Pro is installed

Posted by:

Sometimes the Visio license registry key gets set to Standard (STD) instead of Professional (Pro) causing the Visual Designer not being available. In Visio, you see a blank canvas when creating Workflow diagrams (instead of a canvas with the default stage in it).

Workaround    Do the following:

  1. Open Registry Editor.
  2. Go to this key: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Visio\Application
  3. Look for the LicenseCache property and check to see if it’s set to Standard (STD).
  4. If yes, delete it from that one property.
  5. Close SharePoint Designer and Visio.
  6. Open Visio Pro.

After ...

Continue Reading →

Categories: Blog

Tags: , , , , , , , ,

Lookup data sources shared

Posted by:

Lookup data sources are shared if you call a SharePoint Designer 2010 (WF3) workflow/association multiple times albeit multiple data sources are shown.

Workaround    Create another WF3 workflow with different name and call it.

Continue Reading →

Categories: Blog

Tags: , , , , , , , , ,

Can not use Assignments type field in WF3 workflow with Task Process

Posted by:

You can’t use Assignments type field as a parameter when you invoke a SharePoint Designer 2010 (WF3) workflow that has a Task Process related action in it.

Workaround    Use a SharePoint Designer 2013 (WF4) Task Actions or Start a Task Process, or use WF3 workflow stand-alone.

Continue Reading →

Categories: Blog

Tags: , , , , , , , , , , ,

Special characters shown as hexadecimal code

Posted by:

If a local variable name contains a special character (such as ? or #) in a SharePoint Designer 2010 (WF3) workflow, those characters are shown as a hexadecimal code. Special character or reserved Visual Basic keywords can’t be used for local variable names for SharePoint Designer 2013 (WF4).

Workaround    Remove special characters from the WF3 workflow’s variable name.

Continue Reading →

Categories: Blog

Tags: , , , , , , , , , , , ,

No error message if project fields are missing in visual designer actions

Posted by:

When creating Project Server workflows using the Visual Designer, and if the fields are missing in the Set this field in the project to this value project action, you don’t get an error message.

Workaround    Make sure all the fields are specified.

Continue Reading →

Categories: Blog

Tags: , , , , ,

Unable to publish a project workflow when it includes a “If any value equals value” condition

Posted by:

If a project workflow contains the “If any value equals value” condition for a custom field, it can’t be published.

Workaround    The custom field value needs to be mapped to another variable first, and then that variable can be used for comparison.

Continue Reading →

Categories: Blog

Tags: , , , ,

Date type project custom fields can not be used in project workflows

Posted by:

Date type project custom fields can’t be used in a project workflow.

Workaround    Use a different type of custom field, such as a number or text custom field.

Continue Reading →

Categories: Blog

Tags: , , ,

Workflow form changed from InfoPath form to aspx form

Posted by:

For a workflow based on SharePoint Designer 2013 (WF4) and Windows Azure Workflow, SharePoint creates aspx forms instead of InfoPath forms that were created by SharePoint Designer 2010 (WF3.5) workflows.

Workaround    No workaround is available. If you want to customize the form, you can click it from Forms in workflow summary page and a generic aspx page editor appears.

Continue Reading →

Categories: Blog

Tags: , , , , , , , , , , , , , ,

List workflows do not update their status field on the list item

Posted by:

When a workflow is associated to a list, a workflow status column is automatically created for that workflow. The column has the same name as the workflow association. But when an instance of the workflow is actually run, the status field on the list item remains blank, and is never set to a value.

Workaround    The main cause of the issue is that the workflow status field is set to read-only. You can manually work around this by setting the read-only ...

Continue Reading →

Categories: Blog

Tags: , , , , , , , ,

Design view and Split view are removed from SharePoint Designer 2013

Posted by:

For editing HTML and ASPX pages, only Code view is available and the Design view/Split view aren’t supported. So some menu related web parts and web part zones won’t work.

Workaround    You can use the Parse HTML menu before taking actions on related web parts and web part zones.

Continue Reading →

Categories: Blog

Tags: , , , , , , ,

Fields not supported for lookup in SharePoint 2013

Posted by:

The following is a list of fields not supported for lookup. These fields aren’t visible in lookup user interface and don’t work at run-time.

  • App Created By
  • App Modified By
  • Check In Comment
  • Client Id
  • Comment Type
  • Document Concurrency Number
  • File Size
  • Folder Child Count
  • Item Child Count
  • Item Type
  • Name (for use in forms)
  • Sort Type
  • Source Name (Converted Document)
  • Source Version (Converted Document)
  • URL Path
  • Virus Status
Continue Reading →

Categories: Blog

Tags: , , , , ,

Error creating a workflow

Posted by:

If you use a page editing related area before you create a workflow, you will get the following error message.

The list of workflow actions on the server references an assembly that does not exist. Some actions will not be available. The assembly strong name is Microsoft.SharePoint.WorkflowActions, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Contact your server administrator for more informations.

Workaround    Do the following:

  1. Delete the cached folder: %appdata%\ roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache
  2. Open SharePoint Designer again. (But not from a browser link like Edit in SharePoint Designer.)
  3. Select the Workflow tab.
  4. Create ...
Continue Reading →

Categories: Blog

Tags: , , , , , , , , ,

Page 1 of 8 12345...»