Our DRM system provides multiple Financial hierarchies to Hyperion Planning. Planning requires that all member names and aliases (i.e. descriptions) are unique across the entire Planning application - so a member called IT Costs and a member with the alias property value IT Costs could not be supported in Hyperion Planning, even if the two members existed in two separate hierarchies.
I'm working on a real-time validation that would check that all values in two properties are unique but figured I'd check here in case there's an easy solution to this. Has anyone written similar validation code, or have any tips?