nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Add "Data Visualization Canvas Name" Column in Common - Usage Tracking Subject Area

Vivek_Gautam

Hello Team,

While exploring the "Common - Usage Tracking" Subject Area, we noticed the presence of "Classic Dashboard Name" and "Classic Dashboard Page Name" columns. However, there's no system in place to track the use of Data Visualization Canvases. It would be beneficial if a "Data Visualization Canvas Name" column could be incorporated into the "Common - Usage Tracking" Subject Area.

This column will offer significant insights to businesses aiming to discern which data visualization reports are most utilized, as data visualization provides a plethora of options for crafting reports that are engaging and informative for businesses and stakeholders.

Find more posts tagged with

Oracle Fusion Analytics

Analysis and Data Visualization

FDI

Needs Votes

setup/administration

User Experience

Status: Needs Votes

Comments

Krishna Prasad Kotti-Oracle

Can you review Logical Query Source Path column. It contains information related to Canvas and visualization Name.

Jamie Anderson-Oracle

@Vivek_Gautam09052022 , can you review Krishna's response and let us know if that satisfies what you're looking for? If not, can you expand further on why it doesn't meet your requirements?
Thanks!

Vivek_Gautam

Hi @Krishna Prasad Kotti-Oracle and @Jamie Anderson-Oracle

I apologize for the delayed response, and thank you both for your prompt replies.

The Logical Query Source Path column indeed contains data related to both DV and Classic Reports. I will experiment with a few use cases and keep you updated on the progress.

Thanks & Regards,

Vivek Gautam

Caroline Blanchard

This is a capability also needed for our team as well. @Krishna Prasad Kotti-Oracle The reason the Logical Query Source Path doesn't work is because the canvas information does not show the name of the canvas after you've renamed it, but rather canvas 1, canvas 3, etc.

As you can see here, we can only see Canvas 6, but in the actual report Canvas 6 has been renamed. Without seeing the renamed name, this information is not meaningful to report on. Additionally, I had to do a complex calculation to get to just the report name 'PI Project Tracking Dashboard' rather than the entire pathway. It would be great if we could have separate attributes in the Usage Tracking subject area that are simply Report Name and Canvas name.

Vivek_Gautam

Hi @Krishna Prasad Kotti-Oracle @Jamie Anderson-Oracle,

I agree with @Caroline Blanchard after trying multiple use cases we also came to same conclusion if we can have derived column it would be great and easy to report on.

Thanks & Regards,

Vivek Gautam

User_7W0A0

I’m genuinely surprised by Oracle’s approach here. Usage tracking data lacks key insights, such as identifying the most frequently used workbooks and monitoring individual workbook access. While this information can be retrieved through logical SQL, it’s surprising that this functionality, which was readily available for Classic dashboards, isn’t as accessible in the current version. It would be beneficial if the development team prioritized customer ease by enabling these essential analytics features directly within the system. As it stands, no wonder why users find alternative tools like Power BI more user-friendly when you do not have the basic elements for analysis.

Thanks

Sree

Linda Zheng

We've seen the same behavior in the latest version of OAS and would like to see Oracle provide a canvas name column instead of a random page number. I'm also trying to find out where the metadata for the canvas name and canvas number is stored, if anyone knows please post it here. Thanks!

Vivek_Gautam

HI @Krishna Prasad Kotti-Oracle and @Jamie Anderson-Oracle,

Could you possibly include these requests in future enchantments? The fields in question are highly beneficial for generating usage tracking reports.

Thanks & Regards,

Vivek Gautam

Novita

This is also a key requirement for our organization. Similar to @Caroline Blanchard approach, we need to perform complex calculations to extract only the relevant information (e.g., workbook and canvas name). Having separate attributes in the Usage Tracking subject area would enhance accessibility for users. Thanks!

Swetha Venkataraman

This is also a key requirement for our organization. As @Caroline Blanchard mentioned in her comment, the Logical Query Source Path doesn't show the actual name of the canvas even after renaming the canvas as per our requirements. It would be nice if we have columns in the usage tracking subject area, as Report Name and Canvas name instead of Logical Query Source Path