-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Roleplay Dimension Views for dates #12
Comments
Review Fact Tables for date fields and decide on the Date Views that need to be created. For example, D_LEAD_CREATED_DATE, D_LEAD_CONVERTED_DATE |
Before we implement this fully its best we create a test based on F_CASE_MANAGEMENT dates. Create some cases and close them on different days from the create date (CASE_CREATED_TK and CASE_CLOSED_TK in the F_CASE_MANAGEMENT table). You can dummy this data after the ETL has loaded it from the source system. Then create 2 new views (and DDL) for D_CASE_CREATED_DATE and D_CASE_CLOSED_DATE. Once the views are in place run some queries using these combined views. For example, SELECT * FROM F_CASE_MANAGEMENT .... This should test if the two views that are based off D_DATE work when referenced at the same times as views |
Tested two views joined - working. |
We need to define the views we need. closed, created, modified etc etc |
We need to create the following Date Views: This List could change! D_CASE_CREATED_DATE D_LEAD_CREATED_DATE D_OPPORTUNITY_CREATED_DATE D_INVOICE_CREATED_DATE |
Needs to add views to cover the roleplay aspect of date lookups
The text was updated successfully, but these errors were encountered: