Is there a reason you can't use a database source? You could export csv from OSvC Load .csv to database table Create OAC Data Set with connection to the table in the database (Live connection)

Your best bet is creating a Calendar dimension table (sheet) with the Fiscal Calendar your company uses. Then join that on the dates you currently have present.

That shouldn't be happening. From the documentation: https://docs.oracle.com/en/cloud/paas/analytics-cloud/acabi/track-usage.html#GUID-2C21BB2B-E7C8-4F2C-97D6-12F5A361A56F

The table names should be arbitrary. So long as whats in ADW matches the tables you've define in the Console/BI Server.

Your question is a tad confusing. It sounds like you are trying to set up usage tracking from a new OAC instance, but you reference a new ADW instance as well... In either case, here are a couple things to look into: * Is your connection pool in the RPD pointing to the correct ADW instance? * In your OAC console, did you…

I would have to poke around your environment. My only other suggestion is to try and parse the canvas information from the Query Text/Blob.

I typically wouldn't leverage the independent data set approach for analysis if there are concerns on data level security. If you use an RPD based approach you can implement data level security using Session Variables... Here is a great A-Team article outlining the process:…

That is unexpected behavior... It may depend on how your underlying data model is being created. Are you leveraging an RPD based approach?

There is a field that is used to define when a query error occurs. I believe the field is on the Logical Query table, identified as SUCCESS_FLG. To my knowledge a query error would result in SUCCESS_FLG = '3'. As far as identifying what Project/Canvas this error occurs on I would look to the SAW_SRC_PATH field on the…

To my knowledge there isn't a native API to check the status of a visualization. By broken I'm assuming you mean there is a Query Error. If that is the case you could build a solution leveraging the Usage Tracking features - if you're using ADW as a source you could then build an API against the Usage Tracking table to get…

If you sign into the OAC instance you should have the option to take a snapshot through the console.

If you're sourcing the dataset from a connection you'd be able to leverage the built in SQL Pivot function in the Manual Query selection step. Documentation on Oracle SQL pivoting: https://blogs.oracle.com/sql/post/how-to-convert-rows-to-columns-and-back-again-with-sql-aka-pivot-and-unpivot

That is understood. What I'm attempting to do is restore the OAC Native Data Modeling to an OAC Instance using a Snapshot of a separate OAC instance that has the OAC Native Data Modeling capabilities.

I restored the instance with a backup taken while the OAC Native Data Modeling capabilities were still available. When I view this RPD in the BI Admin tool it still has the Dummy in all 3 layers. I think the resolution is going to be creating an entirely new instance...

You might be better off setting a data filter at the RPD/Data Model Layer. However, this scenario would require a custom application for each user, which may not be tenable.

This can be accomplished by leveraging a Presentation Variable. Set the Presentation Variable then edit the title to be @{PRESENTATION_VARIABLE}, which will update whenever the Presentation Variable is set.

You may need to add columns as part of the Summation values. Additionally, OAC might not allow a summation across the columns because of the column types. It looks like you're summing ratio's which can result in unexpected values.

We are using a user define subject area as the data source - built from relational tables. The hierarchy is built out correctly - the issue is with the display in OAC DV. It is currently displaying Top-Down, whereas, we need it displayed Bottom-Up. See image for details.

I agree this entitlement based data level access would be extremely helpful from a security configuration standpoint. The current process for creating data level security is very manual and difficult to scale.