Disable ads (and more) with a premium pass for a one time $4.99 payment
An orchestrator asset is designed to store various types of configuration data that robots will use at runtime. The types that can typically be stored include simple data types like strings, numbers, and assets that are specifically designed to handle credentials and URLs for easy access during automation tasks.
However, a table, which inherently consists of multiple rows and columns and represents a more complex data structure, cannot be stored directly as an orchestrator asset. Assets are intended for straightforward key-value pairs that can easily be retrieved or updated without the complexity of parsing multi-dimensional data structures. While individual elements can represent parts of a table, the orchestrator's asset system does not support storing the entire table as a single asset because it would exceed the basic intended usage of assets in UiPath automation.
Thus, the inability to store a table as an orchestrator asset signifies a limitation of the orchestrator’s asset management, as it focuses on simplicity and ease of retrieval rather than handling complex data formats. This means data structures that require relationships and multiple dimensions, like tables, must be handled through alternative means, such as using databases or Excel files.