Oracle Design Guidelines – Queries Design (Part 2)

As discussed in the previous post, the correct filtering of data according to user queries is an essential feature of any dashboard. While it may seem straightforward in concept, there are a number of issues to consider when setting up filtering. The Oracle Design Guidelines provide some very specific and helpful information on how to correctly set up filtering. By following this guide, you can set up effective filtering and help avoid layout and charting problems in your reports.

In order to create an efficient report it is very important to eliminate unnecessary columns. In terms of SQL statements, ┬áit is important to validate any physical statements that are created as a result of a request. You should also validate that the functional values of the SQL statements match their structures. To have a look at the physical SQL statements from a report that was just run, go to Setting, Administration and then Manage Sessions. There will then be a list of log sessions which will include the last report. Select View Log URL and then look for “Sending query to database named…” Check each of these queries to ensure that they follow the appropriate procedures as explained above.

It may happen that you obtain the response, “No Log Found”. This means that your user level is not set high enough. In order to view logs it must be at a minimum of level 2. Further information and instructions can be found here.