@Pravin Janardanam-Oracle is this on the roadmap?

The caps are a different topic. I would be interested to hear is specific customers are hitting the caps. The idea or saving to different outputs is useful. Object Store seems like a useful starting point. However, providing users with a database to for this also has other benefits as well!

You can do this today in Subject Areas. For datasets it is useful.

Right now a work around might be to put this in a view.

You can run a logical sql query on a dataset just like you see in the query logs. What is the requirement here you are trying to satisfy?

Taking a look. Does it work with with an uploaded file and the only issue is with a data flow output?

You can have your users add you with full control to the objects. Otherwise, the pattern is to explicitly change ownership to an admin user, make changes and set it back (if desired). This makes the overtake clear from an audit perspective.

@Rajakumar Burra is this a duplicate? If so … I we can point to that for votes.

@Cade Johnston — is this basically a list of optional columns a consumer of the table can add/remove without the author changing the report? Seems useful!

@Gianni Ceresa has great observations here. You may also consider a two-step process here. Migration to OAS 2025 first. Once that is fully migrated, then work on the transition to Semantic Modeler as a second step. This will eliminate any concern over OAS differenced verses the modeling tool. As Gianni indicates — the…

Hi @Pablo Jaquenod , welcome to the community! I am not sure if this has been evaluated before, and I am taking a look at the idea.

Do you see an"All Dashboards" option? Does that work for you here?

Welcome to the community! Have you considered using a parameter or Subject Area/RDP session variable for this? You could add a look up which set the state by user.

Is the focus here on scheduling data flows specifically? There is already a permission for creating data flows — is that an option?

Super cool! It is amazing how this shared infrastructure connects us together!

@Gianni Ceresa we are evaluating how to support it, but it is not clear when we can enable it. There are a lot scenarios for datasets which are different from how subject areas are used. We understand there are uses of session variables in datasets. Our goal is to ensure it works as intended when we enable it.

@Dhaval Parikh Stantec - do you have some additional context here? I assume you mean creating an LSA. Overall LSAs are very similar to just using an SA directly. Perhaps you can explain an example where you see a different in performance (such as adding joins, joining across sources, etc.)

Hiding to clean up the homepage is a good suggestion. The ability to control what the users can see in a dataset — should be done with role-based filters. https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/role-based-filters.html However, it may also be useful to share a dataset and not have it show up on the…

For trouble shooting… a good place to start is make a calculation for each state and list the detail. Once you feel the calc is working as expected — you can add the sum on top. So start with three calcs and put them on the same chart to see the low-level grain.

This is a useful suggestion. Could you leave this as a suggestion in the Idea Lab? https://community.oracle.com/products/oracleanalytics/categories/idealab-oracle-analytics-cloud-server