EXCLUDE_COLUMNS_DS

= optional in PARAM

When using #findata and the ledger tables contain a large amount of rows, the procedure may take a long time to execute if the selection results in many rows. To improve performance and eliminate this behaviour, the designer can tell the procedure to exclude columns that are obsolete in the query. When excluding columns, Bizview will group the results, resulting in fewer rows and enhanced performance when opening the report/form.

Access Exclude Columns in Template Design by selecting Parameters > Datastore > Populate procedure parameters.

Check the columns that should be excluded from the findata query in the specific template:

The designer can choose to select a whole dimension by marking the box to the left. If doing so, the dimension and its linked attributes and description (_descr columns) will not be included in the findata procedure.  If the dimension is needed in the template, it will automatically be added even if it is checked in the above dialog. Instead of excluding an entire dimension, the designer can choose to select only specific attributes and/or description columns.

Bizview does not evaluate anything from the template, so it's up to the designer to exclude the correct columns. The designer can get more information by running the template with trace.

Which Columns Should be Checked or Unchecked?

Objects and attributes that exist in the template area should NEVER be checked.

These are, for example:

1. Columns defined at row 1.
2. Objects and attributes in column A.
3. Objects and attributes that exists in the SEARCHVAL column.

Columns that can be checked are, for example:

1. Object and attributes that only exist in PARAM.

   • Objects and attributes that exist in PARAM can be checked. For example, if you have KONTO in PARAM, Bizview will ONLY exclude that column if there is no selection by that object (the value is blank, * or %). If there is a value, like 30*, Bizview will NOT exclude the column because it is needed to run the form/report. This particular behaviour is automatically handled by Bizview, which means that every object and attribute that ONLY exists in PARAM can be checked.

2. All other objects and attributes that do NOT exist anywhere in the template.

Note: It is up to the designer to evaluate which columns can be excluded and how that affects the report/form. Run the report/form with trace before and after excluding columns to ensure the correct result.