Invoke workflow file - Duplicate error - VisualBasicValue`1_1

[KevinDS (Kevin Da Silva)]

I’m having a problem with one invoke workflow file activity.

It’s giving me the next error:
Invoke Workflow File: An item with the same key has already been added. Key: VisualBasicValue`1_1

These are the argument I’m sending through the invoke:

And the values doesn’t matter. I’ve tried from the beggining of the process and from this activity execution and with values and without values is the same response.

Do you know what could be the problem?

[supermanPunch (Arpan)]

Hi @KevinDS ,

I believe the error is already recorded and a fix is provided. Check the below post on the Error fix :

Troubleshooting Guide : Conversion from Windows-Legacy project to Windows project

This topic describes troubleshooting guide regarding conversion from Windows-Legacy project to Windows project as of Dec 2022. Hope this helps those who face these problems. 1 Quick Reference by Error Messages, Situation etc. Phase Error message / Situation Reference Open project foobar.xaml: Cannot create unknown type’{clr-Namespace:UiPath.foo.Activities;assembly=UiPath.bar.Activities}ActivityName’. 2.2 Missing Activities package OR 2.3 Missing activity Development Unable to set …

We might have to edit your xaml file using a Text editor and remove the duplicated key. But before performing this, make sure you try to open and close the workflow and check again.

Also check if it only happens during Debug.

[Anil_G (Anil Gorthi)]

@KevinDS

Hope this detailed guide on what to do would help in mitigating this error

After Windows Conversion: "Unable to start execution: An item with the same key has already been added. Key: VisualBasicValue `1_1 "

SOLUTION! Took a while to dig into this, but I found that after converting a project from the Legacy framework to the Windows framework, it would not compile the Main.xaml any longer. Eventually, I found that the “VisualBasicValue1_1" key was being used for 2 different transitions. (In addition, "VisualBasicValue1_2” was also being used twice.) The new Windows framework did not like the fact that two transitions were being assigned the same key. (See below.) All I did to fix it was change one…

Cheers

[KevinDS (Kevin Da Silva)]

Thank you guys!

You were right.

I’d solved this issue opening the .xaml files in notePad++

Then I search For “VisualBasicValue`1_” in all open documents.

Then I Saw all the duplicated “VisualBasicValue’1_” (In each file I’d saw for example VisualBasicValue’1_1 and another VisualBasicValue’1_1)

so I’d replaced every duplicated just changing the last number to a next number not duplicated in the same file. (Ex: “VisualBasicValue`1_2” )

Thank you again!