Skip to main content
OneStream Employee
April 30, 2026
Question

Dynamic Cube Views and Workspaces

  • April 30, 2026
  • 2 replies
  • 0 views

Dear community,

I was reading the documentation about cube view services, which implies that the dynamic cube views that are accessible by Dynamic Cube View Services need to be in the same workspace.

Do you know if this is mandatory to have dynamic cube views in the same workspace (as it seems a like a real issue in production) or is there a workaround to address dynamic cube views that are outside of the assembly's workspace ?

Many thanks,

2 replies

OneStream Employee
May 5, 2026

Hi Sergey​ 

I'm not sure I understand what the issue is in production?  Can you please clarify what your current challenge is?

Thanks

SergeyOneStream EmployeeAuthor
OneStream Employee
May 5, 2026

Si Sam,

Well basically, if I can only access cube views that are within the same maintenance unit, that would mean that all existing cube views that I currently have and would like to have as dynamic would have to be placed within this single maintenance unit.

In my case, I want to execute a specific rule when these cube view are accessed, so I defined them as "Is Dynamic = True" but the Dynamic Cube View service only recognize Cube Views that are within the same maintenance unit as my Dynamic Cube View service.

Regards,

OneStream Employee
May 5, 2026

Hey Sergey​ 

Thanks for clarifying.  I am still not sure why you need so many dynamic Cube Views though? 

Using Dynamic Cube Services, we can make a single physical Cube View dynamic (Is Dynamic = True) and use it like a shell that is populated by the Dynamic Cube Service result to return dynamic results, based on our logic. 

So in theory we could just use a single Cube View, for example and return any data

Existing and other new Cube Views (Is Dynamic = False) don't need to be consumed by the Service and will run as normal.  

Hope I have understood correctly and I hope this helps

Sam