Pyramid Analytics - bioXL - User options

In bioXL users have several options to personalize their work environment. These settings are kind a hidden if you don't know that they exist. I recently wrote a blog regarding changing the default values for columns & rows in bioXL. This post will highlight all user options that are available in bioXL.

Query execution

Default slicer execution: Default slicer Execution will ensure that changing any value in a slicer the report will be re-executed. This could be nice to turn off while in pure development. This option can also be toggled at the slicer properties

Default non Empty Mode: Selecting this feature will prevent that empty rows are shown in the results. This setting can also be toggled at the selections pane. 

Default selection Tree Execution: Default selection Tree Execution will ensure that changes in the selection pane will re-execute the report. 

Slicers

Default visualisation: Default slicer that will be selected when adding a value to the slices in the selection pane

Actions

Default Drill-through Rows: Default amount of rows that are returned while using actions

Report Layout

Default view: Default screen that is selected when creating a new bioXL file

Query options

Query size warnings: This feature will allow users to supress warning messages on selecting a large volume of rows. 

As mentioned I have allready explained the default query model. Navigate to this post by clicking the following link . Default value for rows & columns

Pyramid Analytics - bioXL - Default values for rows & columns

Creating bioXL files is easy. Within a few minutes you've created a new report and you can start with the next one.

I'm working with Pyramid Analytics for some time now and there is a hidden feature that's kind a handy when creating many bioXL files. In the bioXL ribbon there is a possibility to set another default query model.

First, lets navigate to the hidden feature. Create a new bioXL, navigate to the "Query" tab and click on the "User options" icon. In this menu you probably will find other options that might be useful. I will discuss these in another post



The default model will put the first dimension on rows, second dimension on columns and first measure in subsets. Consider changes this query model based on your preferences.

Available models:

Columns First dimension Rows Second dimension Subsets Measure Columns Time dimension Rows First dimension Subsets Measure Columns Time dimension Rows Measure Subsets - Columns First dimension Rows Time dimension Subsets Measure Columns Measure Rows Time dimension Subsets -

First dimension will be the first hierachy (if available) from the first dimension based on text sorting
Time dimension will be the dimension with time intelligence attached
Measure will be the first created measure in the cube
















Personally i prefer the fifth option. Measure on columns vs time on rows.