This doesn't work on 365 ?

http://www.sharepointpub.com/nintex-forms-multi-language-form

There is no 'lookup' in the form runtime functions on Nintex 365 forms...

Oh yes...

Maybe you could use panels that will show/hide accordind to language choice.

Less dynamic than lookups but....

...which defeats the purpose of having the translated texts outside the form, in SharePoint, where regional staff can access and update them as required.

Using panels would add to size and load time, and any slight change needs to have the form updated.

This is Nintex Forms 365 - no versioning here.. Relying on preview or publish and hope .. Or export old versions just in case ... All reasons to cut down unnecessary editing if the form in 365 Nintex.

Hi! Have you solved that issue? Can you share your solution with us?

Regards,

Tomasz

Yes, Tomasz. The functionality to enable this became available last July.

I did not get to use it for languages, but here is how I have used it - looking up approval managers for a specific Change Scope.

Here are the steps needed to lookup the data from one row of a list. And can be used for languages as well as names.

1. Source list for data - in my case manager names. Here Title Column will hold the Scope value we will be using to filter on.

2. Lookup column needs to be created on the main list -> this is looking at the title of the Scopes List

3. Add List Lookup Control on to your Nintex 365 form:

4. Add Calculated Value control on the form to pull in the lookup list data, and save it to your local list:

I have a lot of stuff surrounding the lookup, to make the output more presentable, but the heart of it is the lookup function:

(lookup("Scopes-List","ID",ChangeScope,"Operations-Assignee")

...which is using the Change Scope control value to filter the Scopes-List, and pulls the value from the Operations-Assignee column into the Calculated Value. This value is saved locally in teh Ops-Assignee column of the main list.

I hope this is helpful.

lookup("Scopes-List","ID",ChangeScope,"Operations-Assignee") is correct here - I left in a leading bracket... that is not needed

Thank you very much for your input. I'm sure it will help many

Regards,

Tomasz