Unexpected Behavior with Invalid Intersections in EPBCS
Summary:
Invalid intersections in EPBCS work for the main hierarchy but fail to suppress rows in an alternate hierarchy, showing unexpected behavior.
Content:
We are experiencing unexpected behavior with invalid intersections in our EPBCS application. Below is a simplified version of our Entity hierarchy:
Entity Structure:
- Total_Entity (main hierarchy)
- Ent1 (Stored)
- Ent2 (Stored)
- Ent3 (Stored)
- Alt_Entity_Rollup1
- Ent1 (Shared)
- Ent2 (Shared)
- Alt_Entity_Rollup2 (Intended to be invalid for forms)
- Ent2 (Shared)
- Ent3 (Shared)
We have set up invalid intersections to prevent base members under Alt_Entity_Rollup2 from being visible. However, we observed the following behavior:
Case 1:
0