Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Data View Fields

System Administration -> Data Services -> Setup -> Data View Fields

The purpose of a Data View is to create a list of values to be used in for example Selection Panes.

A Data View can be designed in three ways enabling most types of lists to be created.  

  • Custom list using SQL
  • Static list with fixed values
  • Object Values list

Basic Setup

At the top right of the screen select what data view you want to configure. The data view must be published to a client to be visible in the drop-down. Bizview will then execute the data view and retrieve what fields the data view will return. These fields is listed at the far left section of the screen.

You can select what fields from the data view that should be return as fields from the data view. I.e. the underlying query can contain more fields than the data view will return. Unselect the fields you do not want the data view to return. A field can in general be one of two things; a measure (number), or an attribute/dimension. Attributes can be grouped into whats called dimensions.

Select a field and configure meta-data regarding the field. In the middle of the screen, in the property area, you can:

Fields

Field 

Description

Example

Note

Dimension/measure

Choose if the field is a dimension or a measure



Display text

Descriptive text


What the end-user will see when viewing data from the data view

Dimension



If the field is an attribute, you can also group this attribute into a dimension

Aggregate function



If the field is a measure you can define the display format and the aggregate function

Click Save to save the settings.

If  you change the SQL-statement returning the data to the data view, and there are fields defined in the Data View Fields-editor, that no longer is returned by the SQL-statement, you will see a small indicator to the left of the name of the field. If you want to remove these fields from the meta-data definition you can click the Clean up button at the top left of the screen.

Hierarchies

A hierarchy is a representation of the fields that makes it easy and intuitive for the end-user to navigate down through the hierarchy structure. An example can be a structure of Product Groups -> Products, or Year -> Quarter -> Month.

The data view only returns flat data. But an analytical report can internally restructure the flat data into hierarchies. But to be able to know how the different fields are related to each other the analytical report must get meta-data about these relations. This is the objective of the far right section of the screen where one or many hierarchies can be defined.

The following example is based on a scenario with a data view returning three separate fields; Year, Quarter, and month. (And probably many more dimensions and measures).

Click the Add Hierarchy button at the top of the Hierarchies section. First give the hierarchy a name by rename New Hierarchy to something else. This text will be visible to the end-user. A good example is to describe the hierarchy levels in the name such as Year -> Quarter -> Month.

Then drag-and-drop the fields you have in the field list at the far left, into the hierarchy (white box). Start with the top-level field (ie. Year), then the next level (Quarter) etc.

You should also assign the hierarchy to a dimension. In the hierarchy definition you can select a dimension to assign the hierarchy to.

You can preview the data view structure as the end-user will see the structure in an analytical report by clicking the Preview tab at the far right of the screen.

Important: Meta-data for a data source based on an SSAS database is not possible to configure here. This should instead be configured in the SSAS database.

Additional information

Usage

The Data View(s) created can be used in the following places in Bizview

Also see the Functional Whitepaper Data Views

Published:

Data View Fields

System Administration -> Data Services -> Setup -> Data View Fields

The purpose of a Data View is to create a list of values to be used in for example Selection Panes.

A Data View can be designed in three ways enabling most types of lists to be created.  

  • Custom list using SQL
  • Static list with fixed values
  • Object Values list

Basic Setup

At the top right of the screen select what data view you want to configure. The data view must be published to a client to be visible in the drop-down. Bizview will then execute the data view and retrieve what fields the data view will return. These fields is listed at the far left section of the screen.

You can select what fields from the data view that should be return as fields from the data view. I.e. the underlying query can contain more fields than the data view will return. Unselect the fields you do not want the data view to return. A field can in general be one of two things; a measure (number), or an attribute/dimension. Attributes can be grouped into whats called dimensions.

Select a field and configure meta-data regarding the field. In the middle of the screen, in the property area, you can:

Fields

Field 

Description

Example

Note

Dimension/measure

Choose if the field is a dimension or a measure



Display text

Descriptive text


What the end-user will see when viewing data from the data view

Dimension



If the field is an attribute, you can also group this attribute into a dimension

Aggregate function



If the field is a measure you can define the display format and the aggregate function

Click Save to save the settings.

If  you change the SQL-statement returning the data to the data view, and there are fields defined in the Data View Fields-editor, that no longer is returned by the SQL-statement, you will see a small indicator to the left of the name of the field. If you want to remove these fields from the meta-data definition you can click the Clean up button at the top left of the screen.

Hierarchies

A hierarchy is a representation of the fields that makes it easy and intuitive for the end-user to navigate down through the hierarchy structure. An example can be a structure of Product Groups -> Products, or Year -> Quarter -> Month.

The data view only returns flat data. But an analytical report can internally restructure the flat data into hierarchies. But to be able to know how the different fields are related to each other the analytical report must get meta-data about these relations. This is the objective of the far right section of the screen where one or many hierarchies can be defined.

The following example is based on a scenario with a data view returning three separate fields; Year, Quarter, and month. (And probably many more dimensions and measures).

Click the Add Hierarchy button at the top of the Hierarchies section. First give the hierarchy a name by rename New Hierarchy to something else. This text will be visible to the end-user. A good example is to describe the hierarchy levels in the name such as Year -> Quarter -> Month.

Then drag-and-drop the fields you have in the field list at the far left, into the hierarchy (white box). Start with the top-level field (ie. Year), then the next level (Quarter) etc.

You should also assign the hierarchy to a dimension. In the hierarchy definition you can select a dimension to assign the hierarchy to.

You can preview the data view structure as the end-user will see the structure in an analytical report by clicking the Preview tab at the far right of the screen.

Important: Meta-data for a data source based on an SSAS database is not possible to configure here. This should instead be configured in the SSAS database.

Additional information

Usage

The Data View(s) created can be used in the following places in Bizview

Also see the Functional Whitepaper Data Views

For an optimal Community experience, Please view on Desktop
Powered by Zendesk