Orphaned Relationship CiresonHardwareAsset RelatesToOwnedByUserFactvw
I have some custom views and reporting that I have created on my data warehouse database server. I happened to be checking some data today and noticed that I have some hardware assets with a relationship to the owned by user (aka Custodian) in the CiresonHardwareAssetRelatesToOwnedByUserFactvw view that hadn't been marked with a deletedate. We ended up changing the Custodian on an asset with the problem, and it marked the custodian before our change with a delete date for the relationship. It also created a new relationship entry for that device to the new custodian. Although, we still have an original custodian to device relationship that doesn't have a delete date set.
I have created some custom SQL views with joins that use that Cireson Hardware Asset to Custodian relationship to get the current custodian, and filter the relationship data so that only relationship information without a delete date are used. Having multiple relationship entries for an asset are creating multiple entries for a single asset in my custom view. Is there a recommended way to fix this issue, or could there be something wrong with a grooming process? Would there be any issue adding a delete date to the stale entry in the CiresonHardwareAssetRelatesToOwnedByUserFactvw view?