# GET

Get [Component Metadata](https://help.boomi.com/bundle/developer_apis/page/int-Component_object.html) from Runtime and write it to the [Out-Folder](/boomi-console/commands/arguments/common-arguments.md#outdir-o). OPtionally you can specify a template to render information about all components.

```batch
bc COMP GET /c 54222e4e-e9c1-490b-... -t compList.csv
```

{% content-ref url="/pages/IDKspyJTd0wqVKM1Nyyo" %}
[COMP GET Arguments](/boomi-console/commands/arguments/comp-arguments/comp-get-arguments.md)
{% endcontent-ref %}

The command uses a [resolved list of components](/boomi-console/commands/arguments/common-arguments/command-sources.md#component-resolution) and [recurses over parent(s) and children](/boomi-console/commands/arguments/common-arguments.md#component-trees) to:

1. store all metadata in the `<OutDir>\MetaData` folder
2. store human-readable and re-usbale Component information like SQL statements, Scripts, profiles in `<OutDir>\Components`folder
3. Optionally, [specify a template](/boomi-console/commands/arguments/common-arguments.md#templates) to render the list of all components.

<figure><img src="/files/WjnycHXKoFtr28qAu0By" alt=""><figcaption><p>Visual Studio Code shows Components rendered using /t compList.CSV</p></figcaption></figure>

#### Find orphaned components

*comList.CSV* reports the number of parents and children of each component. Components with 0 parents could be orphaned. For *Processes* it can be ok to have zero parents, a mapping with zero parents is simply not referenced: orphaned and subject for deletion.

#### Component Folder Structure

It is vital that you maintain a good folder structure. The COMP GET command tells you where all child and parent components are located.

If you look carefully at the image above, you will see that my process references a script in `99 - ParkingLot` folder. This was definitely not my intention.

#### Components unleashed

If you want to see your raw script, Json profiles or SQL statements, the `Components` folder is right for you.

<figure><img src="/files/KxIhkRTxXKJdzzKo9JbW" alt=""><figcaption><p>The RAW Groovy script as a file in the file-system.</p></figcaption></figure>

#### Metadata as XML files

If you want to know where you have used a document property, you may want to search all your `Metadata` XML files.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://boomi.markusschmidt.pro/boomi-console/commands/comp-components/fetch-get.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.