Handling Views During Discoverer Import

The ‘Expand Views’ option determines whether the underlying SQL definitions of database views, which form the basis of Discoverer folders, are imported into Blitz Report . When set to ‘All’, the view definition SQL is imported as a subquery within the new Blitz Report’s extraction SQL, instead of simply selecting from the view name . The primary benefit of ‘All’ expansion is simplified maintenance, as you can modify the SQL directly within the Blitz Report form, eliminating the need to recompile the view in the database whenever a change is necessary .

When set to ‘Custom’, the view definition SQLs are expanded only for views that either start with `XX%` or with any of the defined custom application short names . This setting allows you to limit the expansion to internal custom views, keeping the SQL for standard Oracle base views clean .

The ‘Include Columns’ parameter allows you to control the columns selected in the imported SQL . If you choose ‘Active’, the imported SQL will only include the columns that were actively used by the Discoverer worksheets . If you choose ‘All’, the SQL will use general folder selection syntax, such as `aia.*`, including all columns of the accessed folders .

Yes, to clean up reports imported from Discoverer, you can use the example script `mass_delete_discoverer_reports.sql` , . This script is provided specifically to remove all imported Discoverer reports before a re-import, which is useful if you need to rerun the import with different settings, such as changing the view expansion mode , .