Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Converting/deploying/retrieving Workflows and its children is broken #1591

Closed
amtrack opened this issue Jun 25, 2022 · 3 comments
Closed

Converting/deploying/retrieving Workflows and its children is broken #1591

amtrack opened this issue Jun 25, 2022 · 3 comments
Labels
custom-registry feature Issue or pull request for a new feature

Comments

@amtrack
Copy link

amtrack commented Jun 25, 2022

Summary

Converting and deploying and retrieving Workflows and child types like WorkflowFieldUpdate is broken.

I'm aware that Workflow is currently not decomposed but I think it could be easily decomposed because it contains only fully addressable child components.
The described behavior further shows that in non-decomposed form, Workflow cannot be placed in multiple package directories.

Steps To Reproduce:

The following repo contains 3 WorkflowFieldUpdate components split over multiple package directories:

  • force-app: Case.ChangePriorityToHigh, Case.ChangePriorityToMedium
  • another-package: Case.ChangePriorityToLow

Repository to reproduce: mdapi-issues/sfdx-workflow-handling

  1. sfdx force:source:convert -m Workflow:Case -d mdapi
  2. sfdx force:source:convert -m WorkflowFieldUpdate:Case.ChangePriorityToHigh -d mdapi
  3. sfdx force:source:retrieve -m WorkflowFieldUpdate:Case.ChangePriorityToHigh

Expected result

  1. Converts all 3 components into a single mdapi/workflows/Case.workflow metadata file
  2. Converts only the given WorkflowFieldUpdate to mdapi/workflows/Case.workflow metadata file
  3. Retrieves the given WorkflowFieldUpdate and appends it to force-app/main/default/workflows/Case.workflow-meta.xml or updates another-package/workflows/Case.workflow-meta.xml

Actual result

  1. Only the workflow components of the last package directory (here: Case.ChangePriorityToLow) are converted to mdapi/workflows/Case.workflow
  2. All children of the first packaging directory are converted and the folder name is invalid (workflowFieldUpdates instead of workflows): mdapi/workflowFieldUpdates/Case.workflow
  3. force-app/main/default/workflows/Case.workflow-meta.xml is overwritten

System Information

  • Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)
  • --> zsh
$ sfdx version --verbose --json
{
        "cliVersion": "sfdx-cli/7.156.1",
        "architecture": "darwin-arm64",
        "nodeVersion": "node-v16.13.1",
        "pluginVersions": [
                "@oclif/plugin-autocomplete 0.3.0 (core)",
                "@oclif/plugin-commands 1.3.0 (core)",
                "@oclif/plugin-help 3.3.1 (core)",
                "@oclif/plugin-not-found 1.2.6 (core)",
                "@oclif/plugin-plugins 1.10.11 (core)",
                "@oclif/plugin-update 1.5.0 (core)",
                "@oclif/plugin-warn-if-update-available 1.7.3 (core)",
                "@oclif/plugin-which 1.0.4 (core)",
                "@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
                "alias 2.1.0 (core)",
                "apex 0.13.0 (core)",
                "auth 2.2.0 (core)",
                "community 2.0.0 (core)",
                "config 1.4.12 (core)",
                "custom-metadata 2.0.0 (core)",
                "data 2.0.4 (core)",
                "generator 2.0.1 (core)",
                "info 2.0.1 (core)",
                "limits 2.0.1 (core)",
                "org 1.13.2 (core)",
                "salesforce-alm 54.6.0 (core)",
                "schema 2.1.1 (core)",
                "sfdx-cli 7.156.1 (core)",
                "signups 1.2.0 (core)",
                "source 2.0.2 (core)",
                "telemetry 2.0.0 (core)",
                "templates 55.0.0 (core)",
                "trust 2.0.1 (core)",
                "user 2.1.0 (core)"
        ],
        "osVersion": "Darwin 21.5.0"
}

Additional information

Screenshot 2022-06-25 at 15 31 40

@amtrack amtrack added the investigating We're actively investigating this issue label Jun 25, 2022
@github-actions
Copy link

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.

@maggiben maggiben added feature Issue or pull request for a new feature and removed investigating We're actively investigating this issue labels Jul 5, 2022
@github-actions
Copy link

github-actions bot commented Jul 5, 2022

Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments.

@git2gus
Copy link

git2gus bot commented Jul 5, 2022

This issue has been linked to a new work item: W-11385847

@github-actions github-actions bot added the stale label Sep 21, 2022
@forcedotcom forcedotcom deleted a comment from github-actions bot Sep 21, 2022
@RodEsp RodEsp removed the stale label Sep 21, 2022
@forcedotcom forcedotcom locked and limited conversation to collaborators Aug 1, 2023
@WillieRuemmele WillieRuemmele converted this issue into discussion #2356 Aug 1, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
custom-registry feature Issue or pull request for a new feature
Projects
None yet
Development

No branches or pull requests

4 participants