SharePoint Designer workflow restore previous version - Applies to SP versions - 2013,2010 and 2007


Today I got into a situation to restore the previous version of one of the SharePoint Designer 2010 workflows, created in SharePoint Designer 2013.
1.     In the left pane of SharePoint Designer, click the little pin icon next to All Files.



2.     Now look for the folder Workflows on the right pane and look for your workflow.




3.     My situation was to restore a previous version of the workflow “Reminder Test. Select and expand it. 



4.     Each of these files has a set of versions. Right click on the XOML file and choose Version History. Select the version you would like to restore. (For my there is some problem in loading version history and so couldn’t provide the screenshot)

5.     Click Restore.

6.     Right click on the next file, the XOML.rules. Go find that exact same date/time of the file as the one in the previous step and restore it. Note that the version number may NOT be the same.

7.     Right click the next file, which is xoml.wfconfig.xml. Do the same thing by finding that same date/time that matches the one you restored at step 4. Restore it.

8.     In this case, I don’t need to change anything about my InfoPath XSN file, which is the task form as part of tasks that are assigned in the workflow. I’m skipping that one.

9.     Once you have restored all above 3 files, make sure that you exit  SharePoint Designer. This is because of a cached version of your workflow needing to be refreshed.

10.  Re-open your site in SharePoint Designer. When you open your workflow in the normal way now (as opposed to the funky way we did in step 2), you will see that good old version that you just restored.

11.  Click Publish. Now your restored workflow is live and in use on the site.


Comments

Post a Comment

Popular posts from this blog

Power BI Refresh Issue: unable to convert the value '' from the source data type 'VT_BSTR' to the expected data type 'VT_I8.

Image
While scheduling refresh in Power BI, you might get below error . Issue: Unable to convert the value '<pii></pii>' from the source data type 'VT_BSTR' to the expected data type 'VT_I8 .     Cause/Reason Behind: Column datatype mismatch between power bi desktop and power bi cloud report. Solution: Edit query in power bi desktop and change the data type so it’s in sync with Power BI service/cloud. Example: In my case, I have modified a column’s datatype from decimal to whole number (to display no. of days). Now power bi desktop and power bi service synced up and I could perform automatic data refresh.
Read more

Run Powershell script on Remote Computer/Server

Image
PowerShell Remoting allows you to run individual PowerShell commands or access full PowerShell sessions on remote Windows systems.   PowerShell is locked-down by default, so you’ll have to enable PowerShell Remoting before using it. This setup process is a bit more complex if you’re using a workgroup – for example, on a home network — instead of a domain.   Enabling PowerShell Remoting On the computer you want to access remotely, open a PowerShell window as Administrator – right click the PowerShell shortcut and select Run as Administrator.   To enable PowerShell Remoting, run the following command (known as a cmdlet in PowerShell):  Enable-PSRemoting -Force This command starts the WinRM service, sets it to start automatically with your system, and creates a firewall rule that allows incoming connections. The -Force part of the command tells PowerShell to perform these actions without prompting you for each step     Workgroup Setup If your computers aren
Read more

wsp not getting deployed in all servers

Last week, got into an issue that wsp was not deployed in all servers and hang. Please find below more information on that: Issue: Unable to deploy wsp solution in SP2016 On-Premise server Resolution : C leared SharePoint config cache and rebooted all SharePoint servers and the SQL server, r an the command Add-SPSolution and  Install-SPSolution and the .wsp solution got deployed Troubleshooting Steps Followed: -     ​In Central Admin checked in Farm Solution Management the status was stuck on deploying​ -     Stopped the SharePoint Admin and SharePoint Timer services -     Checked and found multiple One-time jobs​, deleted those using the scripts below ​   -     Find onetimer running job from timer job definition and delete with below query Get-SPTimerJob | where{$_.schedule.description -eq "One-time"} | ForEach-Object{$_.Delete()}​ Get-SPTimerJob | where{$_.DisplayName -eq $null} | foreach-object {$_.Delete()}Get-SPTimerJob | where{$_.sc
Read more