1) Create a class Test (see export file)
2) Create a fieldcollection Test1 (see other export file)
3) Make Sure the localizedField in the fieldcollection has maximum number of tabs set to 1 (this is important as it changes the view from
to
)
4) Create an object test. Use the locale switcher in the toolbar and switch to french
5) now go to the Detail-Data Tab and add the fieldcollection -> it seems as if the french language/locale is selected)
6) put something in the localized field of the fieldcollection example "testfr"
7) save, check the request and reload the object
Result:
testfr is saved for the en locale which is wrong. i did not check further implications like data being overridden but that might be the case.
Keep in mind this is only reproducible with "maximum number of tabs set to something lower than the amount of languages available. I think the default is 15 or something. So if the project has 15 or more languages, they suffer from this bug
Reproducible on demo
1) Create a class Test (see export file) 2) Create a fieldcollection Test1 (see other export file) 3) Make Sure the localizedField in the fieldcollection has maximum number of tabs set to 1 (this is important as it changes the view from to ) 4) Create an object test. Use the locale switcher in the toolbar and switch to french 5) now go to the Detail-Data Tab and add the fieldcollection -> it seems as if the french language/locale is selected) 6) put something in the localized field of the fieldcollection example "testfr" 7) save, check the request and reload the object
Result: testfr is saved for the en locale which is wrong. i did not check further implications like data being overridden but that might be the case. Keep in mind this is only reproducible with "maximum number of tabs set to something lower than the amount of languages available. I think the default is 15 or something. So if the project has 15 or more languages, they suffer from this bug
fieldcollection_test1_export.json class_test_export.json
@markus-moser @fashxp