Lib made in community not working with upgrade to on-prem

Help Studio
, ,
1

Hi there, we have recently moved from the free community edition of UiPath to a paid on-prem installation. Whilst we were using the free community edition we made a lot of library items inside a single library that now does not seem to work with our on-prem installation.

There seems to be a couple of things going on here:

The on-prem version does appear at first to show our library at the correct version but any updates made to the library simply don’t execute or seem to not be included in the updated library item. For example, I have tested adding a console log to the start of a library item, publishing it, updating the lib in a workflow and running that. When I run the updated workflow the new log that should come from the now updated lib item does not appear, nor do any other changes made to any part of the library… the library version number does update however.

I have tried removing the library from the workflow and then reinstalled the library which unfortunately causes every single library item (items from our own library) in the workflow to not be found and the workflow cannot be saved until all of the now missing library items are replaced.

Please, any help would be greatly appreciated. There was a lot of effort put into creating our library and it is used heavily in many workflows that we created in the community edition of UiPath.

Many thanks

2

@lewis.h,

Community edition gets updated to latest available version whereas Professional version follows long time support version (LTS)

So, with this logic your library developed on higher version will not work properly on lower version because, your on premise setup would be lower version.

To get it work, you can try to downgrade packages up to version supported by your on premise setup.

Thanks,
Ashok :slight_smile:

3

Thanks for your reply. How can I determine which version of each dependency I should downgrade to please? The package manager is telling me that I can upgrade some of the dependencies but doesn’t say I should downgrade any dependencies. I am quite confused.
I did take a look at the library package.json and noticed that it said “studioVersion: 23.6.1.0” which indeed is higher than the version we have now. I did try to manually change that to the version number that we are using now in the hope that it would tell the package manager that we needed lower versions of dependencies, but that did not work. I am struggling to figure out what versions of each dependency I need to downgrade to. Do you know how I can determine that please?

Thanks

4

@lewis.h,

Yes it’s hard to find the version which will work but try downgrade package to version which comes by default in your on premise setup.

Hope this will be helpful.

Thanks,
Ashok :slightly_smiling_face:

5

I’m so sorry but I still don’t understand how I can tell which versions of each dependency they would be. The package manager just says that there are a few dependencies that can be upgraded so that makes me think that those versions are available. If I don’t upgrade those packages I am still in the same situation, no updates to our library do anything, it’s as if they are stuck at a point in time in the past but have the latest version number. Thanks again

6

@lewis.h,

Have you tried by upgrading the packages as it advises?

7

Yes, I have tried that and everything on the surface appears fine at first, no errors. However, if I open the library and make any changes to the library, republish it and then go to the workflow that I want to use that new version in and update it the (now updated) library version number does go up by one but the changes made to the library do not happen.

How I noticed this:

We have a lib item that logs into a system. That lib item was failing to see a login form. I updated the selectors in the lib item and then republished the library. I then went to the workflow that uses it and updated the library. The library did update because the version number changed +1. The problem with UiPath being able to see the login form persisted. I went round and round several times like that trying different methods of selectors. I then wondered if the library was even updating because nothing seemed to make a difference. To check that the library was updating I put a console log right at the top of the login activity that said “I AM UPDATED”, republished it, updated the workflow to use that version of the lib and the “I AM UPDATED” log did not appear.

I really am not sure what is going on, thanks :slight_smile:

8

@lewis.h,

I know it’s frustrating to find the issue.
Could you try this last option from me, delete the library from orchestrator so there won’t be a library to update and republish it again from Studio.

Thanks,
Ashok :slight_smile:

9

I have managed to get it working as expected. I finally noticed that when publishing the version number that auto-populated into the “to” box (to version) was 1 behind what I should have expected. It must have been like that each time I updated the lib but eventually I spotted it. I was rechecking my steps to ensure that I was putting the right info onto this thread and noticed the number was 1 behind… eventually! (It’s in the 400’s so wasn’t quite as obvious as like 1, 2, 3 etc)… I manually typed in the correct number, went through all the same steps of updating the workflow to use the latest lib version and it started behaving exactly as I expected! Very strange! I can’t really explain anything else about this other than it was 1 behind when I was publishing. Still a bit confused but it’s working now. Thank you so much for your help today! I really appreciate it! :slight_smile:

1 Like
10

:smiley: Glad it worked!

Thanks,
Ashok :slight_smile:

1 Like