- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip coder
- uip context-grounding
- uip docsai
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- create-project
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-library-object-repository
- get-object-repository
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-instances
- list-workflow-examples
- pack
- publish
- remote
- restore
- run, debug & execution
- run-file
- search-templates
- start-studio
- stop-execution
- tm
- uia
- uip tasks
- uip traces
- uip traces feedback
- Migration
- Reference & support
Syntax and options for `uip rpa get-object-repository`, which returns the current project's own Object Repository as a JSON tree.
uip rpa get-object-repository returns the current project's own Object Repository — the applications, screens, and elements it defines — as a JSON tree. It excludes entries inherited from referenced libraries; use uip rpa get-library-object-repository to read those separately.
The verb runs inside a hosted project context on both backends (Studio's project process and Helm's project assembly load context), so a project must be open before it can be called.
Synopsis
uip rpa get-object-repository
uip rpa get-object-repository
Options
This verb takes no per-command options. Use the parent-level options shared by every uip rpa verb — see RPA tool overview.
Examples
# Read the current project's Object Repository
uip rpa get-object-repository
# Read the current project's Object Repository
uip rpa get-object-repository
Data shape (--output json)
The command returns the Object Repository tree exactly as objectRepository.getProjectObjects() produces it — apps, then screens, then elements, nested to match the repository's own structure. Shape is otherwise unspecified and may evolve with the Object Repository feature itself; inspect a real project's output rather than relying on a fixed schema.
On failure (for example, no project is open), the command reports:
{
"success": false,
"errorMessage": "<reason>"
}
{
"success": false,
"errorMessage": "<reason>"
}
Related
uip rpa get-library-object-repository— the equivalent read for a library.nupkg's own Object Repository, rather than the open project's.