8f38e94a5c
# Description Automates the new dash query through DWH. It's a first step towards enabling a very simple PBI reporting on new dash performance. Data is aggregated at user level with the main performance indicators that we're currently reporting. I added a few more informative fields from user side. Changes: * in intermediate, creation of `int_core__new_dash_user_overview`. It mainly uses the models in previous PRs to avoid crazy computations, since most of the logic has already been implemented. The only thing is that it's "hardcoded" (with variable) the categorisation of what is NOT a paid service. * in reporting, creation of `core__new_dash_user_overview`. It just exposes the info from intermediate to reporting. * added schema entries for intermediate/core and reporting/core, it's the same description for both cases. # 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. - [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. Related work items: #19570 |
||
|---|---|---|
| .. | ||
| core__bookings.sql | ||
| core__check_in_cover_listings.sql | ||
| core__check_in_cover_users.sql | ||
| core__guest_satisfaction_responses.sql | ||
| core__host_booking_fees.sql | ||
| core__new_dash_user_overview.sql | ||
| core__unified_user.sql | ||
| core__verification_payments.sql | ||
| core__verification_requests.sql | ||
| core__vr_check_in_cover.sql | ||
| schema.yaml | ||