Clarity The data warehouse view ends up with no values in many of the fields including the team_key.
Article ID: 280760
Updated On:
Products
Issue/Introduction
If custom time varying attribute is used on the team page and there are values for the resource, but no actual allocations for the same time period the data warehouse view ends up with no values in many of the fields including the team_key as the view cannot join the periods
1. Create a calendared time varying attribute on the team object
- api enable it
2. Add values for this attribute on some resources (either staff module or on a specific investment)
- MAKE SURE THERE ARE NO OTHER ALLOCATION TYPES for these periods
3. Run full load of data warehouse
EXPECTED RESULT: The view DWH_INV_TEAM_PER_FACTS_M_V has all valid data including the team_key
ACTUAL RESULT: team_key along with all other fields except the custom TSV fields are null
Note: This can happen with a custom time varying attribute on any object and related facts missing if there are no other values for 'facts' except for the custom time varying attribute.
For instance, if you have a time varying attribute on the investment object and have no other records on assignments, allocations, financials, transactions, the record for the time varying attribute will be removed from the data warehouse.
Environment
Clarity 16.2.0 & 16.2.1
Resolution
This issue has been reported to our internal engineering as DE80000 and resolved in 16.2.2
Here is a list of views affected and fixed in 16.2.2
DWH_FIN_BENEFIT_PER_FACTS_F_V
DWH_FIN_PLAN_PER_FACTS_F_V
DWH_INV_ASSIGN_PER_FACTS_F_V
DWH_INV_ASSIGN_PER_FACTS_M_V
DWH_INV_ASSIGN_PER_FACTS_W_V
DWH_INV_PER_FACTS_F_V
DWH_INV_PER_FACTS_M_V
DWH_INV_PER_FACTS_W_V
DWH_INV_TASK_RU_PER_FACTS_F_V
DWH_INV_TASK_RU_PER_FACTS_M_V
DWH_INV_TASK_RU_PER_FACTS_W_V
DWH_INV_TEAM_PER_FACTS_F_V
DWH_INV_TEAM_PER_FACTS_M_V
DWH_INV_TEAM_PER_FACTS_W_V
DWH_RES_PER_FACTS_F_V
DWH_RES_PER_FACTS_M_V
DWH_RES_PER_FACTS_W_V
Additional Information
The fix will be available in Clarity 16.2.2
Feedback
