Forum Discussion
SimonHesford
9 days agoContributor
Could you clarify what you mean by viable intersection. Do you mean that it is not picked up by the in-built validation checks that OneStream performs? If so you are talking about some form of custom validation or sorting out your metadata and security constraints so it does stop users loading data where they shouldn't. The first option may involve quite a bit of work depending on the amount of custom business logic you would need to maintain to identify what you deem as incorrect intersections.
If intersections are viable then then they should be able to accept input and managing data that needs to be restated is more of a process exercise, as trying to find a technical solution is counter intuitive to your data model design.
Related Content
- 2 years ago
- 2 years ago
- 2 years ago
- 9 months ago