Standard Energy Efficiency Data (SEED) Platform™ is a web-based application that helps organizations easily manage data on the energy performance of large groups of buildings.
Other
107
stars
55
forks
source link
Data Import: UBID can't be a matching field if there are multiple UBID entries for any record in the import #4775
It seems like SEED should let the user know, in the first mapping step, that the file they are importing has multiple values for UBID, which they have set to a matching field, and that there can only be one UBID per record if it is a matching field.
Describe alternatives you've considered
n/a
Additional context
see issue #4177
Tested on
Instance: seeddemostaging
SHA: ee056e67e
Org: LBNL 21
File: found in the 4177 issue folder
SEED Shared Folder\Software Development\Issues\Issue 4177
RDmitchell
commented
1 week ago
Is your feature request related to a problem? Please describe.
Yes.
If UBID is set to be a matching field, and a file is imported where one or more records have more than one UBID in the UBID field,
The UI gets stuck here
and on the backend, SEED throws an error.
django.db.utils.IntegrityError: duplicate key value violates unique constraint "seed_propertyview_property_id_f8bdf6c2_uniq" web-celery DETAIL: Key (property_id, cycle_id)=(3352881, 657) already exists.
Describe the solution you'd like
It seems like SEED should let the user know, in the first mapping step, that the file they are importing has multiple values for UBID, which they have set to a matching field, and that there can only be one UBID per record if it is a matching field.
Describe alternatives you've considered
n/a
Additional context
see issue #4177
Tested on Instance: seeddemostaging SHA: ee056e67e Org: LBNL 21 File: found in the 4177 issue folder SEED Shared Folder\Software Development\Issues\Issue 4177