20.08.2026
08:31
I noticed a potentially problematic behavior with the Survey → Choice List field.
The IDs of the answers (a, b, c, ...) seem to be generated automatically based on their current position in the list.
For example, the original configuration is:
a = Windows Account
b = Outlook (Mail)
c = KBS
...
h = Other
i = M365 Guest User
An existing workflow instance with Windows Account and Outlook selected is stored in the database as:
a#Windows-Account|;b#Outlook (Mail)
If I later move M365 Guest User to the second position, WEBCON automatically changes the answer IDs:
a = Windows Account
b = M365 Guest User
c = Outlook (Mail)
...
When I now open the existing workflow instance, WEBCON displays M365 Guest User as selected, although the value stored in WFD_AttChoose is still:
b#Outlook (Mail)
So it seems that the stored label (Outlook (Mail)) is ignored when rendering the field and the current meaning of ID b is used instead.
This also affects business rules/form rules.
For example, we had a rule which made an additional text field required when:
h = Other
After inserting or moving an answer above it, h refers to a different answer, while the business rule still checks for h.
This means that simply reordering or inserting answers in a Choice List can change both the displayed values of existing workflow instances and the meaning of existing business rules.
Is this the intended behavior?
If so, I think at least a warning in Designer/documentation would be important, because changing the order of answers looks like a harmless configuration change but can affect historical instances and existing process logic.
Ideally, Choice List answers would have a stable internal ID independent of their display order, similar to the ID/value concept of regular Choice fields.
Has anyone encountered this before, or is there a recommended way to safely maintain Choice Lists after they are already in production?
