Multilanguage form: default language of form and of library elements

User Support Form Building
,
1

When working with multi-language projects take care of the choice of the default language. If one project collaborator changes the default language and saves a question block in the library this question block cannot be used in the form with the original default language. For integration of question blocks the default language must be identical.

2

Hi @rumis thanks for sharing this!

I just want to make sure I’m understanding the situation correctly. Is this happening while you’re editing a form in the webform editor?

Also, I’m curious — if the question already exists in your form, in what scenario would you need to pull it again from the library?

Any additional detail on what “cannot be used” means in practice (error message, missing labels, blocked insertion, etc.) would really help us pinpoint the issue you’re describing.

Best,

3

Question: A block saved with another (changed) language into the library, this block (from the libriary) cannot be used/imported into a new form with the (different original) default language? Is this correct?

4

correct. The default language needs to be the same.

5

yes, editing in the webform editor.

It is a question block which I wanted to use in other forms as well, therefore added it to the library. I made few manoeuvres of deleting the block from the form and inserting it again. In between, I changed the default language of my form - and with this the choices menu of the inserted question block did not display the labels anymore instead it displayed blanks.

I hope this makes it clear?

BTW the real issue is the fact that the data from a repeated block do not appear in the Kobotool report neither map. But this topic is being discussed in a different thread.

6

Does it work if you temporarily change the default language of the target form to the one of the library block and import the block, and after this, you change the enhanced form to the new default language?

7

Hi @rumis, I tried to reproduce the issue on my side but couldn’t trigger the same error. If possible, could you share a screenshot of what you’re seeing? That would help us understand the behavior and replicate it more accurately.