You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When converting from Altinn2 there is a data model incompatibility for radio buttons and checkboxes. This means that we can't use the same data models for Altinn2 and Altinn3 schemas
How do you want it solved?
Possibility to add datamodelbindings for each individual value in a list for checkboxes and radio buttons.
Possibility to set custom values for checked/unchecked (eg true/false, ja/nei)
Alternative solutions
Creating an extra temporary data model field for altinn3 and map everything manually in ProcessDataWrite. This is a manuall process, and might cause problems (require changes) when the data is processed in receiving systems.
The text was updated successfully, but these errors were encountered:
No, this is a much bigger issue about data model compatibility with altinn2, but I think the solution I have in mind would be an elegant solution to that issue as well.
When converting from Altinn2 there is a data model incompatibility for radio buttons and checkboxes. This means that we can't use the same data models for Altinn2 and Altinn3 schemas
How do you want it solved?
Possibility to add datamodelbindings for each individual value in a list for checkboxes and radio buttons.
Possibility to set custom values for checked/unchecked (eg true/false,
ja
/nei
)Alternative solutions
Creating an extra temporary data model field for altinn3 and map everything manually in
ProcessDataWrite
. This is a manuall process, and might cause problems (require changes) when the data is processed in receiving systems.The text was updated successfully, but these errors were encountered: