SFDX CLI does not deploy Standard SObject workflow elements -- Deployed Source No results found

[ImJohnMDaniel]

Summary

Salesforce CLI appears to be unable to deploy workflow elements for Standard objects when those workflow elements are specified in the package.xml as individual metadata elements (i.e. WorkflowRule, WorkflowAlert, WorkflowFieldUpdate, etc.) and not as a whole workflow metadata element (i.e. Workflow).

Steps To Reproduce:

1. Create a workflow rule with a workflow email alert and workflow field update on the Account object
2. Create a package.xml file listing each of the elements individually in WorkflowRule, WorkflowAlert, WorkflowFieldUpdate, metadata types.
3. Retrieve the metadata. (this works correctly)
4. Deploy the workflow to another org. (Failure point)

Expected result

The workflow elements should be deployed to the target org

Actual result

No deployment occurs. The error seen is:

=== Deployed Source
No results found

Additional information

SFDX CLI Version(to find the version of the CLI engine run sfdx --version):

sfdx-cli/7.77.0-112dd7d412 darwin-x64 node-v12.18.3

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)

@oclif/plugin-autocomplete 0.2.0
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.1 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.4.3 (core)
alias 1.1.2 (core)
analytics 1.12.1 (core)
auth 1.3.0 (core)
config 1.1.9 (core)
generator 1.1.3 (core)
salesforcedx 50.2.0 (core)
├─ templates 50.1.0 (core)
├─ custom-metadata 1.0.10 (core)
├─ salesforce-alm 50.2.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
└─ apex 0.1.1 (core)
sfdmu 3.7.17
sfdx-cli 7.77.0 (core)
shane-sfdx-plugins 4.41.2
├─ @mshanemc/sfdx-sosl 1.1.0
└─ @mshanemc/plugin-streaming 1.1.7
soqlx-opener 0.1.12

OS and version:
MacOS v10.15.7

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[dmgerow]

I can confirm that I am also seeing this issue

[geraemartinez]

this issue is still happening in Windows 10 as well, does anyone have an ETD?

[sayantadandapat]

Hi We are not able to deploy the WorkFlowAlert and Workflow Rule with sfdx-cli/7.81.0-7b953c80d1 win32-x64 node-v12.18.3 version.Whenever we try to deploy the WorkFlowAlert and Workflow Rule it is saying "No Result Found" and showing an success message that deployment is successfull.
But nothing is deployed into the target org.
This is becoming a critical issue for us.
Please address this with upcoming CLI and fix that for our smooth deployment.

[geraemartinez]

I fixed the issue by adding the Workflow types element to my package.xml along with my workflow items

    </types>
         <members>MY_SOBJECT.MY_FIELD_UPDATE_NAME</members>
        <name>WorkflowFieldUpdate</name>
    </types>
    <types>
        <members>MY_SOBJECT.MY_TASK_NAME</members>
        <name>WorkflowTask</name>
    </types>

    <!-- this one is the important -->
    <types>
        <members>MY_SOBJECT</members>
        <name>Workflow</name>
    </types>
    <!-- this one is the important -->

[ImJohnMDaniel]

@geraemartinez -- Thanks for the suggestion but that won't work in my case. If I specify the Workflow element for Account or Case, I end up with all workflow rules on the SObject found in the org and not just the select rules that pertain to my application alone. The Metadata API guide does say that this approach of specifying the individual rules is permissible and thus my only conclusion is that it is a bug with CLI.

[geraemartinez]

@ImJohnMDaniel I agree, this was not happening before, my approach is just a temporary workaround (I hope), anyway, just to explain more my solution, when I am packaging my solution I am only retrieving specific workflow rules of the Account and Lead objects, not all of them, just as we normally used to do, specifying WorkflowTask, WorkflowFieldUpdate, etc.

then when I finished, I go to the workflow rules to make sure that I only see the elements that I specified in my package.xml, if so I add the workflow type (<types> <members>MY_SOBJECT</members> <name>Workflow</name> </types>) to the package.xml, therefore I am adding that element only when I finished to package everything or just when I am about to deploy the packages, in that way the issue does not come up again and I am able to deploy just the metadata that I retrieved.

hope it helps.

[iandrosov]

Based on Metadata Tags separate deploy or even Item deploy should be possible. But in practice, it does not work with SFDX CLI. As I found only way CLIS pull say Workflow on COntact is by pulling in Contact.workflow file that has ALL WF rules and other components even Packaged one. BUt if I want only to manage my custom parts it seem to be broken

[qwikag]

This is still broken on 7.89.2

The workaround seems OK, but I would do it a little differently.

I would create a separate retrieve_workflow.xml and deploy_workflow.xml, and maybe package.xml would be my final.
As suggested above retrieve.xml contains the specifics and deploy.xml contains object (highlevel) workflow xml only, e.g....
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>Opportunity</members> <name>Workflow</name> </types> <version>50.0</version> </Package>

This works

But the normal way is definitely a bug!

[ar-srinivas]

I am still facing this issue even on 7.98.0 version as well.

[demodigit92]

I am still facing the issue even on sfdx-cli/7.99.0 darwin-x64 node-v12.18.3

A workaround is do deploy using MDAPI instead of source API, this way we don't need to include workflow metadata, only WorkflowAlert

[saakshi-gupta]

This issue still persists in version 7.102.0.

I changed the name of a workflow rule and it deleted the workflow rule with the old name but didn't create the one with the new name.

[shetzel]

@saakshig - have you tried this using the new source plugin beta? See the announcement here: #1057

[IVerkhosh]

The issue is still in the sfdx-cli/7.108.0 win32-x64 node-v14.17.1
We are not using mdapi format, just source and it is not working