Skip to content

Issues with retrieving some metadata using the output directory option #3177

@Alfystar

Description

@Alfystar

Description:

Hi team,

We have encountered a problem while using the sf project retrieve start command with the --output-dir option. The anomaly is that main/default appears in the output directory.

/retrievePack/main/default
└─▶ $ tree
.
├── LeadConvertSettings
│   └── LeadConvertSettings.LeadConvertSetting-meta.xml
├── escalationRules
│   └── Case.escalationRules-meta.xml
├── lightningExperienceThemes
│   └── STILE.lightningExperienceTheme-meta.xml
├── notificationTypeConfig
│   └── NotificationTypeConfig.config-meta.xml
├── redirectWhitelistUrls
│   └── https_quenda_enel_com.redirectWhitelistUrl-meta.xml
├── sharingSets
│   └── Permisos_APP_Customer_Community_Ar.sharingSet-meta.xml
└── standardValueSetTranslations
    └── WorkOrderStatus-pt_BR.standardValueSetTranslation-meta.xml

However, we observed that for the StandardValueSetTranslation metadata, there were 2 other package.xml files with the same type (different resources) and both of these retrieves were saved correctly. We have also empirically observed that all these problematic packages are retrieves containing only one file, but we have no direct proof of a connection.

Packages XML:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>LeadConvertSettings</members>
        <name>LeadConvertSettings</name>
    </types>
</Package>

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Case</members>
        <name>EscalationRules</name>
    </types>
</Package>

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>STILE</members>
        <name>LightningExperienceTheme</name>
    </types>
</Package>

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>NotificationTypeConfig</members>
        <name>NotificationTypeConfig</name>
    </types>
</Package>

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>https_quenda_enel_com</members>
        <name>RedirectWhitelistUrl</name>
    </types>
</Package>

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Permisos_APP_Customer_Community_Ar</members>
        <name>SharingSet</name>
    </types>
</Package>

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>WorkOrderStatus-pt_BR</members>
        <name>StandardValueSetTranslation</name>
    </types>
</Package>

We are sending all the package.xml files concatenated together, generated with the following command:

cat package_LeadConvertSettings_0.xml cat package_EscalationRules_0.xml package_LightningExperienceTheme_0.xml package_NotificationTypeConfig_0.xml package_RedirectWhitelistUrl_0.xml package_SharingSet_0.xml package_StandardValueSetTranslation_2.xml

Commands used:

sf project retrieve start --target-org SYSTEST01 --ignore-conflicts --manifest fullRetrieve_Artifact/package_LeadConvertSettings_0.xml --output-dir fullRetrieve_Artifact/retrievePack/dir_660 --wait 240
sf project retrieve start --target-org SYSTEST01 --ignore-conflicts --manifest fullRetrieve_Artifact/package_EscalationRules_0.xml --output-dir fullRetrieve_Artifact/retrievePack/dir_609 --wait 240
sf project retrieve start --target-org SYSTEST01 --ignore-conflicts --manifest fullRetrieve_Artifact/package_LightningExperienceTheme_0.xml --output-dir fullRetrieve_Artifact/retrievePack/dir_665 --wait 240
sf project retrieve start --target-org SYSTEST01 --ignore-conflicts --manifest fullRetrieve_Artifact/package_NotificationTypeConfig_0.xml --output-dir fullRetrieve_Artifact/retrievePack/dir_679 --wait 240
sf project retrieve start --target-org SYSTEST01 --ignore-conflicts --manifest fullRetrieve_Artifact/package_RedirectWhitelistUrl_0.xml --output-dir fullRetrieve_Artifact/retrievePack/dir_153 --wait 240
sf project retrieve start --target-org SYSTEST01 --ignore-conflicts --manifest fullRetrieve_Artifact/package_SharingSet_0.xml --output-dir fullRetrieve_Artifact/retrievePack/dir_222 --wait 240
sf project retrieve start --target-org SYSTEST01 --ignore-conflicts --manifest fullRetrieve_Artifact/package_StandardValueSetTranslation_2.xml --output-dir fullRetrieve_Artifact/retrievePack/dir_234 --wait 240 

Example of command output:

[Count Retry: 0]$> sf project retrieve start --target-org SYSTEST01 --ignore-conflicts --manifest fullRetrieve_Artifact/package_StandardValueSetTranslation_2.xml --output-dir fullRetrieve_Artifact/retrievePack/dir_227 --wait 240
───── Retrieving Metadata ─────
Stages:
1. Preparing retrieve request
2. Sending request to org
3. Waiting for the org to respond
4. Done

▶ Preparing retrieve request…
✔ Preparing retrieve request (1ms)
▶ Sending request to org…
   Retrieving v62.0 metadata from chandrahasa.pottennagari@enel.com.prod.systest using the v62.0 SOAP API
✔ Sending request to org (602ms)
   Status: Pending
▶ Waiting for the org to respond…
   Status: In Progress
✔ Waiting for the org to respond (50.09s)
   Status: Succeeded
▶ Done…
✔ Done (0ms)

Retrieving v62.0 metadata from chandrahasa.pottennagari@enel.com.prod.systest using the v62.0 SOAP API
Status: Succeeded

Elapsed time: 50.69s

Retrieved Source
 State    Name                   Type                         Path
 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 Created  WorkOrderStatus-pt_BR  StandardValueSetTranslation  fullRetrieve_Artifact/retrievePack/dir_227/main/default/standardValueSetTranslations/WorkOrderStatus-pt_BR.standardValueSetTranslation-meta.xml

[StandardValueSetTranslation_2] Done.

We appreciate any help or suggestions you can provide to resolve this issue.

Thank you again for all your support!

System Information

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.71.6",
  "nodeVersion": "node-v23.4.0",
  "osVersion": "Darwin 24.2.0",
  "rootPath": "/opt/homebrew/lib/node_modules/@salesforce/cli",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.14 (core)",
    "@oclif/plugin-commands 4.1.14 (core)",
    "@oclif/plugin-help 6.2.19 (core)",
    "@oclif/plugin-not-found 3.2.31 (core)",
    "@oclif/plugin-plugins 5.4.22 (core)",
    "@oclif/plugin-search 1.2.17 (core)",
    "@oclif/plugin-update 4.6.18 (core)",
    "@oclif/plugin-version 2.2.18 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.28 (core)",
    "@oclif/plugin-which 3.2.21 (core)",
    "@salesforce/cli 2.71.6 (core)",
    "apex 3.6.8 (core)",
    "api 1.3.2 (core)",
    "auth 3.6.82 (core)",
    "data 3.13.5 (core)",
    "deploy-retrieve 3.16.0 (core)",
    "info 3.4.29 (core)",
    "limits 3.3.43 (core)",
    "marketplace 1.3.7 (core)",
    "org 5.2.11 (core)",
    "packaging 2.9.7 (core)",
    "schema 3.3.45 (core)",
    "settings 2.4.9 (core)",
    "sobject 1.4.46 (core)",
    "telemetry 3.6.27 (core)",
    "templates 56.3.34 (core)",
    "trust 3.7.51 (core)",
    "user 3.6.5 (core)",
    "sfdx-plugin-source-read 1.4.1 (user) published 25 days ago (Fri Dec 20 2024)"
  ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue or pull request that identifies or fixes a bugvalidatedVersion information for this issue has been validated

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions