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

to display all rows in resultset while creating dataset in VA

User_I1VY7

Organization Name

Vodafone

Description

Hi Team,

We are getting very limited number of rows (probably just 100) in resultset out of actual result which has more than 5000 rows if we connect to Oracle database and save a dataset.

Since only limited number of rows are being displayed instead of actual result, business teams are not able to apply necessary filters (e.g. Group By) on columns to have exactly required data in dataset.

Use Case and Business Need

Please refer to Oracle support case we have already raised where the issue and requirement was discussed in detail:

SR 3-26031461801 : only 100 rows are being displayed in transform editor while creating dataset in OAS 5.5.0 DV

More details

Please refer to Oracle support case we have already raised where the issue and requirement was discussed in detail:

SR 3-26031461801 : only 100 rows are being displayed in transform editor while creating dataset in OAS 5.5.0 DV

Original Idea Number: 4c51f047fa

Find more posts tagged with

Under Review

Data Connectivity

Data Modelling and Datasets

Analysis and Data Visualization

Data Preparation and Flows

Status: Under Review

Comments

Luis E. Rivas -Oracle

Hi Sumit,

Dataset creation has been improved in the current versions of OAC/OAS - although only 100 rows are displayed in the Data Preview, the underlying random sample is 5000 rows. There is also a way to add filters on each of the tables that make up a dataset. There is one known limitation in the Grouping function if the number of distinct values for a particular column is greater than 100 - we have an enhancement request in the works to resolve this issue - if you are running into this issue, the workaround for it is to bypass the grouping dialog and create a decode statement in the formula editor.

Also, are you still on OAS 5.5 or have you upgraded to OAS 5.9?

User_I1VY7

Hi Luis,

Thanks for going through my request and suggesting workaround.

We are using OAS 5.9.0

Could you please elaborate more on how following can be achieved?

"workaround for it is to bypass the grouping dialog and create a decode statement in the formula editor. "

Many thanks again!

Sumit.