I have a picklist in Salesforce with english values.
I want to have a translation to frensh and the idea is to use this field in smart list.
Thanks for your feedback the idea is not to use them in forms but to use them in smart list as filters or trigger and the business want to have values on frensh language because they don't speak english.
You can't compare a stored French value with a stored English value in a Smart List and have them match* (there's no "master value" that they could both be linked to for comparison) -- if that's what you mean. You'd have to translate one of the values to the implicit primary language, then compare them.
* Except for those words that match under collations that ignore accented characters, of course.
Sanford thank you,
No the idea is that this field I have it in english in salesforce, so when I sync it with Marketo business they see only english values, we want to show them in marketo, frensh values instead of english.
is it clear for you?
So then you want exactly what Dan Stevens listed above. Forms 2.0 with different values for the display than the stored value.
I think the situation is that SFDC people already have values for these fields. So HM wants to have the values be different on both side. The only way this could work is if a data management campaign mapped the Eng. values to French values on-the-fly.
Yes exactly Sanford, this is the needs, is to have those values in frensh for our frensh users in Marketo, to allow them to pick frensh value when they build their smart campaign.
So how I can do this campaign to manage that? I don't understand how it's possible through campaign program?
You could have a Smart Campaign, triggered on Data Value Changes, that sets the value of another field (don't use the same field) to the French version.
This would require an Add Choice condition for each possible English value.
So the complexity depends on how many values you're trying to maintain. If it were over, say, 20 values I would probably call a webhook instead and have that do the translation. It's the same idea though: you're storing the French version in another field. And you want that field to be read-only for the Marketo users who build the SCs (otherwise you'll get caught in a loop of updating the French, then the English, then the French...).