Overview
The View is a metadata layer used by Yellowfin to hide the complexity of database structures from Report Writers. The View is used to define which columns in your database you wish to make available for Report Building. These fields may come from multiple tables and therefore will require joins to be defined (the business logic that links rows in a table together).The two major steps in creating a view include:
- Relationship Entity Diagram - selecting the tables you need from your database and defining how data in these tables are joined
- View Field Selection - defining which fields you wish to make available from these tables and providing metadata for them.
See Views for more information.
Entity Relationship
The Entity Relationship is one of the key components of the view builder. This allows you to define all the key relationships between your selected database tables.
See Model for more information.
Selecting Fields
Select fields that you wish to make available to your end users for reporting. Only columns selected from each table in your Unattached list will be available for reporting.See Table Properties for more information.
Field Categories & Meta Data
Initially, fields selected from the previous step will all be in the Unattached panel in folders that represent the tables that they originated from. These fields have not had meta data associated with them and cannot be used by your report writers. You must assign fields to folders in the Available Fields panel. The reason you do this is to organise you fields in a way that is logical for the Report Writer, giving you the chance to group them differently than the table structure in the database.
See Prepare for more information.
Field Format
The format options will provide the default for how the field will be used on the report. A user will still be able to change a format for a specific report.See Field Settings for more information.
Calculated Fields
In addition to fields from your database you can create calculated fields, pre-defined filters, and date hierarchy fields.Calculated Metric
This type of calculated field allows you to build a calculation that will return a numeric value as the result. In this example we will aim to calculate profit by subtracting cost from invoice figures.
See Calculated Fields for more information.
Date Hierarchy Fields
Date Hierarchy calculated fields allow you to build levels of a hierarchy based on a single date field in your database. This can then be used to define Drill Down hierarchies, or for other purposes in reports.
Drill Down Hierarchy
The hierarchy allows report users to drill down a dimensional hierarchy by limiting the result set as they select one level to the next. For example drill from Year (2014) to Month (August) etc.
See Drill Down Hierarchies for more information.