SFDX Org Browser is missing metadata types (profiles, InstalledPackage, and more) #5784
Replies: 5 comments
-
|
Hi @peternoges , thanks for opening this question. The answer to this is that it depends on the entity/object. I can confirm we won't be adding InstalledPackages and Profiles. The reason for this is that installing packages is done through the use of the cli command For Profiles it's a bit different, we do not support it in Org Browser because it's not possible to retrieve a correct metadata shape for a Profile without retrieving every potential piece of metadata associated with it, that is just a limitation of the APIs. For standard objects, we do support them but they are currently being embedded under For ProfileSessionSetting & ProfilePasswordPolicies, we might've removed those from the Org Browser cause of the way that they were supported back when Org Browser was first released but we can take a look at it. |
Beta Was this translation helpful? Give feedback.
-
|
@lcampos - with the limitation of profiles not being included in org browser, what is the best alterative? |
Beta Was this translation helpful? Give feedback.
-
|
Hey @lcampos! thanks very much for the discussion. Here's an update about the multiple requests to support more types within SFDX OrgBrowser; I've also recently included sfdx/os version info in to my original post. Disregard 1, but what are your thoughts on 2,3,4?
|
Beta Was this translation helpful? Give feedback.
-
|
Hey all - I have re-written the original post with a revised perspective of the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @peternoges . We are planning some work on Org Browser this year and will consider this feedback as we do. As @lcampos mentioned above, a couple of the types you're interested in aren't possible at add but a couple might be. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Recap:
Steps To Reproduce:
Expected result
Ideally we'd see the types from step 2 within orgbrowsers tree.
Actual result
The types from step 2 dont appear in orgbrowsers tree
Additional information
December 30, 2020 Edit:
This post questions why some metadatatypes are missing from orgbrowser's ui tree; standard objects do appear, so i've revised the repo steps and write-up.
VS Code Version:

SFDX CLI Version:
sfdx-cli/7.74.1 win32-x64 node-v12.16.1
OS and version:
Windows 10
Beta Was this translation helpful? Give feedback.
All reactions