Data Visualization return row limit (caching) in table view

Duncan McClintock

Summary

Data source is EBS compound query, table view result does not return entire dataset. Requires user input to page through the resulting table view. User does not want that behavior.

Content

The scenario is this:

• View format is Table
• The catch is that the data source is an SQL Statement that directly hits EBS and likely several table joins.  I’m guessing that DV has some database paging feature, so the user does not have to wait for the entire query to complete in order to view the results, kind of like most SQL editors. If this is true, is there a way to turn it off? The customer wants only a complete return of the dataset and does not want to continue to paginate.

"In DV, after I have refreshed data, DV displays a few thousand records. I have to use the scroll bar and repeatedly scroll down to get all the records. Is there a trick to making DV display all records?"

 

 

Version

DV (Data Analytics 12.2.5.4)

FPonte

Hi Duncan.

Looks like the objective of this report is to export data using DV? Please correct me if I'm wrong.

If that is the case please look at this.

https://docs.oracle.com/en/cloud/paas/bi-cloud/bilug/write-visualization-data-csv-or-txt-file.html

If it is not I'm not sure what the user is trying to see with this amount of records in a table.

Please let us know what is the business use in this case. Other people may have better ideas or approach.

Cheers

Fernando