Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      


Updated on August 16, 2022

A message is dynamic text that communicates errors, warnings, or other types of information to users. By using messages instead of static text in your user interface, you can provide contextual assistance to users that supports localization.

> Message format

Each message has a definition that contains text and references to input parameters. In the following message definition, references to input parameters are in braces. The numbers correspond to the order in which you define the input parameters on the Message form.

The {1} must be later than {2} and at least 30 days before {3}.

When you call a message, you pass a tab-delimited string that starts with the message name and provides run-time values for the input parameters. You can pass literal values or property references to a message.

The following strings are example inputs to the DateRange message above:

  • DateRange\tstart date\ttoday\tthe end date

  • "DateRange\tstartdate " + .StartDate + " \tJanuary 1, 2006\ttoday"

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us