Case sensitivity in naming Variables and Arguments

Help
1

Usually, I will use camel- and pascal-casing to name arguments and variables. I do no use hungarian notation, I try to keep my naming short and sweet.

However…

In a workflow that has an Out-argument named firstName (camel-case), I will likely use FirstName as a local variable during processing, and then use an assign activity to set firstName = FirstName, thus passing the value of my local variable back to the calling workflow through the firstName argument.

Hoooweeeeever…

Are variables and arguments case sensitive in UiPath? And if so, why does it not always recognize variable/argument names when using intellisense/autocomplete?

Thanks,

1 Like
2

No. Both are Case Insensitive in UiPath.

3

Buddy @jjes

In UiPath the variables and arguments are not case sensitive, always,
even if we try to change the camelcase to pascalcase or any other case
it will throw error even while typing
and intellisense would help us to avoid this sort of error as it would list us the variable we have defined in the scope of that activity
For more info on this

Cheers @jjes

4

Buddy @jjes
Kindly check with this, VARIABLE and ARGUMENTS are NOT CASE SENSITIVES

image
image903×395 11.4 KB

image
image865×412 11.3 KB

Cheers @jjes

1 Like
5

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