I got the requirement to design a multilingual form the other day.
Thanks toVadim Tabakman for describing a good way to realize such a form.
Since my customer is thinking about translating the whole SharePoint-Plattform, Oceanik came into discussion.
Unfortunately, I haven't found any discussion about Nintex Forms and Oceanik in combination yet so I decided to share my learnings here. To learn about the capabilities of Oceanik, please visit their website here: OCEANIK for SharePoint 2010, 2013 and 2016 - Oceanik
First, I installed Oceanik on my test environment and activated it on a plain SiteCollection. For this test, I translate terms from Englisch to German.
To check whether the solution is working or not, I put "Go-Live" on my homepage. Now I can switch between the two languages and see the result.
So far so good.
As you can see in the left navigation, I also created a list called "Expenses" and translated that to "Spesen".
Now for my next test, I use the term "expenses" in a label control on my Nintex Form and publish it.
Sadly, Oceanik doesn't seem to be able to translate terms inside a Nintex Form, I thought...
Do you want to see something really odd?
When I use "expenses" as an option inside a choice-control, the translation works:
Oceanik isn't fully supported by Nintex Forms. Under some circumstances, terms are getting translated. Enterprises who face the difficulty of translating their whole SharePoint still need a workaround for Nintex Forms.
Please feel free to comment your experience or guide me if I missed a setting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.