Hi. We've recently experienced some strange behaviour when importing a doc type change into our live environment.
We already had a radio button list field - with values something like:
A
B
C
None
As none of the values were selected by default, the "None" option didn't get used much - only when a user changed their mind and needed to "unset" an option, or was being extra diligent.
We've just used uSync to import some extra values into the list, so now it looks like:
A
B
C
X
Y
Z
None
We've noticed that after the uSync import, anything that was set to "None" is now set to "X" - the index position of the previous "None" option.
Does this sound like a bug? Obviously it's not desirable behaviour, but I'm not sure whether it's uSync-specific or just how Umbraco handles the fields.
uSync import additional values in Radio Button list
Hi. We've recently experienced some strange behaviour when importing a doc type change into our live environment.
We already had a radio button list field - with values something like:
As none of the values were selected by default, the "None" option didn't get used much - only when a user changed their mind and needed to "unset" an option, or was being extra diligent.
We've just used uSync to import some extra values into the list, so now it looks like:
We've noticed that after the uSync import, anything that was set to "None" is now set to "X" - the index position of the previous "None" option.
Does this sound like a bug? Obviously it's not desirable behaviour, but I'm not sure whether it's uSync-specific or just how Umbraco handles the fields.
Can anyone validate/repeat this experience?
is working on a reply...