Review the new Extract mode for LSAs. I might address your issue. The key thing to understand for this option is that it represents the data for one user — so it does not apply Subject Area security after the extract. If you use this feature, be sure the users you are sharing with have the same access as the user creating…

I think the goal here is sharing workbooks with datasets without sharing the datasets for Dataset or Analysis authoring. Is that correct?

This looks like an issue with the Assistant which I can repro. As a work around — you could rename the column in a dataset to something from say $ Amount to USD Amount … for now.

For reference, here is a walk through on connecting dashboard filters across canvases via a parameter. https://www.youtube.com/watch?v=3lSaK7mHUgc

@Wayne Van Sluys if you can create an SR for one of these examples — it is worth support helping to research what is happening. If Diagnostic logs don't show the error — there may be a gap in the logging.

What is a custom DM?

The idea makes a lot of sense. I am not sure how it is best implemented. It does seem related to save filter state.

I don't think this is feedback for OAC or OAS. What product is this for?

I don't think this is feedback for OAC or OAS. What product is this about?

@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.