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 a user uploads an XML file manually, it holds onto upload file for tracking purposes in this table, which is behaving as expected.
But, with these duplicate files, it also created duplicate records in the “Scenarios & Measures” table with identical information and identical dates in each drop-down menu.
This is a pathway that should be improved on the SEED side by enabling better data management by the user (e.g., ability to delete files loaded in error or duplicate files)
When a user uploads an XML file manually, it holds onto upload file for tracking purposes in this table, which is behaving as expected.
But, with these duplicate files, it also created duplicate records in the “Scenarios & Measures” table with identical information and identical dates in each drop-down menu.
This is a pathway that should be improved on the SEED side by enabling better data management by the user (e.g., ability to delete files loaded in error or duplicate files)
From SEED-AT Demo Workflow presentation, slide 26: https://docs.google.com/presentation/d/1FPE74-Qx3s3-zaY8hPIaR8pFEp8lzKPh/edit?pli=1#slide=id.g2f2e6095736_1_0
The text was updated successfully, but these errors were encountered: