I agree - not all users are fans of those "wannabe funny" messages, rather provide the ability to customize message, which will appear during page loading (this can be leverage to provide some admin messages, informing user community about some important facts).

Similar topic has been discussed in Idea : https://cloudcustomerconnect.oracle.com/posts/a28f798a09 . We are also using "automatic" addition to "login" parameters (&NQUser + &NQPassword) into URL for our current "publicly" exposed OBIEE dashboards (using OBIEE 12c - see for…

Hi Mike, just out of curiosity - when can we approximately expect, that this API will be made available in both OAC/OAS products ? Thanks and regards Michal

Hi Mike, just a short question - can similar approach (as described in blog "Oracle Analytics Cloud (OAC) Embedding— Public User Access — Part 1") be taken to expose DV content publicly using OAS (thus on-premise sw) ? Thanks and kind regards Michal 

I completely agree - users should be restricted on DV Home page to see only objects (Subject Areas, data sets etc...), they are entitled to see, based on their privileges (assignments to application roles), they should not see all objects. I consider this behavior as a Bug , which should be fixed very soon.

To compete with self-service BI tool "pioneers" (Tableau,Power BI...) and offer similar capabilities, this feature is definitelly a "must" - and it pays for DV projects but as well for good old Dashboards/Analysis as well.

Hi, BIPLATFORM schema is one of the "supporting" schema, leveraged by OAS instance. For OAS, creation of those supporting DB schemas is part of the installation procedure. For OAC I guess, those schemas are created automatically (somewhere...) during provisioning of OAC instance. But you your questions (in respect of OAC)…

Hi Marcelo, actually OAS (and I assume OAC as well) is internally storing BI catalog object definitions in tables in BIPLATFORM schema (as opposed to OBIEE 12c, where BI catalog was physically directory structure on server filesystem) - those tables are following (this is result of my internal exploration, so no official…

Very smart idea - DV should have the same concept as GoURL for Answers/Dashboards, alloowing me to construct URL for displaying particular canvas of DV project and passing filtering conditions for that canvas.

Should be part of standard API for DV objects - which is still missing (I mean the API) - at least for on-premise Oracle Analytics Server.

This feature will put DV on the similar level in respect of functionality/features as the "good old" Answers/Dashboards tools from OBIEE.

Definitely wanted feature. If I remember correctly from Oracle Analytics roadmap presentation held by Garry Rubin at OA Summit, he was mentioning, that here will be quite substential changes in modeling data sets for DV , but I am not sure, whether this feature is also part of those plans.

Our end users would be grateful for this feature, this is missing since OBIEE times.

Hi Nikunj, you only need one Init Block (one SQL query) to retrieve all "strings" for presentation layer object names for display. I dont think that retrieval of 1000 + column names would be a problem... Rgds Michal

We used for this purpose (for on-premise OBIEE, but I guess, it should work) concept of externalization of names/decriptions of objects in presentation layer (see: https://docs.oracle.com/en/middleware/bi/analytics-server/metadata-oas/use-administration-tool-utilities.html#GUID-3F2BD5A3-2C8A-4F28-9379-7FCF32A748BE).…

Official (published and documented) Oracle Analytics Server API is definitelly a must requirement. Not only for running DF, but also for manipulating DV Data Sets - like for example: * creating DS * re-uploading file DS * purging BI Server cache entries, connected with particular DS * changing definition of DS etc...

One addition to this requirement - capability of building/designing hierachies should be available in data set definition. And this hierarchy should be exposed (in DV projects visualization) in similar way as hierarchical columns in Answers.

This is another idea, dealing with the same requirement, which has been already posted - proofing, that this is really highly desirable feature - organizing data sets in a more structured way (not just in dummy way) is critical.

Generally structuring objects into BI catalog folders should be a "golden rule" for majority of DV objects (not only for DV projects as it is now, but also for data sets, data flows, possibly Connection objects is not that critical). This would definitelly help to better organize/maintain DV object and also security aspect…

Definitelly highly wanted feature. This limitation (for OAS, but for OAC I guess same is valid) is described in ORA Support document: "OAS: Export DV Project As Dashboard Object Error Out "Currently Not Supported " (Doc ID 2681662.1)".