Skip to content

Data: Is Omitted is not working if the omitted fields have already been used in another import -- that Is Omitted data IS imported #5084

Open

Description

@RDmitchell

Instance: production
SHA: b264666
Org: LBNL 5333

It does appear that the "Is Omitted" functionality is NOT working if the fields that are omitted in one import have already been mapped from another import.

This doc has more details

Activity

  1. added theissue type on Sep 12, 2025
  2. self-assigned this
    on Sep 12, 2025
  3. changed the title [-]Data: Omitted fields for geoJSON files -- exploring use cases[/-] [+]Data: Is Omitted is not working if the omitted fields have already been used in another import -- that Is Omitted data IS imported[/+] on Sep 12, 2025
  4. changed the issue type fromtoon Sep 12, 2025
  5. removed
    To InvestigateThese issues are newer that need to be investigated or confirmed.
    on Sep 12, 2025
  6. RDmitchell commented on Sep 12, 2025

    @RDmitchell
    Author

    folder for this issue, with sample files used in these tests
    https://drive.google.com/drive/folders/1_6Bu1-Jc3dTfBtY6t5M-DdaCVE_GvRq_?usp=drive_link

  7. removed their assignment
    on Sep 12, 2025
  8. moved this to Ready for Testing on Dev/Stage in FY25on Sep 29, 2025
  9. RDmitchell commented on Sep 29, 2025

    @RDmitchell
    Author

    Instance: dev1
    SHA:

    I think this is fixed, but my testing is a bit limited at this point.

    I think it would be good to test again when this is moved to staging and the production db is also moved to staging.

    Then I can do more complete testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    • Status
      Ready for Testing on Dev/Stage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions