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
Use this command to identify individual components in your manifest file or if you want a high-level view of particular metadata types in your org. For example, you can use this command to return a list of names of all the CustomObject or Layout components in your org, then use this information in a retrieve command that returns a subset of these components.
4
+
5
+
The username that you use to connect to the org must have the Modify All Data or Modify Metadata Through Metadata API Functions permission.
6
+
7
+
# summary
8
+
9
+
List the metadata components and properties of a specified type.
10
+
11
+
# examples
12
+
13
+
- List the CustomObject components, and their properties, in the org with alias "my-dev-org":
- List the Dashboard components in your default org that are contained in the "folderSales" folder, write the output to the specified file, and use API version 57.0:
The information includes Apex classes and triggers, custom objects, custom fields on standard objects, tab sets that define an app, and many other metadata types. Use this information to identify the syntax needed for a <name> element in a manifest file (package.xml).
4
+
5
+
The username that you use to connect to the org must have the Modify All Data or Modify Metadata Through Metadata API Functions permission.
6
+
7
+
# summary
8
+
9
+
Display details about the metadata types that are enabled for your org.
10
+
11
+
# examples
12
+
13
+
- Display information about all known and enabled metadata types in the org with alias "my-dev-org" using API version 57.0:
API version to use; default is the most recent API version.
24
+
25
+
# flags.output-file.summary
26
+
27
+
Pathname of the file in which to write the results.
28
+
29
+
# flags.filter-known.summary
30
+
31
+
Filter the known metadata types from the result to display only the types not yet fully supported by Salesforce CLI.
32
+
33
+
filter metadata known by the CLI
34
+
35
+
# flags.output-file.description
36
+
37
+
Directing the output to a file makes it easier to extract relevant information for your package.xml manifest file. The default output destination is the terminal or command window console.
Copy file name to clipboardExpand all lines: messages/open.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,8 @@ Open your default scratch org, or another specified org, in a browser.
6
6
7
7
To open a specific page, specify the portion of the URL after "https://MyDomainName.my.salesforce.com/" as the value for the --path flag. For example, specify "--path lightning" to open Lightning Experience, or specify "--path /apex/YourPage" to open a Visualforce page.
8
8
9
+
Use the --source-file to open a Lightning Page from your local project in Lightning App Builder. Lightning page files have the suffix .flexipage-meta.xml, and are stored in the "flexipages" directory.
10
+
9
11
To generate a URL but not launch it in your browser, specify --url-only.
10
12
11
13
To open in a specific browser, use the --browser flag. Supported browsers are "chrome", "edge", and "firefox". If you don't specify --browser, the org opens in your default browser.
@@ -24,10 +26,18 @@ To open in a specific browser, use the --browser flag. Supported browsers are "c
0 commit comments