Cube Views
Hi Everyone,
In our system - Profit Center is in the Entity Dim and Cost Center is in UD1. Only specific Cost Center(s) are valid per profit center, and this mapping is stored in a SQL table in the...
Forum Discussion
JackLacava
OneStream Employee
OneStream Employee3 possible strategies:
- replicate the constraints you have in that table in actual metadata, so you can again rely on invalid intersections. However, considering you already went to the trouble of creating a custom table, I expect this might have been deemed unfeasible already.
- write Conditional Input rules that will look up the SQL table to determine if an intersection is valid or not and return the appropriate state, then suppress invalid intersections in the Cube View
- write a Custom Member List that will look up the SQL table and return valid CC members, so the Cube View will display only those. This might require some complexity in the Cube View definition though.
Yep we can't do constraints because one PC might have multiple valid CC combinations. I feel like the second strategy would help us out. Will try it out and get back to you, thank you!