Site Columns are corrupted by using SharePoint Designer 2013 to create 2010 Workflows

Hi,

I would like to know if SharePoint Designer 2013 users with SharePoint 2013 SP1 has had these issues:

Occasion 1: In a 2010 workflow (not connected to a content type when workflow was created) with associated (custom) content types, all the content types dissappeared from the site collection. All the custom site columns where gone even when inspecting the columns from Site Settings in SharePoint 2013. I had to recreate the SharePoint site. Luckily it was the test site not the production site.

Occasion 2: In a 2010 workflow connected to Document content type, to be able to use the document title in the email to the user, the date-time columns in a child Documnt content type Information Policy settings are screwed up. User account columns are listed as date-time columns when I try to set to start a workflow. Further the CurrntItem:Title column is now missing in SharePoint Designer 2013 and can't be set in the email.

My conclusion so far is that to create 2010 workflows in SharePoint Desgner 2013 is very risky!

Has other similar experience and is there any suggestions how to improve SharePoint Designer 2013 stability?

I'm a bit scared to destroy the production Sharepoint system - that would be unacceptable!. I don't dare to use SharePoint Designer 2013 in production enviroment except maybe to Publish/Publish Globally.

Hope for help and suggestions.

Csaba Urbaniczky

August 24th, 2015 9:29am

Hi, after some further search on Internet, I found a reference that SharePoint Designer 201 do destroy site columns. I have updated now to 15.0.4569.1506. Does this version solve this issue? When I started SharePoint Designer it did not solve any of the issues I now have. I propably have to reinstall the test installation again.
Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 7:07pm

Well, I succeded to corrupt a third site collection with SPD 15.0.4569.1506, so NO, it doesn't solve the issue.
August 27th, 2015 7:20pm

Well, I succeded to corrupt a third site collection with SPD 15.0.4569.1506, so NO, SPD 15.0.4569.1506 doesn't solve
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2015 7:20pm

Or is it due to taht I impprt a workflow created with VS2010 into SPD 2013 that corrupts the SharePoint system? No suggestions at all from the community? Or is SPD this bad and no-one cares?

August 28th, 2015 9:25am

Or is it due to that I imported a workflow created with VS2010 into SPD 2013 that corrupts the SharePoint 2013 system? No suggestions at all from the community? Or is SPD this bad and no-one

Free Windows Admin Tool Kit Click here and download it now
August 28th, 2015 1:25pm

Hi Csaba,

As I understand, the site columns are corrupted when creating 2010 workflows in SharePoint designer 2013.

You could check if there is relative information about the issue in the ULS log.

You could create a new list or library and create the 2010 workflow in SharePoint designer 2013 to check if the same issue will occur.

And you also could create a new content type and create the 2010 workflow associated with the content type in SharePoint designer 2013 to check if the same issue will occur.

Best regards,

Sara Fan

September 3rd, 2015 3:31am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics