Oracle Analytics Cloud and Server Idea Lab

Home› Oracle Analytics› Oracle Analytics Idea Labs› Oracle Analytics Cloud and Server Idea Lab

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Possibility of utilizing a single Data Set that should be reusable across multiple projects

Needs Votes
31
Views
1
Comments
Dorel Olea-Oracle
Dorel Olea-Oracle Rank 1 - Community Starter
in Oracle Analytics Cloud and Server Idea Lab

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of): Wyndham City Council

Description (Required): Problem Description

When a Data Set is connected to a Subject Area and saved to a Project and another project is created and uses the same data set, the join in the first project is being removed.

Steps to reproduce:

1. Create a Data Set.

2. Create a Project and connect the Data Set to a Subject Area (e.g. Asset - Activity) via Prepare tab > Data Diagram. Save the Project.

3. Create another Project and connect the same Data Set to a Subject Area (e.g. Asset - Work Order) via Prepare tab > Data Diagram. Save the Project.

4. In the first Project, go to the Prepare tab and Data Diagram. The connection is removed from the Data Set and Subject Area.

Use Case and Business Need (Required):

The issue is about utilizing a single Data Set that should be reusable across multiple projects. It seems counterproductive to the flexibility/reusability of the objects in OUAV to have to create two separate instances of a Data Set that have the exact same structure and content for every project that needs to use the data within.

Enhancement Request / Service Request:

SR 3-27732761204: (GCS Collaboration) (Closed) Data Set joins removed when used in multiple Projects

Bug 33297074 - OAS 5.9 : DELETING A JOIN ON PROJECTS WHICH SHARE THAT JOIN CAUSE ISSUES


Tagged:
6
Up
6 votes

Needs Votes · Last Updated

Comments

  • Nina Asenbauer
    Nina Asenbauer Rank 4 - Community Specialist

    There is also no way to "persist" calculations except doing so in a data flow or subject area. Not exactly the same, but issue adjacent I think. Apart from the subject area and the multi table dataset (which only can be populated from a database if I recall correctly), there is no way to really "persist" and reuse already prepared data (ie. with joins, calculations etc.). Or is there something I have overlooked? Maybe all this will be covered with the new semantic modeller?