<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>dSHIFT</title>
	<atom:link href="http://www.dshift.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dshift.com</link>
	<description>Finely Crafted SharePoint Solutions</description>
	<lastBuildDate>Mon, 17 Jun 2013 07:23:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Copy and paste feature issues SharePoint Designer 2013 text-based workflow designer</title>
		<link>http://www.dshift.com/blog/copy-and-paste-feature-issues-sharepoint-designer-2013-text-based-workflow-designer/</link>
		<comments>http://www.dshift.com/blog/copy-and-paste-feature-issues-sharepoint-designer-2013-text-based-workflow-designer/#comments</comments>
		<pubDate>Fri, 14 Jun 2013 07:27:26 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[issues]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[workflow designer]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8737</guid>
		<description><![CDATA[Even though we tried to enable frequently used features found within most editing tools, the following are some limitations:<br />
<br />
Can’t use Undo (Ctrl+Z).<br />
Can’t select multiple objects by clicking and dragging.<br />
Can’t move selected items by clicking and dragging ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/copy-and-paste-feature-issues-sharepoint-designer-2013-text-based-workflow-designer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Workflow form changed from InfoPath form to ASPX form</title>
		<link>http://www.dshift.com/blog/workflow-form-changed-from-infopath-form-to-aspx-form-2/</link>
		<comments>http://www.dshift.com/blog/workflow-form-changed-from-infopath-form-to-aspx-form-2/#comments</comments>
		<pubDate>Fri, 14 Jun 2013 07:25:59 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[aspx form]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[InfoPath form]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[SharePoint 2010 workflows]]></category>
		<category><![CDATA[SharePoint Designer]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[Windows Azure Workflow]]></category>
		<category><![CDATA[Workflow form]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8735</guid>
		<description><![CDATA[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 ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/workflow-form-changed-from-infopath-form-to-aspx-form-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Task Process actions can’t be inserted when two instances of SharePoint Designer are running</title>
		<link>http://www.dshift.com/blog/task-process-actions-cant-be-inserted-when-two-instances-of-sharepoint-designer-are-running/</link>
		<comments>http://www.dshift.com/blog/task-process-actions-cant-be-inserted-when-two-instances-of-sharepoint-designer-are-running/#comments</comments>
		<pubDate>Fri, 14 Jun 2013 07:24:50 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[SharePoint Designer]]></category>
		<category><![CDATA[SharePoint Designer 2010 workflow]]></category>
		<category><![CDATA[Task Process actions]]></category>
		<category><![CDATA[workflow designer]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8733</guid>
		<description><![CDATA[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.<br />
Workaround    Work with one instance of SharePoint ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/task-process-actions-cant-be-inserted-when-two-instances-of-sharepoint-designer-are-running/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fields SharePoint Designer workflows don’t support for lookup</title>
		<link>http://www.dshift.com/blog/fields-sharepoint-designer-workflows-dont-support-for-lookup/</link>
		<comments>http://www.dshift.com/blog/fields-sharepoint-designer-workflows-dont-support-for-lookup/#comments</comments>
		<pubDate>Fri, 14 Jun 2013 07:24:06 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[HTTP Web Service action]]></category>
		<category><![CDATA[lookup fields]]></category>
		<category><![CDATA[SharePoint 2010 workflows]]></category>
		<category><![CDATA[SharePoint Designer]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[SharePoint lists and document libraries]]></category>
		<category><![CDATA[workflows]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8731</guid>
		<description><![CDATA[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 ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/fields-sharepoint-designer-workflows-dont-support-for-lookup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>“is empty” operation can’t be used with “If” condition when comparing person type fields</title>
		<link>http://www.dshift.com/blog/is-empty-operation-cant-be-used-with-if-condition-when-comparing-person-type-fields/</link>
		<comments>http://www.dshift.com/blog/is-empty-operation-cant-be-used-with-if-condition-when-comparing-person-type-fields/#comments</comments>
		<pubDate>Fri, 14 Jun 2013 07:22:17 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint Designer 2010]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8729</guid>
		<description><![CDATA[When you compare a person type field in an If conditional statement, we don&#8217;t provide an &#8220;is empty&#8221; operation that we supported in SharePoint Designer 2010.<br />
Workaround    Store person data to string type variable (using coercion) and compare it with ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/is-empty-operation-cant-be-used-with-if-condition-when-comparing-person-type-fields/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some of workflow actions/conditions aren’t available in SharePoint Designer 2013</title>
		<link>http://www.dshift.com/blog/some-of-workflow-actionsconditions-arent-available-in-sharepoint-designer-2013/</link>
		<comments>http://www.dshift.com/blog/some-of-workflow-actionsconditions-arent-available-in-sharepoint-designer-2013/#comments</comments>
		<pubDate>Fri, 14 Jun 2013 07:21:28 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[SharePoint Designer 2010 (WF3)]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[SharePoint Designer 2013 (WF4)]]></category>
		<category><![CDATA[workflow actions]]></category>
		<category><![CDATA[workflow platform]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8727</guid>
		<description><![CDATA[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).<br />
Here&#8217;s a detailed list of deprecated ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/some-of-workflow-actionsconditions-arent-available-in-sharepoint-designer-2013/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Workflow fails when ‘{‘ or ‘}’ is used with Lookup in Email editor and String Builder designer type</title>
		<link>http://www.dshift.com/blog/workflow-fails-when-or-is-used-with-lookup-in-email-editor-and-string-builder-designer-type/</link>
		<comments>http://www.dshift.com/blog/workflow-fails-when-or-is-used-with-lookup-in-email-editor-and-string-builder-designer-type/#comments</comments>
		<pubDate>Fri, 14 Jun 2013 07:18:28 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[workflow]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8724</guid>
		<description><![CDATA[SharePoint 2013 workflow fails when ‘{‘ or ‘}’ is used with Lookup in Email editor and String Builder designer type.<br />
Workaround    Store ‘{‘ or ‘}’ in a different string variable and use it with lookup.<br />
]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/workflow-fails-when-or-is-used-with-lookup-in-email-editor-and-string-builder-designer-type/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quick Step cant use SharePoint 2013 workflow</title>
		<link>http://www.dshift.com/blog/quick-step-cant-use-sharepoint-2013-workflow/</link>
		<comments>http://www.dshift.com/blog/quick-step-cant-use-sharepoint-2013-workflow/#comments</comments>
		<pubDate>Fri, 14 Jun 2013 07:17:47 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[Blogs]]></category>
		<category><![CDATA[Quick Step]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[SharePoint 2010 workflow]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[SharePoint Server 2013]]></category>
		<category><![CDATA[workflow]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8722</guid>
		<description><![CDATA[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.<br />
Workaround    Use SharePoint 2010 workflow for quick step.<br />
]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/quick-step-cant-use-sharepoint-2013-workflow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Visual Designer might not be available even if Visio Pro is installed</title>
		<link>http://www.dshift.com/blog/visual-designer-might-not-be-available-even-if-visio-pro-is-installed/</link>
		<comments>http://www.dshift.com/blog/visual-designer-might-not-be-available-even-if-visio-pro-is-installed/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:55:04 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint Designer]]></category>
		<category><![CDATA[Visio Pro]]></category>
		<category><![CDATA[Visual Designer]]></category>
		<category><![CDATA[workflow]]></category>
		<category><![CDATA[Workflow diagrams]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8683</guid>
		<description><![CDATA[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 ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/visual-designer-might-not-be-available-even-if-visio-pro-is-installed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lookup data sources shared</title>
		<link>http://www.dshift.com/blog/lookup-data-sources-shared/</link>
		<comments>http://www.dshift.com/blog/lookup-data-sources-shared/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:54:12 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[Lookup data sources shared]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint Designer]]></category>
		<category><![CDATA[SharePoint Designer 2010]]></category>
		<category><![CDATA[SharePoint Designer 2010 (WF3) workflow]]></category>
		<category><![CDATA[WF3 workflow]]></category>
		<category><![CDATA[workflow]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8680</guid>
		<description><![CDATA[Lookup data sources are shared if you call a SharePoint Designer 2010 (WF3) workflow/association multiple times albeit multiple data sources are shown.<br />
Workaround    Create another WF3 workflow with different name and call it.<br />
]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/lookup-data-sources-shared/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Can not use Assignments type field in WF3 workflow with Task Process</title>
		<link>http://www.dshift.com/blog/can-not-use-assignments-type-field-in-wf3-workflow-with-task-process/</link>
		<comments>http://www.dshift.com/blog/can-not-use-assignments-type-field-in-wf3-workflow-with-task-process/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:53:38 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint Designer]]></category>
		<category><![CDATA[SharePoint Designer 2010]]></category>
		<category><![CDATA[SharePoint Designer 2010 (WF3) workflow]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[SharePoint Designer 2013 (WF4)]]></category>
		<category><![CDATA[stand-alone]]></category>
		<category><![CDATA[WF3 workflow]]></category>
		<category><![CDATA[workflow]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8678</guid>
		<description><![CDATA[You can&#8217;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.<br />
Workaround    Use a SharePoint Designer 2013 (WF4) Task Actions or Start a Task ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/can-not-use-assignments-type-field-in-wf3-workflow-with-task-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Special characters shown as hexadecimal code</title>
		<link>http://www.dshift.com/blog/special-characters-shown-as-hexadecimal-code/</link>
		<comments>http://www.dshift.com/blog/special-characters-shown-as-hexadecimal-code/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:52:57 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[hexadecimal code]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint Designer]]></category>
		<category><![CDATA[SharePoint Designer 2010]]></category>
		<category><![CDATA[SharePoint Designer 2010 (WF3)]]></category>
		<category><![CDATA[SharePoint Designer 2010 (WF3) workflow]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[SharePoint Designer 2013 (WF4)]]></category>
		<category><![CDATA[WF3 workflow’s]]></category>
		<category><![CDATA[WF3 workflow’s variable]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8677</guid>
		<description><![CDATA[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 ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/special-characters-shown-as-hexadecimal-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No error message if project fields are missing in visual designer actions</title>
		<link>http://www.dshift.com/blog/no-error-message-if-project-fields-are-missing-in-visual-designer-actions/</link>
		<comments>http://www.dshift.com/blog/no-error-message-if-project-fields-are-missing-in-visual-designer-actions/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:52:13 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[Project Server workflows]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[Visual Designer]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8675</guid>
		<description><![CDATA[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.<br />
Workaround    Make sure all the fields are specified.<br ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/no-error-message-if-project-fields-are-missing-in-visual-designer-actions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unable to publish a project workflow when it includes a &#8220;If any value equals value&#8221; condition</title>
		<link>http://www.dshift.com/blog/unable-to-publish-a-project-workflow-when-it-includes-a-if-any-value-equals-value-condition/</link>
		<comments>http://www.dshift.com/blog/unable-to-publish-a-project-workflow-when-it-includes-a-if-any-value-equals-value-condition/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:51:30 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[Unable to publish a project workflow]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8670</guid>
		<description><![CDATA[If a project workflow contains the “If any value equals value&#8221; condition for a custom field, it can&#8217;t be published.<br />
Workaround    The custom field value needs to be mapped to another variable first, and then that variable can be used ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/unable-to-publish-a-project-workflow-when-it-includes-a-if-any-value-equals-value-condition/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Date type project custom fields can not be used in project workflows</title>
		<link>http://www.dshift.com/blog/date-type-project-custom-fields-can-not-be-used-in-project-workflows/</link>
		<comments>http://www.dshift.com/blog/date-type-project-custom-fields-can-not-be-used-in-project-workflows/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:49:04 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8669</guid>
		<description><![CDATA[Date type project custom fields can’t be used in a project workflow.<br />
Workaround    Use a different type of custom field, such as a number or text custom field.<br />
]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/date-type-project-custom-fields-can-not-be-used-in-project-workflows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Workflow form changed from InfoPath form to aspx form</title>
		<link>http://www.dshift.com/blog/workflow-form-changed-from-infopath-form-to-aspx-form/</link>
		<comments>http://www.dshift.com/blog/workflow-form-changed-from-infopath-form-to-aspx-form/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:47:48 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[aspx form]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[InfoPath form]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint Designer 2010]]></category>
		<category><![CDATA[SharePoint Designer 2010 (WF3.5)]]></category>
		<category><![CDATA[SharePoint Designer 2010 (WF3.5) workflows]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[SharePoint Designer 2013 (WF4)]]></category>
		<category><![CDATA[Windows Azure Workflow]]></category>
		<category><![CDATA[workflow]]></category>
		<category><![CDATA[Workflow form]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8667</guid>
		<description><![CDATA[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.<br />
Workaround    No workaround is available. If you want to customize ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/workflow-form-changed-from-infopath-form-to-aspx-form/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>List workflows do not update their status field on the list item</title>
		<link>http://www.dshift.com/blog/list-workflows-do-not-update-their-status-field-on-the-list-item/</link>
		<comments>http://www.dshift.com/blog/list-workflows-do-not-update-their-status-field-on-the-list-item/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:47:07 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[list item]]></category>
		<category><![CDATA[List workflows]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint PowerShell]]></category>
		<category><![CDATA[workflow]]></category>
		<category><![CDATA[workflow status field]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8664</guid>
		<description><![CDATA[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 ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/list-workflows-do-not-update-their-status-field-on-the-list-item/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design view and Split view are removed from SharePoint Designer 2013</title>
		<link>http://www.dshift.com/blog/design-view-and-split-view-are-removed-from-sharepoint-designer-2013/</link>
		<comments>http://www.dshift.com/blog/design-view-and-split-view-are-removed-from-sharepoint-designer-2013/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:46:21 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[Design view]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint Designer 2013]]></category>
		<category><![CDATA[web part zones]]></category>
		<category><![CDATA[web parts]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8662</guid>
		<description><![CDATA[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.<br />
Workaround    You can use the Parse HTML menu before taking actions on ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/design-view-and-split-view-are-removed-from-sharepoint-designer-2013/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fields not supported for lookup in SharePoint 2013</title>
		<link>http://www.dshift.com/blog/fields-not-supported-for-lookup-in-sharepoint-2013/</link>
		<comments>http://www.dshift.com/blog/fields-not-supported-for-lookup-in-sharepoint-2013/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:45:31 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[Fields not supported for lookup in SharePoint 2013]]></category>
		<category><![CDATA[lookup user interface]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8661</guid>
		<description><![CDATA[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.<br />
<br />
App Created By<br />
App Modified By<br />
Check In Comment<br />
Client Id<br />
Comment Type<br />
Document Concurrency ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/fields-not-supported-for-lookup-in-sharepoint-2013/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Error creating a workflow</title>
		<link>http://www.dshift.com/blog/error-creating-a-workflow/</link>
		<comments>http://www.dshift.com/blog/error-creating-a-workflow/#comments</comments>
		<pubDate>Mon, 27 May 2013 06:44:12 +0000</pubDate>
		<dc:creator>srehman</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[blog sharepoint]]></category>
		<category><![CDATA[Error creating a workflow]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[sharepoint]]></category>
		<category><![CDATA[sharepoint 2013]]></category>
		<category><![CDATA[sharepoint 2013 blog]]></category>
		<category><![CDATA[sharepoint blog]]></category>
		<category><![CDATA[SharePoint Designer]]></category>
		<category><![CDATA[workflow]]></category>
		<category><![CDATA[WorkflowActions]]></category>

		<guid isPermaLink="false">http://www.dshift.com/?p=8659</guid>
		<description><![CDATA[If you use a page editing related area before you create a workflow, you will get the following error message.<br />
The list of workflow actions on the server references an assembly that does not exist. Some actions will not be ...]]></description>
		<wfw:commentRss>http://www.dshift.com/blog/error-creating-a-workflow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  www.dshift.com/feed/ ) in 2.14416 seconds, on Jun 18th, 2013 at 8:55 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Jun 18th, 2013 at 9:55 pm UTC -->