Update from code changes: custom metrics cloned from existing metrics#1036
Open
mintlify[bot] wants to merge 1 commit into
Open
Update from code changes: custom metrics cloned from existing metrics#1036mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new Create custom metric action that clones an existing YAML metric into an editable custom metric, and notes the base-dimension requirement for dbt write-back.
Changes
guides/custom-fields.mdx: new "Creating a custom metric from an existing metric" section covering entry points (field-tree ⋯ menu and results column header), aggregate-only eligibility, what gets cloned (SQL, type, formatting, filters), default filter targeting via the base metric's underlying dimension, MIN/MAX date-formatting carry-over, and the source-metric provenance shown in edit mode.guides/developer/dbt-write-back.mdx: callout thatWrite back to dbtis hidden for custom metrics without a base dimension (cloned-from-metric customs).Context
Source PR: lightdash/lightdash#25751 — "feat: create custom metrics from existing explore metrics".