@Christian Berg Would that fake dimension be setup within EPM or OAC? We've started seeing this issue on an EPM connection in OAC that had been working without issue up to now.

@GabriellePrichard-Oracle would something like that be possible now? If so, I'd love to hear more about how to implement that. Making sure our security is right is currently our biggest hurdle to delivering more DV based reports.

This would be a great addition to OAC. Having those objects having to be overwritten leads us to do some development in our production environment entirely to avoid that happening. The other option we sometime use is to export a workbook from Classic as a .catalog file as that does seem to work as well. But, if you have…

@Avinash Krishnaram-Oracle While the parameter feature does mostly allow default values in filters, it is still a very messy solution that is not easily implemented. Having to use a logical SQL statement instead of just selecting a server variable name is sometimes difficult. Additionally, even when creating these default…

Agreed, while parameters can work as a column selector, some kind of view selector functionality would greatly enhance our ability to move away from Classic as it's a commonly used feature in our Classic analysis.

Yes, we have run into this problem as well. Our OAC developers create a dataset in our development environment and the when the DVA is exported then imported by a different user the project breaks because the name of namespace of the dataset has changed. This has forced us to change our process and give people admin access…