this is my problem when i try to update activity package
and then if i try to go back then i have this problem to solution
how should i change versions without break any robot???
@amy93amanda Replace the activity with new activity and update the variable inside
When you upgrade to new packages few activities might be different hence you are seeing this behaviour….there is no direct way
What you can try is to make a copy of the project and then upgrade and then replace the missing activities with bew activities and you can open the old project as well to check which activities are missing and use them
Cheers
well thats an idea to make a migration but its not the ideal and less when the robot its huge
thanks
But as activities change there is no option to migrate as is…but in latest UiPath you can see which activity is missing …i believe youa re using old version so you are not aeeing the missing activity name but only a placeholder is display
Cheers
1 Like
Yes, usually when the package is updated,the activity also gets updated automatically but in your case the package cannot be updated for some reason.
@loginerror please help on this
Hi @amy93amanda
Could you please share which activity package has this issue?
Also, a few other details:
- your Studio version
- what exactly is the scenario here (please list steps you take to reproduce this issue)
- version of your activity packages
This will help us debug the issue.
-
studio version
-
the issue in the first image come from updating then click in the workflow to open it and just for open this error pops up
-
version of package over 21.10.5, this last its which i can keep.
in this case the activities with the errors were path exist, write text
Would it be possible to share a sample project that is causing this issue?
Or at least the full error message via the Copy to Clipboard option?
I developed the code in new version of UiPath studio using windows mode.but I wanted to develop the remaining code in older version.so,when I try to open the code in older version it is giving me the same error.can anyone help me?
This seems like a different issue than the one from this post.
In short - we do not guarantee that you can bring a project from a newer version to the older version and that it will always work (otherwise we wouldn’t be able to introduce new features at the risk of breaking this type of compatibility). What it means is that the older Studio / package version does not “know” about the new features that you used in the newer Studio / pacakge version.
We only guarantee it the other way around - when you go from an older to a newer version.