views:

797

answers:

3

MS CRM Dynamics 4.0 incorporates the MS WF engine. The built in designer allows the creation of sequential workflows whos activities have native access to CRM entities.

Is it possible to:

  • Create a state machine workflow outside of CRM (i.e. in visual studio) and import it into CRM?
  • Have this workflow access the CRM entities?
A: 

I don't know the answer to your specific question, but hopefully this information will point you in the right direction.

The "native" format for WF workflows is ".xoml" files. These are basically identical to XAML files, and both are nothing more than generic persistence formats for a .NET object tree. If you can access the saved data that is output by the Dynamics designer, it should be in the same format. If it is, you should be able to open it from the Visual Studio designer.

The key here is that CRM undoubtedly defines its own set of custom activities that you'll need to be able to reference from within the alternate designer. With any luck, these will be in assemblies with obvious names and/or in the GAC.

Curt Hagenlocher
-1: MSCRM uses WF, but provides zero access to the XOML it builds so although in theory you could do it, you actually can't. MSCRM custom activities are not in the GAC, and are "hidden" internally (old versions of the SDK had a way to find them, that has been removed to prevent exactly this.)
Robert MacLean
+2  A: 
  • It is NOT possible to create a state machine workflow for use in MSCRM.
  • It is also not supported to create any workflow outside of MSCRM and import it.
  • As a work around you could write either all the logic you need into a custom workflow activity and import that into MSCRM and have it called from a normal workflow.
  • The other option is build a seperate application which runs a state machine workflow and interacts with MSCRM via the web services. You could (would need to?) combine this with a custom workflow activity to kick off processes.
Robert MacLean
Even if it's not supported it is possible to create a Workflow and import it in CRM...
Mercure Integration
@Mercure Supported is important for two reasons. One if something goes wrong you know Microsoft will be able to help and two so that upgrades are smooth, and with CRM 5 on the doorstep it is very important now.
Robert MacLean
I agree. The only point that I wanted to highlight is that it's possible, even if it's not supported.
Mercure Integration