DEV Community: Jaeyoung Jung

Package cannot be published to the shared feed

Jaeyoung Jung — Fri, 01 Nov 2024 04:07:35 +0000

PROBLEM

While publishing template to the shared feed, the error occurred same with the title.

CAUSE

Trying deployment of library on tenant feed when it is allowed only for host feed.

SOLUTION

Allow deployment of library to both host and tenant feeds on orchestrator.

Go to Tenant
Go to Settings
Go to Deployment

Go to Libraries
Check Both host and tenant feeds on Feeds
Check Internal on Deployment
Check Secure Deployment on Security
Save

Json Payload for Orchestrator Http Request Activity with Get Method

Jaeyoung Jung — Fri, 01 Nov 2024 01:16:55 +0000

PROBLEM

Conditions on Json Payload field for orchestrator http request activity with Get method are not applied to the response.

CAUSE

Http request with Get method doesn’t receive json Payload because the conditions are set on the URL.

SOLUTION

With Get method, empty Json Payload field and put the conditions on the URL.

Missing Required Key in Body of PUT /odata/Assets({Key}) Edit an asset on UiPath.WebApi 18.0

Jaeyoung Jung — Fri, 01 Nov 2024 01:07:32 +0000

PROBLEM

While Editing an asset with orchestrator API, even though put all required keys in body(AssetDto), 404 error occurred with “Asset does not exist”.

CAUSE

In the body(AssetDto), Name and ValueScope are marked as required keys. However Id is also required key.

SOLUTION

Add Id in the body.

Could not connect to the server (#101)

Jaeyoung Jung — Fri, 01 Nov 2024 00:54:19 +0000

PROBLEM

While setting up On-premise orchestrator, Could not connect to the server (#101) error occurred. This error didn’t occurred with setting queues, assets, packages, libraries and etc. but with storage bucket.

CAUSE

Certificate for orchestrator was not installed.

SOLUTION

Export certification from orchestrator.
Install certificate to Trusted Root Certification Authorities.
Kill all browsers.
Reopen orchestrator.