A few list of points that can be considered while designing reports:
1. Use database independent SQL whenever possible.
2. Use ANSI SQL join syntax (left outer, right outer) in the report design.
3. Use ANSI functions such as CASE and COALESCE instead of proprietary functions such as DECODE and ISNULL.
4. Reference all database objects in lower case.
5. The "not in" cost more than "in" in DB. So, prefer "in".
6. Include no more than 12 fields in a grouped section. One way to resolve a report with a large number of fields is through hidden fields. Hidden fields don't display in the browser, but users can choose to view the hidden fields when they download (Export data) it as a .csv file. Out of box with this option is "Asset List" (asset.rptdesign).
1. Use database independent SQL whenever possible.
2. Use ANSI SQL join syntax (left outer, right outer) in the report design.
3. Use ANSI functions such as CASE and COALESCE instead of proprietary functions such as DECODE and ISNULL.
4. Reference all database objects in lower case.
5. The "not in" cost more than "in" in DB. So, prefer "in".
6. Include no more than 12 fields in a grouped section. One way to resolve a report with a large number of fields is through hidden fields. Hidden fields don't display in the browser, but users can choose to view the hidden fields when they download (Export data) it as a .csv file. Out of box with this option is "Asset List" (asset.rptdesign).
No comments:
Post a Comment