One Form to Rule All Languages | Community
Skip to main content
Joseph_Moran2
New Participant
October 30, 2018
Solved

One Form to Rule All Languages

  • October 30, 2018
  • 1 reply
  • 2759 views

@Sanford Whiteman​

We are working through this approach for translations, https://blog.teknkl.com/smoothing-embedded-marketo-form-loads/ . Three questions came up today that I was wondering if you could shed some light on.

​How do you manage/translate the "This field is required" message and other validation error messages?

​How do you handle the translation of drop downs, checkboxes (multi-selects)?

Related to question 2, ​is it possible for us to translate the stored values or is this method just for front end translations?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

How do you manage/translate the "This field is required" message and other validation error messages?

That's the ValidationMessage property of the field in the descriptor.

How do you handle the translation of drop downs, checkboxes (multi-selects)?

Similarly, those will be in the PicklistValues property.

Related to question 2, is it possible for us to translate the stored values or is this method just for front end translations?

You can translate just the value or the label, too. All up to you.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
October 31, 2018

How do you manage/translate the "This field is required" message and other validation error messages?

That's the ValidationMessage property of the field in the descriptor.

How do you handle the translation of drop downs, checkboxes (multi-selects)?

Similarly, those will be in the PicklistValues property.

Related to question 2, is it possible for us to translate the stored values or is this method just for front end translations?

You can translate just the value or the label, too. All up to you.