Skip to content
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

cannot find members of StandardValueSet by "sfdx force:source:manifest:create" #1877

Closed
takahitomiyamoto opened this issue Jan 13, 2023 · 8 comments
Labels
bug Issue or pull request that identifies or fixes a bug

Comments

@takahitomiyamoto
Copy link

takahitomiyamoto commented Jan 13, 2023

Summary

In order to create a package.xml automatically, I ran the command sfdx force:source:manifest:create --apiversion 56.0 --fromorg demo -o manifest -t package. When I checked the package.xml, I cannot find the tag <name>StandardValueSet</name> .

Steps To Reproduce:

scoop update nvm
nvm version   # 1.1.10
nvm install 18.13.0
nvm use 18.13.0
node -v   # v18.13.0
npm -v   # 8.19.3
npm install -g [email protected]
sfdx -v   # sfdx-cli/7.183.1 win32-x64 node-v18.13.0
sfdx force:project:create -x -n demo
cd demo
sfdx force:source:manifest:create --apiversion 56.0 --fromorg demo -o manifest -t package

Expected result

I can find the tag <name>StandardValueSet</name> in the manifest/package.xml .

Actual result

I cannot find the tag <name>StandardValueSet</name> in the manifest/package.xml .

System Information

  • Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)

PowerShell 7.3.1

  • If you are using sfdx
    • Run sfdx version --verbose --json
{
  "cliVersion": "sfdx-cli/7.183.1",
  "architecture": "win32-x64",
  "nodeVersion": "node-v18.13.0",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 1.3.8 (core)",
    "@oclif/plugin-commands 2.2.2 (core)",
    "@oclif/plugin-help 5.1.20 (core)",
    "@oclif/plugin-not-found 2.3.13 (core)",
    "@oclif/plugin-plugins 2.1.8 (core)",
    "@oclif/plugin-search 0.0.6 (core)",
    "@oclif/plugin-update 3.0.9 (core)",
    "@oclif/plugin-version 1.1.4 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.18 (core)",
    "@oclif/plugin-which 2.2.6 (core)",
    "alias 2.1.14 (core)",
    "apex 1.3.0 (core)",
    "auth 2.3.8 (core)",
    "community 2.0.18 (core)",
    "config 1.4.22 (core)",
    "custom-metadata 2.0.5 (core)",
    "data 2.1.19 (core)",
    "generator 2.0.13 (core)",
    "info 2.3.1 (core)",
    "limits 2.2.0 (core)",
    "org 2.2.20 (core)",
    "packaging 1.12.2 (core)",
    "schema 2.2.2 (core)",
    "signups 1.2.12 (core)",
    "source 2.3.12 (core)",
    "telemetry 2.0.5 (core)",
    "templates 55.1.0 (core)",
    "trust 2.2.4 (core)",
    "user 2.1.24 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
    "heat-sfdx-cli 0.3.3 (user)",
    "salesforce-alm 54.8.5 (core)",
    "sfdx-plugin-prettier 1.0.5 (user)",
    "sfpowerkit 5.0.0 (user)"
  ],
  "osVersion": "Windows_NT 10.0.22000",
  "shell": "cmd.exe",
  "rootPath": "C:\\Users\\takahito.miyamoto\\scoop\\persist\\nvm\\nodejs\\v18.13.0\\node_modules\\sfdx-cli"
}

Additional information

By the way, when I use Org Browser in VS Code for the same sandbox, I can find the members of StandardValueSet.

image

@takahitomiyamoto takahitomiyamoto added the investigating We're actively investigating this issue label Jan 13, 2023
@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.

@WillieRuemmele
Copy link
Member

Hi @takahitomiyamoto - I used the dreamhouse project, and then created a manifest with that command. I see

        <members>TaskSubject</members>
        <members>TaskType</members>
        <members>WorkOrderLineItemStatus</members>
        <members>WorkOrderPriority</members>
        <members>WorkOrderStatus</members>
        <name>StandardValueSet</name>
    </types>

in the manifest. I would check your .forceignore file to see if maybe they're ignored?

@takahitomiyamoto
Copy link
Author

@WillieRuemmele Thanks, but my .forceignore file was not changed from default. Please see here:

# List files or directories below to ignore them when running force:source:push, force:source:pull, and force:source:status
# More information: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_exclude_source.htm
#

package.xml

# LWC configuration files
**/jsconfig.json
**/.eslintrc.json

# LWC Jest
**/__tests__/**

Are you using a developer edition org or a sandbox org ?

@SabariRavi
Copy link

Hi ,

  • This issue affected me too , with the version sfdx-cli/7.183.1 , we cannot reterive the StandardValueSet
  • .forceignore , previusoly ignored quickaction , permission set and some roles too getting retirived. Not all the files are retrieved but some files.
    image

@WillieRuemmele
Copy link
Member

Hi @takahitomiyamoto - I was using a scratch org for this, I'll spin up a sandbox and test... Did this start happening after a specific release?

@WillieRuemmele WillieRuemmele added bug Issue or pull request that identifies or fixes a bug and removed investigating We're actively investigating this issue labels Jan 18, 2023
@git2gus
Copy link

git2gus bot commented Jan 18, 2023

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

@shetzel
Copy link
Contributor

shetzel commented Jan 26, 2023

UPDATE: This is fixed in the current CLI release candidate, v7.186.0 which will be promoted in a week.

@shetzel
Copy link
Contributor

shetzel commented Feb 3, 2023

The fix is now in the current production CLI, v7.186.2.

@shetzel shetzel closed this as completed Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug
Projects
None yet
Development

No branches or pull requests

4 participants