Interesting Bug with Valid Intersections in Multiple Databases
Thought I'd pass along some info on a bug I discovered. We have two databases where some members in the hierarchy are only valid in one of the databases. If Valid Intersections reference that member (so data can be entered in forms to that database), than it breaks the other DB (makes all intersections). Instead you must put IAncestors of the member to Allow data entry in both the DB that has the member and the DB that doesn't have the member.
Just passing along the info in case anyone else hits the problem and needs a solution. The work around is easy enough that I didn't think an SR was worth the effort