Hi, everyone. I thought I could fix any issue with converting from Legacy to Windows, but I’ve run into one that has me stumped.
I have a library with a workflow that works perfectly when I debug it from inside the library. It compiles and everything.
However, when I use this library as a dependency, it fails. The whole project compiles, making me believe that there are no issues, but then when the process hits that workflow, I get this error: Get FaxDetails Table: Expression Activity type ‘VisualBasicValue`1’ requires compilation in order to run. Please ensure that the workflow has been compiled.
I decided to ignore the error and see how far I could get, and I got the same error at this “Configure FaxDetails Table” workflow a bit downstream. It uses the same data table that the “Get FaxDetails Table” used. I think there is something the compiler does not like about the data table… But I’m not sure why it would work fine in my library but not here in the process.
Here are screenshots of A) the new error, and B) the properties of the workflow: A)
can also have other sources as double quote issues. For a massive ghost hunting you can do the following (take backup before). Have all XAMLs close and search with a text editor (e.g. notepad++) over all xamls for all non valid double quotes “...” or „…“ etc …
So at least this issue can be excluded from further inspections
As it is a library we would also recommend to check each Default values defined within
Thanks, @Anil_G . This will be my next step. Will keep everyone posted.
2 hours later, and my 2 workflows have been completely rebuilt from scratch. I published them, added them back as dependencies, and… TA-DA, SAME ERROR! Get your popcorn, this one’s not over yet.
Still working on this issue. I think this may be related to copying and pasting some workflows from a process that I developed in the Legacy framework over to a new process developed in the Windows framework. I was trying to save some time not having to recreate my workflows, but it looks like there are some errors related to namespaces throughout the problematic library and the process itself. Trying to figure out how to take care of these issues since deleting the namespaces with the errors, republishing, and importing into the process did not work.
This issue is most likely due to 1 or more package misalignments. Specifically, the library is using UiPath.System.Activities 22.4.5, but the process that is using that library is on 22.10.3. Furthermore, our Studio is version 22.4.
Still working on confirming that this is the issue, but it is more likely than not the cause.
Word for the wise: keep your versions aligned!
Confirmed that having the 22.10.3 version in the process interfered with the library running 22.4.5. Downgraded everything, and it’s working.
Thanks to @ppr and @Anil_G for your help along the way!