|
1 | 1 | # summary
|
2 | 2 |
|
3 |
| -convert metadata from the Metadata API format into the source format |
| 3 | +Convert metadata retrieved via Metadata API into the source format used in Salesforce DX projects. |
4 | 4 |
|
5 | 5 | # description
|
6 | 6 |
|
7 |
| -Converts metadata retrieved via Metadata API into the source format used in Salesforce DX projects. |
| 7 | +To use Salesforce CLI to work with components that you retrieved via Metadata API, first convert your files from the metadata format to the source format using this command. |
8 | 8 |
|
9 |
| -To use Salesforce CLI to work with components that you retrieved via Metadata API, first convert your files from the metadata format to the source format using "sfdx force:mdapi:convert". |
10 |
| - |
11 |
| -To convert files from the source format back to the metadata format, so that you can deploy them using "<%= config.bin %> project deploy", run "<%= config.bin %> project convert source". |
| 9 | +To convert files from the source format back to the metadata format, run "<%= config.bin %> project convert source". |
12 | 10 |
|
13 | 11 | # examples
|
14 | 12 |
|
15 |
| -- $ <%= config.bin %> <%= command.id %> -r path/to/metadata |
16 |
| - |
17 |
| -- $ <%= config.bin %> <%= command.id %> -r path/to/metadata -d path/to/outputdir |
18 |
| - |
19 |
| -# flags.root-dir |
20 |
| - |
21 |
| -the root directory containing the Metadata API–formatted metadata |
22 |
| - |
23 |
| -# flags.output-dir |
24 |
| - |
25 |
| -the output directory to store the source–formatted files |
| 13 | +- Convert metadata formatted files in the specified directory into source formatted files; writes converted files to your default package directory: |
26 | 14 |
|
27 |
| -# flags.manifest |
| 15 | + $ <%= config.bin %> <%= command.id %> --root-dir path/to/metadata |
28 | 16 |
|
29 |
| -file path to manifest (package.xml) of metadata types to convert. |
| 17 | +- Similar to previous example, but writes converted files to the specified output directory: |
30 | 18 |
|
31 |
| -# flags.metadata-path |
| 19 | + $ <%= config.bin %> <%= command.id %> --root-dir path/to/metadata --output-dir path/to/outputdir |
32 | 20 |
|
33 |
| -comma-separated list of metadata file paths to convert |
| 21 | +# flags.root-dir.summary |
34 | 22 |
|
35 |
| -# flags.metadata |
| 23 | +Root directory that contains the Metadata API–formatted metadata. |
36 | 24 |
|
37 |
| -comma-separated list of metadata component names to convert |
| 25 | +# flags.output-dir.summary |
38 | 26 |
|
39 |
| -# flagsLong.root-dir |
| 27 | +Directory to store your files in after they’re converted to source format; can be an absolute or relative path. |
40 | 28 |
|
41 |
| -The root directory that contains the metadata you retrieved using Metadata API. |
| 29 | +# flags.manifest.summary |
42 | 30 |
|
43 |
| -# flagsLong.output-dir |
| 31 | +File path to manifest (package.xml) of metadata types to convert. |
44 | 32 |
|
45 |
| -The directory to store your files in after they’re converted to the source format. Can be an absolute or relative path. |
| 33 | +# flags.metadata-path.summary |
46 | 34 |
|
47 |
| -# flagsLong.manifest |
| 35 | +Comma-separated list of paths to the local metadata files to convert. |
48 | 36 |
|
49 |
| -- The complete path to the manifest (package.xml) file that specifies the metadata types to convert. |
| 37 | +# flags.metadata.summary |
50 | 38 |
|
51 |
| -- If you specify this parameter, don’t specify --metadata or --source-path. |
| 39 | +Comma-separated list of metadata component names to convert. |
52 | 40 |
|
53 |
| -# flagsLong.metadata-path |
| 41 | +# flags.manifest.description |
54 | 42 |
|
55 |
| -- A comma-separated list of paths to the local metadata files to convert. The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories). |
| 43 | +If you specify this parameter, don’t specify --metadata or --source-path. |
56 | 44 |
|
57 |
| -- If you specify this parameter, don’t specify --manifest or --metadata. If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of double quotes. |
| 45 | +# flags.metadata-path.description |
58 | 46 |
|
59 |
| -# flagsLong.metadata |
| 47 | +The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories). |
60 | 48 |
|
61 |
| -A comma-separated list of metadata component names to convert. |
| 49 | +If you specify this flag, don’t specify --manifest or --metadata. If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of double quotes. |
62 | 50 |
|
63 | 51 | # expectedDirectory
|
64 | 52 |
|
|
0 commit comments