Assets Update and Bucket creation using Uipath CLI

Help Orchestrator
1

Hi Everyone,

I’m facing issue while updating assets using CLI although I’m able to create the assets. Same with storage bucket as well.

The image displays an error message in a code editor indicating that 'assetDto must not be null,' accompanied by additional debugging information including an error code and a trace ID. (Captioned by AI)
The image displays an error message in a code editor indicating that 'assetDto must not be null,' accompanied by additional debugging information including an error code and a trace ID. (Captioned by AI)1917×119 4.66 KB

error for storage bucket.

This image displays an error message from a command-line interface command related to UiPath Orchestrator, indicating a missing or undefined storage bucket. (Captioned by AI)
This image displays an error message from a command-line interface command related to UiPath Orchestrator, indicating a missing or undefined storage bucket. (Captioned by AI)1108×142 6.97 KB

Regards,
Ankit

Forum Engagement Daily Reports
2

@Codeverse

are you using same format

# Create new Text asset
uipath orchestrator assets post --folder-id "$folderId" \
                                --name "MyAsset" \
                                --value-scope "Global" \
                                --value-type "Text" \
                                --string-value "my-value"

cheers

3

Hi @Anil_G Thanks for reply

I’m trying to update the assets using this command uipath orchestrator assets put-by-id --folder-id "4771090" --name "Outlook Account" --value-scope "Global" --value-type "Text" --string-value "Text" --key "1301006" { "errorCode": 0, "message": "; assetDto must not be null", "traceId": "00-646baa90c7d7e9dbd712fd9da3953ea4-50b3f3001ec6fe2a-00" }

Getting this error.

Although above command is working for me to create a new asset.

Can you please look for this.

4

The issue with updating assets or buckets is usually related to one of the following:

  1. Incorrect Syntax or Missing Parameters:
    Updating via CLI often requires specific flags like --id or --name. If you’re missing a required field (like asset ID or storage bucket name), the update will fail. Double-check the syntax for the update command you’re using.
  2. Asset or Bucket Not Found:
    If you’re using the name to update, make sure the name exactly matches the one in Orchestrator — it’s case-sensitive. Or even better, try using the unique ID if possible.
  3. Permissions Issue:
    Even if you can create resources, updating them might require different permissions depending on your role. Make sure the robot/user running the CLI has proper rights to update existing assets or buckets.
  4. CLI Version Mismatch or Bugs:
    Sometimes certain CLI versions have known bugs. It’s worth updating to the latest version of UiPath CLI to rule that out.

If you can share the exact command and error message you’re getting (especially for the storage bucket one), I could help troubleshoot more precisely — but most likely it’s either a missing parameter or the resource not being identified correctly during the update call.

5

Use Full Payload for Updates

Updating requires all fields (not just the ones you’re changing).
Include --id, --name, --value-type, and --string-value for assets.
Use put-by-id Instead of post or patch

For assets:

Check Folder ID and Permissions

Ensure you’re using the correct --folder-id and have update permissions.
Storage Buckets May Require Re-creation

If update fails, delete and re-create with new values.
Use Latest CLI Version

Update UiPath CLI to avoid bugs in older versions.

6

Hi @sai_gupta

I have used the same full payload uipath orchestrator assets put-by-id --folder-id "4771090" --name "Outlook Account" --value-scope "Global" --value-type "Text" --string-value "Text" --key "1301006"

But getting this error

image
image657×101 2.79 KB