Adjusted JOINS on the sourceproject for the Hydraulic Boundary Location of Grass Cover Erosion Outwards: - Do not join on the PK of the HBL entries, because these can be different between grass outwards and the hbls on assessment section level, instead join on the LocationID and the containing assessment section -- Adjusted migration logic for the outputs -- Adjusted migration logic for the HBL entries of grass cover erosion outwards --> take the HydraulicLocationEntityId as leading PK - Adjusted test files to represent the following scenarios situation: -- An HBL on the grass cover erosion failure mechanism that has a PK corresponding with a HBL that is not in the same assessment section -- Two HBLs on the grass cover erosion failure mechanism in the same assessment section that differs from the PKs of the HBLs on the assessment section
WTI-1657
