Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Org Browser unable to retrieve GlobalValueSet
See original GitHub issueSummary
Org Browser can’t retrieve any GlobalValueSets.
Steps To Reproduce:
- Have/create a Picklist Value Set
- Connect to Org in VSCode
- Open Org Browser
- Go to GlobalValueSet category
- Press any of the two buttons to retrieve it
Expected result
Retrieve the selected GlobalValueSet metadata.
Actual result
Fails to retrieve. VSCode “Salesforce CLI” Output panel shows:
Starting SFDX: Retrieve Source from Org
=== Retrieve Warnings
FULL NAME TYPE MESSAGE
────────────────────── ────────────── ──────────────────────────────────────────────────────────────────────────────
Review_Root_Cause__gvs GlobalValueSet Entity of type 'GlobalValueSet' named 'Review_Root_Cause__gvs' cannot be found
ended SFDX: Retrieve Source from Org
Additional information
The problem is probably from the __gvs suffix being included in the request fired by the Org Browser.
I say this because attempting to retrieve using the CLI is successful when omitting the suffix:
PS > sfdx force:source:retrieve -m GlobalValueSet:Review_Root_Cause__gvs
Preparing retrieve request... done
=== Retrieved Source
No results found
=== Retrieved Source Warnings
FILE NAME PROBLEM
────────────────────── ──────────────────────────────────────────────────────────────────────────────
unpackaged/package.xml Entity of type 'GlobalValueSet' named 'Review_Root_Cause__gvs' cannot be found
PS > sfdx force:source:retrieve -m GlobalValueSet:Review_Root_Cause
Preparing retrieve request... done
=== Retrieved Source
FULL NAME TYPE PROJECT PATH
───────────────── ────────────── ────────────────────────────────────────────────────────────────────────────────
Review_Root_Cause GlobalValueSet force-app\main\default\globalValueSets\Review_Root_Cause.globalValueSet-meta.xml
PS >
Salesforce Extension Version in VS Code: 55.8.0
SFDX CLI Version: 7.165.0
OS and version: Windows 11 Pro, Version 21H2, Build 22000.856
Screenshots
How it shows up in the Org Browser:
How the Picklist Value Set looks in the org:
Demonstrating __gvs can’t be something named by the user:
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Retrieve Standard Value Sets in Org Browser #1579 - GitHub
Summary. No Standard Value Set visible in Org Browser. Steps To Reproduce: Open Org Browser. Click on Standard Value Sets. Expected result.
Read more >Cannot change which global value set this picklist use
Deploying picklist fields in Copado, you might receive a deployment error that looks like this: "Cannot change which global value set this ...
Read more >apex - Retrieve Globalvalueset without Object_API_Name and ...
I want to retrieve all the picklist values of the Global Value Set without using the Object name and the field name. –...
Read more >Packaged GlobalValueSet picklist values not getting updated ...
Retrieve the Metadata of the same GlobalValueSet from subscriber Org and update the picklist values in the metadata file .
Read more >Populate a Custom Picklist with a Global Value Set - Tether
Firstly themes and branding sets the Org aside from all other Greenfield Orgs, and then we get into Record Types, Page Layouts and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@49FD7E1E1F Thank you for the additional detail and screenshots! Very helpful. It looks like this issue might be caused by this change in the Winter '23 release. I am working on reproducing the issue locally and will provide an update when I am able to repro.
Yes, let’s re-open if this change gets added back into the next release in the same way and the issue re-appears. Thanks again for all of the additional info while investigating this one.