Evaluating Variables

I suggest you to add a panel in which We can watch and evaluate the variables value . It will make us easier finding errors

1 Like

If you use logging correctly in your processes this is not required. However, I have raised with UiPath the possibility of automatically logging any variables that are created at Trace level. Personally I think a separate panel would be overkill.

@badita what do you think?

Do you mean at runtime?

Because there is something like that in Debug Mode.


hey @Lucky0906

as @Cosin said: [quote=“Cosin, post:3, topic:1755”]
in Debug Mode.

you can see this thing :slight_smile: for debugging purpose you will need this thing.

In debug mode you can see the above things [quote=“Lucky0906, post:1, topic:1755”]
can watch and evaluate the variables value



Hi askh1yadav,
How to I get to the Name and Value to watch a variable.

Go To Locals tab (bottom of your screenshot)

We’ll extend this for datatables, collections, dictionaries.


Having a watch window would be a great idea, just like in Visual Studio we can then figure out the exact value to be placed in the code.

1 Like

If you can do a Locals Windows (like in Excel - vbe) where we can see all the values of an arrays, a dictionary, attributes of an objetc etc. it would be a GREAT plus for UiStudio, thanks in advance. :slight_smile:

i need to extract only three columns form my excel sheet of 10 columns.
can anyone help me doing this.
Thanks in advance

Hi @Lucky0906

Latest versions have all the goodies - Locals panel, Watch panel, Immediate panel :slight_smile:

Hi all,

I guess there is no way to verify variables while debugging in UiPath Studio, unless we use the “write line” activity. In my opinion, it would be better if it had something like “Immediate window” in Visual Studio, where you can stop the execution of the program and execute methods over the existing variables in execution time. For example, let’s assume we had created a robot to read an excel file and store the result in a variable called dataResult; we could debug the robot and just try some codes (dataResult(0)(1) <- to get the second column of the first row of the data result) to navigate into the dataResult variable without the need to include lots of write line activities.

Hope you consider this idea!

Best regards,

Bruno Costa.


This would be great, although I’m not sure how doable baring in mind that in WorkflowFoundation all variables are stored in contexts.

There is a debug preview window though - when in Debug mode, open the Preferences panel, it’s there at the bottom (but only for primitive types).