For the Core.AllocationAmounts_fact table, we need to support the idea that a single water right can have multiple owners / owner types. Right now, our OwnerClassificationCV field only accepts a 1-1 relationship and will not support this. We are having to truncate the list of owners down to 1 in the event a single water right has multiple owners.
This is not an issue for the AllocationOwner field. Just the OwnerClassificationCV field with it's relation towards the CVs.OwnerClassification table.
For the Core.AllocationAmounts_fact table, we need to support the idea that a single water right can have multiple owners / owner types. Right now, our OwnerClassificationCV field only accepts a 1-1 relationship and will not support this. We are having to truncate the list of owners down to 1 in the event a single water right has multiple owners.
This is not an issue for the AllocationOwner field. Just the OwnerClassificationCV field with it's relation towards the CVs.OwnerClassification table.