Oracle Analytics and AI

For XSA datasets, Usage Tracking presentation_name column shows a random subject area name

Description

When using OAC usage tracking, the PRESENTATION_NAME column in the LOGICALQUERIES for queries that use datasets has a prefix on the value that appears to be just a random subject area name from the RPD.

Example:

"FIS_PAYROLL, XSA('dross@cfo.pitt.edu'.'033a5cdf-55f1-4260-9c08-bf0eb3189ba8')"

"FIS_PAYROLL, XSA('dross@cfo.pitt.edu'.'21bde7e9-b836-456e-9d28-9f383d1534e8')"

"FIS_PAYROLL, XSA('dross@cfo.pitt.edu'.'9186c958-3320-4d50-a14c-f644b539956d')"

"FIS_PAYROLL, XSA('dross@cfo.pitt.edu'.'OAC Users Clean')"

"FIS_PAYROLL, XSA('dross@cfo.pitt.edu'.'OAC Users')"

Suggestion is to remove the subject area name or use a default value like "DATASET" to identify it.

Use Case and Business Need

The dummy subject area name makes filtering the data more difficult when trying to do usage tracking reporting by subject area.

More details

Makes the usage tracking information more confusing.

Original Idea Number: e779182fe6

Find more posts tagged with

Under Review

Administration

Status: Under Review

Comments

Michal Zima

I am fighting with this for some time as well - it really complicates constructing Usage Tracking queries specific for Data Visualization. So this is highly wanted feature.

gmigotto

We also have experienced the same. A "need to be solved" issue.

Ed Balmelli

Seeing the same behavior in OAS 5.9. The random subject area appearing in the PRESENTATION_NAME column along with the XSA details make it difficult to report on which subject areas are being used.

Michal Zima

This is really very annoying "feature" and complicates very much Usage Tracking reporting on top of DV data sets (we have created our own "parsing" method for extracting real DV data sets names out of PRESENTATION_NAME column in s_nq_acct table). Could anybody from Product Development take a look at this issue and react accordingly ? Thanks very much.

Michal Zima

Any update from Product Development on this idea ?

Thanks

Alan Lee - Oracle-Oracle

The requirement is under review on how to address. In the cases the logical query contains both an SA and dataset(s), is marking to the SA name acceptable.

Subhakara Netala-Oracle

Hi @Alan Lee - Oracle-Oracle ,

Sometimes Datasets names recorded in UT along with Random subject area names which is not related to Dataset. Datasets based on Database as well behaving the same, not sure why this is happening? If SA name is acceptable then it also should be corrected to display correct SA name and apart from SAs datasets then it should recorded as only Datasets names.

Subhakara Netala-Oracle

Any update on this? Now DV usage is increased a lot, so Customers are focusing on DV Usage Tracking. Not only Dataset but also Workbook names contain additional chars apart from actual name and those are random. Please update on this.