When a priority habitat is moved to the potential priority habitat area you will always need to complete any missing/invalid data (e.g. determination quality) before you can then select the whole row and press the <Del> key.
The original reason for including the Legacy Habitat field in the data attributes was to retain the habitat class/type prior to the bulk translation to IHS because not all class/types used by LRCs are available in the Sources fields (e.g. HBIC used to use a pseudo-Phase1 code unique to only them). When the HLU Tool was developed the field was therefore included in the user interface, but as changes are made to the attributes the usefulness of the field is reduced because it becomes more and more out-of-date. It was not meant to be maintained to stay in line with the IHS Habitat because that is what the Sources fields are for.
There are a few options available:
1. If your Legacy Habitat class/category is based on Phase 1 (or any other class/type available in the Sources fields) then it might be better to delete all the Legacy Habitat values in the database to avoid any potential confusion.
2. Enable users to be able to collapse/hide the Legacy Habitat field so it doesn't cause confusion - the IHS Summary field would then stretch right across the whole form.
3. Allow the Legacy Habitat field to be updated
Ecologist & IT consultant
Andy Foy Consulting (ex-HBIC)