Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Altinn2 convert: Individual bindings for radio buttons and checkboxes and custom values #7528

Closed
ivarne opened this issue Nov 22, 2021 · 3 comments
Assignees
Labels
kind/feature-request Feature request that will be considered.

Comments

@ivarne
Copy link
Member

ivarne commented Nov 22, 2021

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.

@ivarne ivarne added the kind/feature-request Feature request that will be considered. label Nov 22, 2021
@altinnadmin
Copy link
Member

Is this a duplicate of Altinn/app-frontend-react#114?

@ivarne
Copy link
Member Author

ivarne commented Nov 22, 2021

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.

@ivarne
Copy link
Member Author

ivarne commented Dec 19, 2021

This is a duplicate of Altinn/app-frontend-react#789.

@ivarne ivarne closed this as completed Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature-request Feature request that will be considered.
Projects
None yet
Development

No branches or pull requests

2 participants