0
There is an inconsitent behaviour when deploying solutions that include a workflow and a business rule, both with a look up field. Issue comes when the look up field guid is not the same in the source and destination environment.

Behaviour for Workflows: the solution with the workflow is deployed in the destination environment, when solution is published the workflow is NOT active and cannot be activated until you remove the old guid reference from the source environment and add the new guid reference from the destination environment.

Behaviour for Business rukes: the solution with the B.R. is deployed in the destination environment, when solution is published the B.R. is active and does not shows any error. This is misleading when doing the deployment because when the B.R. is triggered it does not work as expected. Solution is the same performed with the workflow (deactivate the B.R., remove the old reference record guid and add the correct destination source record guid)

Expected behaviour: Ideally both actions should have the same behaviour and we think the logical would be that B.R. should be published into the destination environment as Inactive so the deployer knows after a basic check that he needs to modify and correct it
Category: Workflow
STATUS DETAILS
Needs Votes