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

Data Import: UBID can't be a matching field if there are multiple UBID entries for any record in the import #4775

Open
RDmitchell opened this issue Sep 5, 2024 · 1 comment
Labels
Feature Add this label to new features. This will be reflected in the change log when generated.

Comments

@RDmitchell
Copy link

RDmitchell commented Sep 5, 2024

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
image

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: ee056e6
Org: LBNL 21
File: found in the 4177 issue folder
SEED Shared Folder\Software Development\Issues\Issue 4177

@RDmitchell RDmitchell added the Feature Add this label to new features. This will be reflected in the change log when generated. label Sep 5, 2024
@RDmitchell
Copy link
Author

see also #4774

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Add this label to new features. This will be reflected in the change log when generated.
Projects
Status: No status
Development

No branches or pull requests

1 participant