Create Result Views (Project)
Applies to
Platform: Microsoft SQL Server · Snowflake · Snowflake dbt · Databricks · Databricks dbt · Fabric Lakehouse · Fabric Warehouse · Oracle
Create Result Views (CreateResultViews) decides whether the generator creates a result view for each model object. Without result views, downstream model objects read the tables, and the calculations of the result views are not generated.
Available since Generator 2.2.
Values and defaults
true: every model object gets a result view.false: no result views, except for Current View, History View, Business Current View and Business History View.
The default is true, and false on Snowflake dbt and Databricks dbt. Set the value in the Implementation group of the Additional Settings in Project Settings.
Effect on generated output
With false:
- Downstream model objects and the delta views read the tables instead of the result views.
- BG_ValidToTimestamp exists only when Persist Validity is
true. With Persist Validityfalse, validation reports error ID-10064 for each historized Store Entity, Entity and satellite. - Downstream model objects that read a Data Vault table also get its unknown-member row, which the result view leaves out.
- dbt generators create no separate result models.
A change from true to false does not drop result views that are already deployed.
Example
With Create Result Views false and Persist Validity true, a Satellite on Microsoft SQL Server generates these objects:
RDV_SAT_load_customer_sat table RDV_SAT_load_customer_sat_Source view RDV_SAT_load_customer_sat_Hashing view RDV_SAT_load_customer_sat_Delta view RDV_SAT_load_customer_sat_Loader stored procedure
A query on the table also returns the unknown-member row, with a Hub_HK of zero bytes and CUSTOMER_TYPE Unknown.
Related articles
- Reference: Persist Validity (Project), BG_ValidToTimestamp
- See also: Understand the Generator target objects, Manage Project settings and Generator configuration