Skip Ribbon Commands
Skip to main content

Quick Launch

Laura Rogers @WonderLaura > Posts > SharePoint 2013 SP1 Workflow Improvements
August 09
SharePoint 2013 SP1 Workflow Improvements

I installed SP1 on my virtual machine. Yay.  For the workflow stuff though, there's a bit more that you need to do.  Install KB2799752 (for Service Bus 1.0) and KB2799754 (for Workflow Manager 1.0). Andrew Connell talks all about these steps in his post here.  Also, don't forget to run the SharePoint PowerShell command register-spworkflowservice after all that is done.  My full command (in my test VM) that I ran was:

register-spworkflowservice -spsite -workflowhosturi -allowoauthhttp –force

When I was looking through SharePoint Designer for some of the supposed updates, some of them didn't show up until I had run that PowerShell command.  Here are the workflow improvements that were made that are visible in the UI, and I got them out of Microsoft's spreadsheet list.  I'm not highlighting bug fixes here, just changes you that visibly see.

2817429 SharePoint Workflows won't wait for changes to content approval status fields

When you used the "Wait for field change in current item" action, the "Approval Status" and some other system type fields weren't available (Approver Comments, Checked Out To, etc)

Now they are there…

2817429 E-mails generated by workflow cannot be disabled for approvals in SharePoint workflows

In the 2 different task actions, there was no interface to select whether or not you want an email to get sent at all when a task gets assigned to someone. Also, if you looked at the Properties of the task process action, this is what you saw:

Before updates:

Now, there are a few more options that you have:

This means that if you change WaiveAssignmentEmail to Yes, no one will receive an email when the task is assigned to them. You can also use WaiveCancelationEmail by changing it to Yes if you don't want an email to go out to the assignee when the task is canceled.


2817429 Incomplete tasks are deleted when workflow task activities complete

This means just what it says. When the workflow completes, by default any tasks that haven't been completed get automatically deleted.

Now, look at the screenshot above. There's a setting you can change. It will still have the same default behavior, but now you can change PreserveIncompleteTasks to Yes if you want to. This one only applies to the "Start a task process" action. (inherently, the Assign a task action only assigns a single task, so this problem would never happen)


Matthew Bramer

Why would you call this a hack?
You've been telling everyone to do it this way for years. I don't really understand. Can you shed some light on that?

 on 8/9/2012 5:03 PM


Hey Matthew,
Yeah, since there's no design view in SharePoint Designer 2013, it would appear as though you can't do data view web parts anymore.  So the trick here is that I'm opening a SharePoint 2013 site in SharePoint Designer 2010, so that's why it's a hack.
lauraNo presence information on 8/9/2012 6:02 PM

Tom Resing

Inserting a Data View Web Part on a new .aspx page in SharePoint Designer 2010 worked for me. I've also once inserted one on a regular page in SPD 2013. Setting the data source, however, only worked for me in SPD 2010 on the blank page. I wasn't able to set the data source for the web part I added in SPD 2013.
 on 8/10/2012 6:25 AM

Brian Bedard

I'm curious what urls you were using when you did this.  I'm still trying to understand the new App Models.  When you added the web part to your site, were you in the sharepoint server content database or the new App Web? If you were in sharepoint, it would be a simple URL.  If you were in the App Web it would be some wierd GUIDed URL.  Also what did you create your site collection as.  And the template.

If you were in the sharepoint server, this really defeats the purpose of what Microsoft was trying to do.  Limit exposure to sharepoint by custom anything.

Just curious.
 on 8/10/2012 6:51 AM


I wouldn't call this is a hack. At the end of the day the DVWP doesn't care where and how you configured it. You could use Notepad if you prefer, so using SPD 2010 is just a convenience.
Check out for the bare minimum you need to get the DVWP up and running. And yes this still works in SP2013.
 on 8/10/2012 2:51 PM


Thanks, huge time saver over using a Notepad or SPD2013. 

What does SPD 2013 do now?
 on 8/28/2012 2:16 AM


Yes, it works like it's always worked, but how are people going to know that it needs to be done in spd2010 with no master page? That's why I wrote this.

lauraNo presence information on 8/30/2012 12:03 PM


Thanks for giving me some hope for SPD2013 without design view. I'm really gonna miss it.
 on 11/1/2012 12:48 PM


I foresee a lot of webcasts and Sharepoint Saturday sessions on how to survive without design view in SPD.
 on 11/1/2012 12:50 PM


thanks so much. DVWP are my go-to feature - this at least gives me a life jacket.
 on 11/8/2012 8:02 AM


Come on ...Move out of Sharepoint Designer atleast after the release of Sharepoint 2013.Ther is definelty some reason why this was not supported ann better to noy use it
 on 11/17/2012 9:38 AM


I should have known you'd already figured this out!  Thanx Laura... You're the bomb as usual. 

Praveen - some of us don't want to live in Visual Studio so Laura's work is VERY helpful. 
 on 12/12/2012 11:23 PM


For me, the biggest loss from Design View is not having the conditional formatting support in SPD 2013. I create a lot of custom lists that help me track various aspects of projects. Having conditional formatting helped to relay information about the state of certain rows/columns/cells, which proved to be very useful.

So, I'd love for someone to explain how I can get conditional formatting working on my SharePoint 2013 sites. I'd prefer a solution that has visual interfaces like SPD 2010 did, but I don't mind getting my hands dirty.

 on 12/14/2012 4:18 PM


Well, you can either do it the way that I've outlined here in this blog post, or you can try this new software by Lightning Tools called the Data Viewer Web Part:
lauraNo presence information on 12/18/2012 8:39 PM

Gianni Zanetti

Hi Laura
thanks a lot, was running into this problem and cojuld solve it with this approach, magic work!
 on 1/1/2013 3:05 PM


Hi Laura,

I've been looking at that Lightnight tools Data viewer Web Part for 2013 too. That woud be very valuable. One thing that  concerns me with buying it is that those types of 3rd party apps are going to keep sites from moving to SharePoint Online.  Been playing with SPO and it's just brilliantly clean and responsvie, but the idea that we can't easily connect int on-Prem datasources nullifies anything worth having in the Cloud. MS introduces some black box on-Prem solution that lets us wireup SPO connections and secure stores to on-Prem Data Sources in a few configurable steps. What you have to do now is somewhat nuts.. develop a MCF Service layer with contracts for every operation and host it on your own outward facing Web servers? Or build Hybrid App Hosted solutions and maintain an on-prem and cloud instance?  I'm a .Net Developer and I can tell you I understand why SPD is still here.
 on 1/27/2013 5:45 PM


Laura - When I try this I get the following error on my test.aspx page:  Web Part Error: A Web Part or Web Form Control on this Page cannot be displayed or imported. The type Microsoft.SharePoint.WebPartPages.DataViewWebPart, Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c could not be found or it is not registered as safe.

How can I fix this?
 on 2/27/2013 9:58 AM

Doesn't work

Cannot open SP2013 Foundation site in SP Designer 2010. the SP 2013 full Server may still be working though.
 on 3/18/2013 9:39 PM

Thomas Bohn

Have the same problem now. Some weeks ago it had worked. Dammed, seems that MS has maked some changes in updates to prevent the access to SPF2013 server from SPD2010.
 on 3/28/2013 4:45 PM

Dave Kuehling

I too have been using this "hack" for some time and came back one day to find it not working.

There are two options based on my testing: uninstall SPD2010 and reinstall. This will fix it, but the next time updates are applied it will break again.

Option two, roll back or block KB2553382 from being applied. This is the update that effectively stops SPD2010 from connecting to a 2013 site.

I removed and reinstalled SPD2010 then applied each update one by one testing SPD to see which broke it. Once KB2553382 was applied I could no longer connect, once I rolled it back, I was able to connect again to 2013 from SPD2010. You can find this updated grouped under SharePoint Designer 2010 in Add Remove Programs/Updates.

I have hidden this update in Windows Update to prevent this from happening again.

**Disclaimer** Please check with your IT group before rolling back or blocking any updates. They may also need to block this at the server level if using WSUS to push updates.

Hope that helps!!

 on 4/3/2013 9:43 AM

Good Hack Laura, This was really surprise from Microsoft that there is no Design view in SharePoint Designer 2013. But you have cracked it with the help of SharePoint Designer 2010.
But this thing need extra efforts as we need to create a new ASPX page with no master page then do the things for design, save to file, upload and add to page. These are the extra efforts. Nevertheless, good work.
 on 4/24/2013 11:36 PM


Do you have any new workarounds for this since it has been locked down?
 on 5/6/2013 4:37 PM

Julian Knight

It WAS a good hack but now Microsoft have turned off the ability to use Designer 2010 with SharePoint Online.

If your on-premise site still works, great, but it is only a matter of time before it catches up with SP Online.

Extremely annoying and one that I've raised with our Microsoft technical and account reps.
 on 5/9/2013 1:00 AM


Well, even in SPD 2013, you can still go into code view and insert data view web parts and do a lot of the same functionality.  The trick is that you have to know where to put your cursor in the code in order to do that.
Laura RogersNo presence information on 5/30/2013 3:48 PM

Steve Of Pekin

I also attempted to try this and found out it was turned off.  Has anyone found a tool that will allow you to do this.  Does MS plan on putting this capability back into SPD 2013.  I really hope so. We may put the whole converision to 2013 off since we have found this issue. 
 on 6/18/2013 4:06 PM


I just want to thank DAVE KUEHLING  for the tip about uninstalling the SPD update. I asked several people at MSFT about this and they had no clue.  So nice of MSFT to pass this off as an "update" so no one would know about it. 
 on 6/26/2013 2:38 PM


No, Microsoft has stated that they are not planning on giving us back the design view.  :-(  You can install a product called the "Data Viewer Web Part" by Lightning Tools.  It's the only tool like that, that I know of.
Laura RogersNo presence information on 8/2/2013 12:49 PM

Sam Lau

Hi Laura,
Thanks for those useful information. However, when I followed the steps above and tried to import to my SharePoint 2013 portal. All the conditional formatting are lost and the + sign for "Group By" are not functioning... Did I miss something very important? Please help and advise.

Thank you very much.
 on 8/6/2013 8:40 PM


You are my hero!   This works, and it is just awesome.

Thanks also to Dave K. for discovering which "fix" causes the incompatibility.

[I am soooooo mad at Microsoft for removing Design View!]
 on 8/13/2013 1:46 PM

Sri Kalagarla

Laura, You hack still works if you uninstall SPD Update (KB2553382 ) or not install it...
 on 9/18/2013 9:40 AM


Thanks so much Laura for this workaround. Was glad that I could use SPD 2010 with SP 2013 but realized soon that web parts did not work very well. This will really help me.
 on 11/15/2013 1:40 AM


I call this a hack because the feature that we used to use, which was MUCH easier - doesn't work. So we have to 'hack' it to make it easier. If it was obvious how to replace the old feature - then that wouldn't need a hack.
 on 11/20/2013 1:58 PM


MSFT snuck the update that blocks access to SPD 2010 through again - this time disguised as an Office 2010 update. The KB is 2687455 so now you have to remove that too. 
They don't provide details on what else the update does so remove at your own risk. But Office worked okay before it got updated and it doesn't seem to affect anything so I suspect it just blocks access to SPD 2010.
 on 12/5/2013 6:12 PM


If designer is not available then how we can update the Parameter value through code.
What is the Tag Name.
 on 1/6/2014 5:23 AM


Great job!  Thanks a lot Laura. It would really help out many SharePoint 2013 developers.

Thanks a ton!
 on 1/6/2014 7:35 AM


Awesome hack, I wish that MS didn't block it though :( 
 on 1/20/2014 1:16 PM


I keep getting: "An error occurred while attempting to add the item to the page".
How can I fix that?
 on 2/25/2014 1:52 AM


i am creating linked data source of two list,but first list column data displaying and second list column data is blank(second list column are lookup column),how can i solve it.
Waiting for reply.
 on 3/25/2014 6:51 AM

 Contacting You Back

​When you ask a question here, and would like to know when I answer you, please provide your twitter handle, so I can ping you when I respond.  It takes me a few weeks sometimes.

Add Comment

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.

Your Name *

Body *


Today's Date *

Select a date from the calendar.


RSS FeedFacebookYouTube

 Our Books for End Users


 My Tweets