How to force automatic dependency updates in automations?

Hi!

I have dozens of automations that use my dependency. This dependency contains screen maps and functions from our internal system, but this system frequently undergoes updates, which breaks all the automations. With the migration from legacy to Windows, I can’t invoke my library from external folders to the project, so I converted it to a dependency. But how can I force all my automations to always update to the latest version of my dependency? If a system screen changes and I update the dependency, all automations will need to run using the new version to work, as having to update the dependency project by project is totally unfeasible… Can someone help me?

PS: Preventing Windows Project from calling xaml from external folders is a huge setback in the evolution of the UiPath system…

Thank you.

You can’t, and you wouldn’t want to anyway. Updating dependencies can break things. You have to manually update, test/fix, then republish.

That being said, technically you can but it’s a bit of a hassle and considering what I said above could cause problems. Anyway, say you have published your dependency as version 1.0. What you’d do is go into Orchestrator and delete the library, then republish the new code as the same version 1.0. Then you have to go to every robot server and delete the package file that’s stored in all the robot users’ folders. This way next time the automations run they’ll see that the file is gone and re-download version 1.0 from Orchestrator.

By the way, to make that procedure simpler you can configure your robot servers so that all users store packages in a common folder on the server (instead of each user in its own folder). This way there’s just one folder on each server where you have to delete the package file.

@Marco_HVS

Check this

It will update all together

Studio - Project Dependencies Mass Update.

Cheers

Thank you all for the responses, I will analyze the options and come back to post the results.

But to detail, as I said, I need it to be done in bulk. It’s an internal system, and we have been working this way for over 3 years with total success. If our internal system undergoes any updates, I need to update the library and then place it in a shared folder. All the robots invoke the xaml from this folder, and everything works. As I mentioned, there are dozens of processes and several robots, so it is absolutely unfeasible to do this one by one, especially since the system sometimes updates more than once a week. I understand the concern about testing, and I always do it before putting the xaml correction in the shared folder, but everyone lives a different reality, and ours makes it completely impossible to work the way UiPath requires us to.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.