|
| Re: Adhoc Reporting in Open Source BIRT [message #725027 is a reply to message #724824] |
Tue, 13 September 2011 18:18   |
|
Actuate's interactive viewer does items 1-6 in addition to adding charts
etc. It is not open source though, but will work with reports created
in open source.
Jason
On 9/13/2011 5:57 AM, sam wrote:
> Hi All
>
> Here is my requirement.
>
> I have a finite list of columns (say 30). Here are the steps the user
> might perform
>
> 1) Clicks a link. 2) App shows all the 30 columns and all the rows (page
> wise)
> 3) User can remove and later add columns to the results
> 4) User can apply filters
> 5) User can select a column to sort
> 6) User can select a column to group
>
> req's 5/6 can be done later. But 1-4 are must.
> I am looking at birt to help me achieve this.
>
> I am thinking to do this. Once the user clicks on the main link, show
> all the data (page wise). At this point generate the rptDocument. And
> then, apply filters / add / remove columns over the rptDocument. My
> question is can we query over an existing rptDocument. Or add / remvoe
> columns in rptDocument.
>
> Pl note that I am going to use an appserver and use RE API.
>
> Is my thinking in the right direction. Pl let me know if there are any
> other options available.
>
> Thanks
>
|
|
|
|
| Re: Adhoc Reporting in Open Source BIRT [message #725139 is a reply to message #725124] |
Wed, 14 September 2011 04:46 |
|
Sam,
I have several example that apply filters and sorting using client side
script that re-run the reports. Would these be useful?
Jason
On 9/13/2011 11:08 PM, sam wrote:
> Thanks Jason for the reply.
> I understand Actuate Interactive Viewer has those features. I would like
> to know if we can achieve using ONLY open source. Thats our current
> requirement. I just need a direction.
>
> Thanks
|
|
|
|
|
|
| Re: Adhoc Reporting in Open Source BIRT [message #726113 is a reply to message #725744] |
Fri, 16 September 2011 15:38 |
|
I am not certain. I have not tried this approach before.
Jason
On 9/15/2011 12:28 PM, vavesw wrote:
> Thank you for your examples.
>
> I am thinking of the following approach. Our database is huge and
> regenerating the report from database may not be feasible.
>
> The first time when the user clicks on the main screen, all the database
> rows (accessible by that user) will be shown with all the columns (30).
> We will generate this by Run + Render task. This will generate an
> rptdocument.
>
> All the subsequent searches / filters / sorts / grouping will be in a
> new report, for which the backend will be the rptdocument created first.
> We will use scripted dataset for this and the filters / sorts / groups
> will be added dynamically to the table.
>
> I have tested a basic flow with this and seems like it works.
>
> Would there be any challenges in this approach with large amounts of data?
>
> Thanks
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03388 seconds
] 
Search
Help
Register
Login
Home
