About flexible report

Question

Hi.
I'm aware that by using lexical parameters and even a pl/sql function that returns a cursor variable, you can build very flexible reports: dynamic where clause, even dynamic select list, dynamic order by, etc. However, i'd like address some specifics issues and see if some feedback is provided:
1) I'd like to give users the abitlity to choose a summary function to apply to some columns: for example, given the amount and quantity columns, give users the option to dynamically select a summary function to be applied: i.e. sum, avg, max, min, etc. Is there a way to dynamically change a summary function?.
2) As flexible as data model can be, i find the layout model not that flexible: you have to use format triggers, anchors and so forth to get the job done. Consider these two situations:
- You allow the user to select the fields he wants in the report. On the data model size it's quite easy, if you use lexical parameters, on the layout side, you have to consider things like column size, spacing, labels, etc. These can get a bit tricky here.
- You want to give the user the ability to configure a let's say a receipt report: i mean he decides where in the paper he wants to place receipt number, customer name, code ,etc. I mean there isn't seem to exist an option such as a dynamic layout as far as i know. How flexible or dynamic a layout can be without having to write too much code?.
Any feedback will be greatly appreciated ... Thanks in advance ...!

Answer 1

1. If aggregate function is done in the SQL, the same lexical approach can be used to change the operation. If aggregation is done in the data model using summary column, you will need to create several summary columns for all possible summary functions that user can choose from. Then one more formula columns will be needed to pick one of the created summary columns based on the summary parameter value.
2.1 The layout can be flexible to some extent. It should be known in advance how many columns user can select, e.g. either 4, or 5, or 6. Then you can create different layouts for each case and switch between them, or you can even adjust the same layout using triggers, anchors, and frame elasicities, which is not too easy. For more user flexibility the Discoverer would be a better option, but you will trate flexibility for formatting and layout possibilities.
2.2 Offering the user more formatting options is also limited to what is envisaged in the layout. For example, you can ask user if he wants page numbers in the top, in the bottom, to the left, to the right, but you will have to place the page numbers in all the places and then suppress all of them except for what user has selected. For more end user freedom, XML Publisher can be the better option. The user will be able to create his own template in MS Word and move the fields as he likes.