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
Description:
Given the new possibilities with participant-import:
It is worth discussing if the preview should only the data from the file, or whether it should show preexisting data.
Somethings which needs discussion:
how to handle data from the file which is new
how to handle data from the file which is old
how to handle the preview if the file is empty (at this place) but the data field is filled in the backend
how to handle the preview if the file is filled (at this place) but the data field is ALSO filled in the backend
What shoud be discussed/happen:
The preview should include all existing user data
The text was updated successfully, but these errors were encountered:
The second wanted behaviour (The preview should include all existing user data) is not implementable without a new concept.
So far this was actively not the desired behaviour, because the preview should only show data which was from the imported file.
After some internal discussions that part will become it's own Issue or clarifying actions will be updated here.
I also took out the project labels as I understood them to be applicable to the bug part of what was initially asked.
If that is wrong @Elblinator@MSoeb please add them back
Elblinator
changed the title
Membership number: user import by referencing data didn't work
Import rework Preview
May 31, 2024
Description:
Given the new possibilities with participant-import:
It is worth discussing if the preview should only the data from the file, or whether it should show preexisting data.
Somethings which needs discussion:
What shoud be discussed/happen:
The text was updated successfully, but these errors were encountered: