You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user has customised an object shipped in Managed Package vscode metadata org browser should let them download that custom object.
Steps To Reproduce:
Find a managed package that contains an object
Create a sandbox (e.g. dev sandbox off of production)
Install the managed package
Create a new field in the object in this package (such that the object has a prefix e.g. myprefix__My_Object__c but your NEW field does not (myprefix__My_Object__c.Our_Field__c)
Refresh 'custom objects' in metadata org browser in VS Code
Expected result
myprefix__My_Object__c is listed
Actual result
myprefix__My_Object__c is NOT listed
Additional information
Workaround: create the myprefix__My_Object__c folder under objects, add the corresponding xml file (even empty), right-click -> Retrieve source from org.
The fact that the workaround works suggests that there is no API limitation on downloading this data, it's just the SFDX extension chooses not to show it to users.
Hi @az-oolloow - The org browser does not display metadata inside of managed packages because that metadata cannot be retrieved (metadata retrieve) by a subscriber. We have an open issue on this - #1998. If you get a chance, please add any other use cases you have to that issue. I'm going to close this one as a duplicate to keep one place to track on this.
Summary
If a user has customised an object shipped in Managed Package vscode metadata org browser should let them download that custom object.
Steps To Reproduce:
myprefix__My_Object__c
but your NEW field does not (myprefix__My_Object__c.Our_Field__c
)Expected result
myprefix__My_Object__c
is listedActual result
myprefix__My_Object__c
is NOT listedAdditional information
Workaround: create the
myprefix__My_Object__c
folder underobjects
, add the corresponding xml file (even empty), right-click ->Retrieve source from org
.The fact that the workaround works suggests that there is no API limitation on downloading this data, it's just the SFDX extension chooses not to show it to users.
VS Code Version:
Version: 1.44.2
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T17:07:18.473Z (1 wk ago)
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0
SFDX CLI Version: 48.11.0
OS and version: macOS Catalina 10.15.3
The text was updated successfully, but these errors were encountered: