98c40d21d2
# Description I noticed this morning that after the name changes some exclusions have been messed up. I think is about time we handle this properly. Following what we did for `ytd_mtd_aggregated_main_metrics_overview`, I apply the same logic: the metric display configuration is handled for each metric in the configuration rather than by some crazy-complex-name-logic. I also took the opportunity to make Host Resolutions timely after a discussion with Chloe yesterday. Finance handles resolutions payments twice a week, and the "delay" in time is mostly coming from Resolutions accepting to pay someone vs. Finance handling the payment. In any case we're talking about a few days maximum difference, which I believe it's 1) process-related freshness, rather than data-related and 2) much better to have visibility in a timely manner rather than waiting for the 20th on next month. # Checklist - [X] The edited models and dependants run properly with production data. - [X] The edited models are sufficiently documented. - [X] The edited models contain PK tests, and I've ran and passed them. - [ ] I have checked for DRY opportunities with other models and docs. **Logic is common among YTD and MTD models. At some moment this can be improved** - [X] I've picked the right materialization for the affected models. # Other - [ ] Check if a full-refresh is required after this PR is merged. Related work items: #28560 |
||
|---|---|---|
| .. | ||
| daily_currency_exchange_rates.sql | ||
| dates.sql | ||
| deals_consolidation.sql | ||
| edeposit_and_athena_verifications.sql | ||
| monthly_aggregated_metrics_history_by_deal.sql | ||
| monthly_aggregated_metrics_history_by_deal_by_time_window.sql | ||
| monthly_growth_score_by_deal.sql | ||
| mtd_aggregated_metrics.sql | ||
| new_dash_booking_summary.sql | ||
| schema.yml | ||
| simple_exchange_rates.sql | ||
| ytd_mtd_aggregated_main_metrics_overview.sql | ||