Comments on: Workflow not starting (state field is empty) when Versions.AddVersion after Sitecore upgrade from 6.5 to 8.1 https://blog.peplau.com.br/workflow-not-starting-state-field-is-empty-when-versions-addversion-after-sitecore-upgrade-from-6-5-to-8-1/ The things I've seen as a Sitecore Professional Sun, 26 Nov 2023 01:01:24 +0000 hourly 1 https://wordpress.org/?v=4.1.41 By: Rodrigo Peplau https://blog.peplau.com.br/workflow-not-starting-state-field-is-empty-when-versions-addversion-after-sitecore-upgrade-from-6-5-to-8-1/#comment-33 Mon, 05 Dec 2016 00:55:01 +0000 http://blog.peplau.com.br/?p=492#comment-33 Yes we tried that, however the issue was something else. Believe it or not, during the upgrade, the site definition we were using at the project got the attribute “enableWorkflow” removed, which in turn made the default value “false” take over, and that was causing ALL WORKFLOWS to be simply ignored.

The most funny is the guys at Sitecore’s Helpdesk also struggled a bit till they found out the issue.

]]> By: James Coleman https://blog.peplau.com.br/workflow-not-starting-state-field-is-empty-when-versions-addversion-after-sitecore-upgrade-from-6-5-to-8-1/#comment-32 Tue, 29 Nov 2016 16:56:50 +0000 http://blog.peplau.com.br/?p=492#comment-32 Just curious did you try to wrap your .AddVersion() with try catch suggested in the link below – might work withouth having to do your workflow hack – haven’t tried it, just a thought:

http://blog.boro2g.co.uk/sitecore-addversion-returns-null/

]]>