As the indicators will likely change multiple times, we need a graceful import of old json files.
This works already quite well: all fields that are present are imported; new fields are simply ignored, and old fields that are not present in the current scheme are ignored as well.
Please add two UI features:
(A) A model pop-up that shows a warning "Importing old data. Please check the data for correctness!" and a tabular summary of the import success: which indicators have not been imported? Which fields in the new scheme have no value yet?
(B) Highlight indicators with missing values in the form (e.g., with yellowish background).
There is a special case when filters/conditions are applied:
The old data could have a value in an unconditional field, which in the new version became the child of a filter item. As the parent filter item is initially undefined, the child with the present value is not displayed (and hidden to the user). Should we still import the value?
As the indicators will likely change multiple times, we need a graceful import of old json files. This works already quite well: all fields that are present are imported; new fields are simply ignored, and old fields that are not present in the current scheme are ignored as well.
Please add two UI features:
(A) A model pop-up that shows a warning "Importing old data. Please check the data for correctness!" and a tabular summary of the import success: which indicators have not been imported? Which fields in the new scheme have no value yet?
(B) Highlight indicators with missing values in the form (e.g., with yellowish background).
There is a special case when filters/conditions are applied: The old data could have a value in an unconditional field, which in the new version became the child of a filter item. As the parent filter item is initially undefined, the child with the present value is not displayed (and hidden to the user). Should we still import the value?