Remove attribute from Library/Custom Activity without replacing all activities

Hi everyone!
I made a library/custom activity to add custom logging options and I wanted to add some functionality.
I removed an attribute because it was no longer needed and all my custom activities on the project became Unresolved Activties.
Downgrading to the previous package version resolves the errors but I don’t want to leave unnecessary fields and I want to install the new and updated version.

What happens in the project:

Replacing the activity removes all the properties

Since I have 150+ activities of the same type in the project it would take me a lot to rewrite everything.
Is there a way to replace the activities maintaining all the matching and existent properties, ignoring the removed ones?

The temporary fix I found is to add them to the bottom of the list…

Hi @tommaso.perina

You have have the latest version of the packages. Go to Manage packages-> Downgrade all the packages to lowest version by keeping Runtime Rule as Lowest As Applicable and save the packages. You will find some unresolved activities. Now update the packages to the latest version and do not change Runtime Rule. You can work with the latest package versions. Lowest as Applicable ruletime takes the version whichever is suitable.

Regards

As far we have understood

  • the new version of the Custom Activity has one setting less
  • the XAML configured for the old version will result to unresolved state, when upgrading the reference package

We recommend to take a Backup from UiPath Studio Project first

  • checkout the XAML within a text editor and compar the XML Tags and attribute difference between old and new version
  • Check if the adaption can be done within a mass replace within the text editor (we got good results with notepad++)
1 Like

So, I need to install the latest version, which gives out the “Unresolved Activity” error and remove every trace of the unused attributes?

I removed every unused attribute and it resolved every activity, thank you so much!

image

image

From the snippet we would state that within the newer version an out Argument was removed.


For other researchers with similar use case some additional starter help for the analysis:

Within an isolated RnD

  • we create / inspect modelling for the old version
  • we create / inspect modelling for the new version

And compare the XAMLs

  • at the activity modelling part
  • also on other parts e.g. the top line where the namespaces for the import / references are set

With these outcomes we can check for the best strategy of the mass replace

1 Like

I did not compare the XAML files, I only removed all references to the deleted attributes without touching the code structure. Worked first try.

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