Yes this is a good idea lab request. @Marcelo G. Proaño what is your use case for this metadata?

You can use vanity URLs today. Can you be more specific about which UI or gesture has the limitation? A screen shot might be helpful.

This is a useful feature. Something you can do today is to add all of the datasets which need refreshing to a sequence and they will all be reloaded. I would recommend this as an immediate solution.

One troubleshooting step can be to delete the output dataset and try re-running the data flow. Note — you will need to reapply sharing permissions on the output dataset after running it for other users to access it.

@Gina DiVenti did your admin increase the timeout value? How long is it set for?

This looks like a feature request for an application such as Fusion or NetSuite. Please open it in the product area which would implement it.

This seems like a bug. @GabriellePrichard-Oracle can you take a look?

You can create distinct subject areas which allow different reporting areas to have different data inputs. Also - publishing a new set of subject areas (or an RPD) does not cause any down time. Queries are simply routed to the updated subject areas when the publishing is completed. If you are having trouble designing this,…

The OCI audit and diagnostic logs have essentially the same information as the OAS logs. The format is a bit different. Is there some specific information you are not able to find for auditing or troubleshooting?

Do you want to control which Subject Areas users can use or which workbooks users can see and use? These are two different layers of the system.

I think this is a good suggestion for the Idea Lab:

What is the benefit you are after here. While there are few more API calls… this is essentially the same as getting it from object storage. BAR files can be large and well suited to being stored and retrieved from Object Store.

Thank you for posting the question. If the datasets you have are all facts — you will need to use blending. Don’t think of this as modeling joins. Blending desvribes relationships and the join behavior can be changed with each viz. see these docs. Note — blending is between data assets and can’t be different for different…

Per visual — you can control the overall Blending behavior. Since blending is not really the same as a join — it doesn't support pure join semantics. Understand Blending in the docs You can change the blending on each visual via the properties.

There are two features which are delivered. For a workbook — you can control the Blend behavior (all row, etc.) For a table or file with a Subject area Local Subject Area, you can create a dataset where you define an explicit join type. Between these two features, I think you can accomplish what is needed. For Blending…

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.