03797827a4
# Description Considers the 2 Claims NewDashVersion and NewDashMoveDate as sources of truth, removing the previous (crazy) logic. If a user has the claim NewDashVersion, then it's in New Dash. The claim value will also provide the version in which the user appeared (MVP, V2, etc) If a user has the NewDashMoveDate, it means it has moved from Old Dash. If not, but still has NewDashVersion, it means the user was directly created in New Dash. The models now provide logic to handle these cases, and it's propagated downstream will ensuring reporting will still work. # Checklist - [X] The edited models and dependants run properly with production data. - [X] The edited models are sufficiently documented. - [NOT AT ALL] The edited models contain PK tests, and I've ran and passed them. **MANY ISSUES ON PRODUCTION CURRENTLY** - [X] I have checked for DRY opportunities with other models and docs. - [X] I've picked the right materialization for the affected models. # Other - [ ] Check if a full-refresh is required after this PR is merged. Changes claims and logic to consider user is in new dash. Downstream propagation included Related work items: #23457 |
||
|---|---|---|
| .. | ||
| tests | ||
| .gitkeep | ||
| business_kpis_configuration.sql | ||
| calculate_safe_relative_increment.sql | ||
| cosmos_db_utils.sql | ||
| generate_schema_name.sql | ||
| generate_stripe_sources_unioned_select.sql | ||
| is_date_before_previous_month.sql | ||
| unix_ms_timestamp_to_utc.sql | ||