Loading

Variable names are not Case Sensitive

Data pubblicazione: Sep 26, 2024
Risoluzione

SYMPTOM

When declaring flow variables in a Mule application which have similar names (i.e. all the same characters in the same order), such as "fileName", "filename", "FILENAME" (or even "fIlEnAmE"), the value of any newly-declared variable will replace the value of the similarly-named flow variable which was declared first in the Mule application. Also, the name of that newly-declared variable will not be present as a flow variable.

CAUSE

Flow variable names declared within a Mule application are not case-sensitive and have been implemented this way since their introduction in Mule 3.

SOLUTION

The solution is to simply avoid using a new flow variable name that could be interpreted by the Mule application as an already-declared flow variable name. To determine if a new flow variable name would clash with a flow variable name that has already been declared in the Mule application, ensure that the new flow variable name, if converted to all lowercase, would not resemble the name of any flow variable name previously declared in the Mule application if it, too, were converted to all-lowercase. For example, "fileName" and "FILENAME" would be regarded as the same flow variable by the Mule application because both of these variable names would resolve to "filename" when converted to all-lowercase.
Numero articolo Knowledge

001123527

 
Caricamento
Salesforce Help | Article