Skip to content

docs(dbt_orders): clarify partner analysis context in metric descriptions - #104

Open
lightdash[bot] wants to merge 1 commit into
mainfrom
lightdash-ai-writeback/1605b656-88e1-4e47-86f4-947b57f843af
Open

lightdash[bot] wants to merge 1 commit into
mainfrom
lightdash-ai-writeback/1605b656-88e1-4e47-86f4-947b57f843af

Conversation

@lightdash

@lightdash lightdash Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Updated descriptions for 7 metrics in dbt_orders.yml to clarify how each metric behaves when grouped by Partner
  • No changes to metric names, labels, SQL, or types — documentation only
  • Affected metrics: count_distinct_order_id, count_of_order_id, sum_of_basket_total, average_of_basket_total, sum_of_profit, avg_profit, sum_of_partner_commission

Changes

Each description now follows the pattern: what the metric measures overall, then an explicit note on what it shows when grouped by the Partner dimension. This makes partner-level analysis self-documenting in the Lightdash metric catalogue.

Test plan

  • Lightdash compile: SUCCESS (exit 0, 5/5 explores)
  • Verify updated descriptions appear in the Lightdash metric picker for the Orders explore
  • Confirm no regressions on existing metric behaviour (names, types, SQL unchanged)

…ions

## Summary

- Updated descriptions for 7 metrics in `dbt_orders.yml` to clarify how each metric behaves when grouped by Partner
- No changes to metric names, labels, SQL, or types — documentation only
- Affected metrics: `count_distinct_order_id`, `count_of_order_id`, `sum_of_basket_total`, `average_of_basket_total`, `sum_of_profit`, `avg_profit`, `sum_of_partner_commission`

## Changes

Each description now follows the pattern: what the metric measures overall, then an explicit note on what it shows when grouped by the Partner dimension. This makes partner-level analysis self-documenting in the Lightdash metric catalogue.

## Test plan

- [ ] Lightdash compile: SUCCESS (exit 0, 5/5 explores)
- [ ] Verify updated descriptions appear in the Lightdash metric picker for the Orders explore
- [ ] Confirm no regressions on existing metric behaviour (names, types, SQL unchanged)

Co-authored-by: lightdash[bot] <183517231+lightdash[bot]@users.noreply.github.com>
Co-authored-by: Josh Elston-Green <josh@lightdash.com>
@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

Lightdash Validation Results

Validating default project 8a223608-a1e4-426e-adcd-0598ea72b9f8

/opt/hostedtoolcache/Python/3.10.20/x64/lib/python3.10/site-packages/google/api_core/_python_version_support.py:255: FutureWarning: You are using a Python version (3.10.20) which Google will stop supporting in new releases of google.api_core once it reaches its end of life (2026-10-04). Please upgrade to the latest Python version, or at least Python 3.11, to continue receiving updates for google.api_core past that date.
  warnings.warn(message, FutureWarning)
/opt/hostedtoolcache/Python/3.10.20/x64/lib/python3.10/site-packages/google/api_core/_python_version_support.py:255: FutureWarning: You are using a Python version (3.10.20) which Google will stop supporting in new releases of google.cloud.dataproc_v1 once it reaches its end of life (2026-10-04). Please upgrade to the latest Python version, or at least Python 3.11, to continue receiving updates for google.cloud.dataproc_v1 past that date.
  warnings.warn(message, FutureWarning)

- SUCCESS> dbt_support_requests 
- SUCCESS> dbt_orders 
- SUCCESS> dbt_orders_no_preagg 
- SUCCESS> dbt_baskets 
- SUCCESS> dbt_users 

Compiled 5 explores, SUCCESS=5 ERRORS=0
-   Waiting for validation to finish
✖   Validation finished in 18s with 6 errors


- Tables: 0 errors
- Charts: 4 errors
- Dashboards: 2 errors


NAME                                                         LAST UPDATED BY   LAST UPDATED AT ERROR                                                                           
How do order volume and order values trend over time?        Jess Hitchcock      2026-05-13    Metric error: the field 'dbt_orders_median_revenue_per_order' no longer exists  
Partner Sales by Month - Last 12 Months                      Rohan Bedi          2026-06-11    Metric error: the field 'monthly_partner_info_total_sales' no longer exists     
with tc sql What is the median revenue per order by partner? João Viana          2026-04-30    Metric error: the field 'dbt_orders_median_revenue_per_order' no longer exists  
XLSX Export Test Table                                       Giorgi Bagdavadze   2026-06-09    Metric error: the field 'dbt_orders_median_revenue_per_order' no longer exists  
Sales Updates                                                Rohan Bedi          2026-06-10    The chart 'Partner Sales by Month - Last 12 Months' is broken on this dashboard.
XLSX Export Test Dashboard                                   Giorgi Bagdavadze   2026-06-09    The chart 'XLSX Export Test Table' is broken on this dashboard.                 

--> To see these errors in Lightdash, run lightdash preview

Note: 6 chart configuration warnings hidden. Use --show-chart-configuration-warnings to show.

This validation check is informational and does not block merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants