[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward change to existing dbt-semantic-interfaces functionality, rather than a Big Idea better suited to a discussion
Describe the feature
As conversion metrics rolls out, we need validations on the parser to ensure the correct configs are passed.
Proposed Rules:
entity must exist in both the semantic models that the base_measure and conversion_measure are in
base_measure and conversion_measure must be valid and can only be SUM(1) or COUNT or DISTINCT_COUNT measures
In constant_properties, both property that is stated must be referencing either an existing dimension/entity in the respective base/conversion semantic model
Is this your first time submitting a feature request?
Describe the feature
As conversion metrics rolls out, we need validations on the parser to ensure the correct configs are passed.
Proposed Rules:
entitymust exist in both the semantic models that thebase_measureandconversion_measureare inbase_measureandconversion_measuremust be valid and can only be SUM(1) or COUNT or DISTINCT_COUNT measuresconstant_properties, both property that is stated must be referencing either an existing dimension/entity in the respective base/conversion semantic modelDescribe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response