Livecycle

Naming variables

At run time, naming conflicts occur when the names of variables are identical to those used as XML Form Object Model properties, methods, or form design field names. These conflicts can cause scripts to return unexpected values; therefore, it is important to give each variable a unique name. Here a couple of examples:

•	Use the variable name fieldWidth and fieldHeight instead of x and y.

•	Use the form design object name clientName instead of name.

Note:

Variable names are case-sensitive and should not contain spaces.

See also 

About variables

To define a text variable

To view a text variable definition

To delete a text variable

Using variables in calculations and scripts

Naming variables