Description

Story: BI-1590 - Disallow Adding New Observation Unit to Existing Environment

Added logic to check for an experiment import row with an Env that already existed and no ObsUnitId (implying that a new ObsUnit should be created for an existing Environment), and if so, throw an error that displays in the banner.
In addition, fixed file mapping for experiment import template so ObsUnitId could actually be retrieved for said logic.
Note that this change just checks for existence of values in ObsUnitId column and does not do any validation on said column.

Dependencies

bi-web/develop

Testing

• Import experiment
• Try to upload another experiment with same environment as first and ObsUnitId column missing values - error in banner should appear
• Try to upload another experiment with same environment as first and ObsUnitId with filled values - should get successfully to 'Confirm New Experiments & Observations Records' page

Checklist:

• I have performed a self-review of my own code
• I have tested my code and ensured it meets the acceptance criteria of the story
• I have tested that my code works with both the brapi-java-server and BreedBase
• I have create/modified unit tests to cover this change
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to documentation
• I have run TAF: <please include a link to TAF run>