Missing key-value for flow-step object

Hi everyone,

I have created a flowchart in my process-workflow to manage the processing based on attributes of the queue item. Now when I try to open process.xaml I am getting error message: “‘*\Process.xaml’ could not be opened. Document is invalid” (System.IO.InvalidDataException) and in the output panel: "line “212” and line “57” of “Invalid key-value for FlowStep-Object.” Line 212, Column: 57.

I found this post in forum but unfortunately without solution.

Does anyone know how to fix this or recover the process workflow?

Thanks in a advance and best regards

Nico

@nicortak

Can you check if you are passing arguments correctly?

Also check the direction as well

Hope this may help you

Thanks

1 Like

@Srini84,

I just checked with the invoke process workflow and all invoked workflows therein but unfortunately it is still not working. Do you know where to check for line 212, column 57 to find out more about the error?

Thanks

@nicortak I am getting error message: “’*\Process.xaml’ ??? May I know why did you give *\before process.xaml

Hi @ushu before \Process.xaml is just userprofile path. Actually it displays the full path C:\Users.…

@nicortak Can you try to pass the complete path of Process.xaml manually by avoiding user profile path

in some fixing scenarios we take a backup form the XAML and open the origin xaml within a text editor (e.g. notepap++) and refer to the reported line for fixings

  • is the file only complaining and opening in UiPath or not?
  • was any package version modified and the issue occurs afterwards?

Can you share the XAML and the project JSON with us?

1 Like

Hi @ppr,

process.xaml is not opening at all with document invalid error popup.
Regarding package version, I am not sure but this shouldn’t be the cause as yesterday before closing studio it still worked.

Attached the process.xaml
Process.xaml (20.0 KB)

and project.json
project.json (1.3 KB)

Reported line then apparently at

<x:Reference>__ReferenceID4<x:Key></x:Key></x:Reference>

open your xaml in a text editor (notepad++ is recommended, also take backup before)

do following changes:

then open it in UiPath again and correct the flow switch back
grafik

1 Like

It worked!
Thank you very much for your help everyone!

Also I found the root cause in Studio:

I was trying to use case “(empty)” as in screenshot, which caused the error for me (and still is when reproducing), in case someone else is facing this in the future.

image

1 Like

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