LookML view · dating-platform

The proposition_templates view: date idea templates with a fallback name rule

At a glance

Does: Reads proposition templates: category, location, featured and official flags, created, expires and deleted dates, and a display name. One measure: count.Trust: Source-defined
Why: A catalogue of date ideas that users can propose. The enterprise model explores it as date_ideas, joined to the propositions made from each template.Trust: Inferred
Breaks: 3 warnings. Top: Template counts fan out in date_ideas
Grain: One row per template. id is the primary key.Trust: Source-defined
Source: dating_platform/proposal_templates.view.lookml 120 lines

Source: proposal_templates.view.lookml L1-10

dating_platform/proposal_templates.view.lookmlL1-10 Show context

1- view: proposition_templates2  sql_table_name: ${TABLE}.proposition_templates3  fields:4  - dimension: id5    primary_key: true6    type: int7    sql: ${TABLE}.id8  - dimension: category9    sql: ${TABLE}.category10  - dimension_group: created11    type: time12    timeframes:13    - time

dating-platform, proposal_templates.view.lookml, lines 1-10

Shape

Source-defined

Every field as declared, with the dashboard tiles that read it. Computed from the source; nothing here is edited.

Table: ${TABLE}.proposition_templates

Dimensions 25

Name	Type	SQL	Used by	Tags
`id`L4	int	`${TABLE}.id`	-	primary key
`category`L8	string	`${TABLE}.category`	-
`created`time, date, week, monthL10	time group	`${TABLE}.created_at`	-
`date`date, week, monthL18	time group	`${TABLE}.date`	-	hidden
`deleted`date, week, monthL26	time group	`${TABLE}.deleted_at`	-
`expires`date, week, monthL33	time group	`${TABLE}.expires_on`	-
`featured`L40	yesno	`${TABLE}.featured`	-	name reused
`featured`time, date, week, monthL43	time group	`${TABLE}.featured_at`	-	name reused
`global`L51	yesno	`${TABLE}.global`	-
`lat`L54	number	`${TABLE}.lat`	-	hidden
`lng`L58	number	`${TABLE}.lng`	-	hidden
`location`L62	string	`${TABLE}.location`	-
`market_id`L64	int	`${TABLE}.market_id`	-	hidden
`meta_description`L68	string	`${TABLE}.meta_description`	-	hidden
`meta_keywords`L71	string	`${TABLE}.meta_keywords`	-	hidden
`meta_title`L74	string	`${TABLE}.meta_title`	-	hidden
`name`L77	string	`COALESCE(${TABLE}.name, INITCAP(REPLACE(${TABLE}.slug...` `COALESCE(${TABLE}.name, INITCAP(REPLACE(${TABLE}.slug, '-', ' ')))`	-	derived
`official`L80	yesno	`${TABLE}.official`	-
`proposition_id`L83	int	`${TABLE}.proposition_id`	-	hidden
`slug`L87	string	`${TABLE}.slug`	-	hidden
`time`L90	string	`${TABLE}.time`	-
`updated`time, date, week, monthL92	time group	`${TABLE}.updated_at`	-	hidden
`url`L101	string	`${TABLE}.url`	-
`user_id`L103	int	`${TABLE}.user_id`	-	hidden
`venue_id`L107	int	`${TABLE}.venue_id`	-	hidden

Measures 1

Name	Type	SQL	Used by	Tags
`count`L111	count	`COUNT(*) of rows`	-

Relationships

Source-defined

No joins, no upstream views and no dashboard tiles reference this view. It is an island in the model.

Relationships of proposition_templates

This Block

Text version

proposition_templates is the base view of date_ideas: base view

Worth noticing

Names fall back to the slug

Source-defined

name uses name when present, otherwise it turns slug into title case, so wine-tasting reads Wine Tasting.

Source: proposal_templates.view.lookml L77-79

dating_platform/proposal_templates.view.lookmlL77-79 Show context

74  - dimension: meta_title75    hidden: true76    sql: ${TABLE}.meta_title77  - dimension: name78    type: string79    sql: COALESCE(${TABLE}.name, INITCAP(REPLACE(${TABLE}.slug, '-', ' ')))80  - dimension: official81    type: yesno82    sql: ${TABLE}.official

dating-platform, proposal_templates.view.lookml, lines 77-79

Explored under another name

Source-defined

The enterprise model exposes this view as the date_ideas explore and joins propositions on proposition_template_id.

Source: enterprise.model.lookml L49-54

dating_platform/enterprise.model.lookmlL49-54 Show context

46  - join: messages47    sql_on: messages.proposition_id = propositions.id48    fields: []49- explore: date_ideas50  view: date_ideas51  from: proposition_templates52  joins:53  - join: propositions54    sql_on: propositions.proposition_template_id = date_ideas.id55- explore: tests56  view: user_metrics57  label: Test Metrics

dating-platform, enterprise.model.lookml, lines 49-54

What can change the answer 3

Caution: Template counts fan out in date_ideas

Inferred

date_ideas joins propositions with no relationship, so Looker assumes many_to_one. One template has many propositions, so template rows repeat and are not deduplicated.

What goes wrong: Template count turns into a proposition count as soon as a propositions field is selected.

Read the guide: Join fanout

Source: enterprise.model.lookml L49-54

dating_platform/enterprise.model.lookmlL49-54 Show context

46  - join: messages47    sql_on: messages.proposition_id = propositions.id48    fields: []49- explore: date_ideas50  view: date_ideas51  from: proposition_templates52  joins:53  - join: propositions54    sql_on: propositions.proposition_template_id = date_ideas.id55- explore: tests56  view: user_metrics57  label: Test Metrics

dating-platform, enterprise.model.lookml, lines 49-54

Caution: featured is both a yes/no and a time group

Source-defined

featured is a yes/no dimension over featured, and featured is also declared as a dimension_group over featured_at.

What goes wrong: References to featured can land on the flag or on the timeframes, so filters may not mean what the author intended.

Source: proposal_templates.view.lookml L40-50

dating_platform/proposal_templates.view.lookmlL40-50 Show context

37    - week38    - month39    sql: ${TABLE}.expires_on40  - dimension: featured41    type: yesno42    sql: ${TABLE}.featured43  - dimension_group: featured44    type: time45    timeframes:46    - time47    - date48    - week49    - month50    sql: ${TABLE}.featured_at51  - dimension: global52    type: yesno53    sql: ${TABLE}.global

dating-platform, proposal_templates.view.lookml, lines 40-50

Note: Table name built on the TABLE placeholder

Inferred

sql_table_name: ${TABLE}.proposition_templates uses ${TABLE} inside its own definition, as the messages view does.

Source: proposal_templates.view.lookml L1-3

dating_platform/proposal_templates.view.lookmlL1-3 Show context

1- view: proposition_templates2  sql_table_name: ${TABLE}.proposition_templates3  fields:4  - dimension: id5    primary_key: true6    type: int

dating-platform, proposal_templates.view.lookml, lines 1-3

Parser checks 1

Source-defined

Mechanical findings from parsing the LookML. They are facts about the files. The cards above explain which ones matter.

Show all 1 check

name-collision 1
- proposal_templates.view.lookml:43 proposition_templates.featured is declared as both dimension and dimension_group.

At a glance

Shape

Dimensions 25

Measures 1

Relationships

Worth noticing

Names fall back to the slug

Explored under another name

What can change the answer 3

Caution: Template counts fan out in date_ideas

Caution: featured is both a yes/no and a time group

Note: Table name built on the TABLE placeholder

Parser checks 1

Related

Guides built on this file

Related source files

Source model