Error message when you publish an imported workflow in Microsoft Dynamics CRM 4.0: "Automatic workflow cannot be published if no activation parameters have been specified"

Applies to: Dynamics CRM 4.0

Symptoms


Consider the following scenario in Microsoft Dynamics CRM 4.0. You import a workflow that is set to "On demand." Then, you publish the workflow. In this scenario, you receive the following error message:
Automatic workflow cannot be published if no activation parameters have been specified.

Cause


This problem occurs because the import process does not examine the "ondemand" element of the ImportExportXml file of the exported workflow when the workflow is imported. By default, the value of the "ondemand" element is false when the workflow is saved to the Microsoft Dynamics CRM database. Therefore, the workflow is missing a key dependency that is needed to successfully publish the workflow.

Workaround


To work around this problem, open the workflow form, and then save the workflow. When this action occurs, the dependency to the Microsoft Dynamics CRM database persists. Then, the workflow can be published.

Resolution


This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
949256 Microsoft Dynamics CRM 4.0 updates and hotfixes

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates


For more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:

887283 Microsoft Business Solutions CRM software hotfix and update package naming standards