Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
Report Studio: Add DataSet Dialog: What is the "Add" button for?
cmiller
When in the BIRT Report Studio, creating a new report, the Add DataSet Dialog has an "Add" button, which if clicked launches a new Pop up called "Sample ODA editor" which appears to be attached to the sample data.
What does this editor do? How can it be applied to our data sets?
I have not yet found this button or it's use in the documentation. Any help is appreciated!
Thanks,
Cole
(Images attached of Add DataSet Dialog and the Sample ODA Editor pop up)
Find more posts tagged with
Comments
averma
Hi Cole,
You can define the data set you want to use in a BIRT Template and use this template as a starting point to build adhoc reports in BIRT Report Studio. You could also expose data sets as information objects (you will require iServer for this) and uses these IO's in BIRT Report Studio. You can find more details in the following documentation:
http://www.birt-exchange.com/be/documentation/Manuals10SP1/using-birt-report-studio.pdf
Here is a link to getting started guide on wiki:
http://www.birt-exchange.org/org/wiki/index.php?title=GSG:Getting_Started_with_BIRT_Report_Studio
Ashwini
cmiller
Hi Ashwini,
Thank you for the quick response. I looked over the links you sent and I have a few more questions.
It says the ODA Editor "select the data to use in the report", does this just filter out the columns of the dataset or does it modify the query used in the data set?
I was able to drag individual columns to the report from the "Available Data" menu on the right hand side to the report area, which seems to be the same according to the documentation as what the ODA Editor does.
Do these two actions have the same result or is there a difference?
Thanks,
Cole
averma
The first approach is a customized approach to building a data set query to work with in BIRT Studio and hence query will reflect only the columns that you have selected.
The second approach is more generic approach (starting with version 11 there are some major performance improvements in the area of query optimization like limited fetching of columns, pushing down filtering and aggregation to the database layer etc.)
Ashwini