> For the complete documentation index, see [llms.txt](https://boomi.markusschmidt.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boomi.markusschmidt.pro/boomi-console/commands/arguments/common-arguments/command-sources.md).

# Component Resolution

In addition to specifying a `/ComponentId` as an explicit argument there are additional ways how to *feed* a command with components:

{% hint style="info" %}
Before the command starts executing, a so called **component resolution** takes places, to resolve all those component ids which will be used for the current action.
{% endhint %}

The simplest way to provide a component id is to specify it explicitly as an [argument](/boomi-console/commands/arguments/common-arguments.md). In addition, you can specify a `/QueryFilter` or `/ComponentsSet` as the source for components. Last but not least you can refer to a `/Folder` in your repository or you specify a `/PackageVersion` . In any case, components are resolved from all provided sources you specify and the command runs with the resolved list of all these components.

If you use multiple parameters, like `/ComponentId` and `/QueryFilter`, the command will use the aggregate of all references components (additive).

## See also

* [Query Filter](/boomi-console/commands/arguments/common-arguments/query-files.md)
* [Component Set](/boomi-console/library/packages.md)
* [Common Arguments](/boomi-console/commands/arguments/common-arguments.md#folder-f)
* [Common Arguments](/boomi-console/commands/arguments/common-arguments.md#packageversion-pv)
