CoDash for Looker

LookML development, analysis and deployment

Start with the meaning.
Build reporting from there.

Bring models, views and explores into one LookML workflow. Review the definitions behind your metrics before they reach the next dashboard.

LOOKER. YOUR NEXT CHAPTER.
  1. Start withLookML models, views and explores
  2. Work with CoDashAuthor, inspect and validate
  3. Your team reviewsA reviewed project to download or deploy

The pillars, in your platform

Follow a metric from definition to delivery.

This page covers Looker and LookML. Supported migration directions are listed separately from native project development.

See how the reporting definitions connect.

Analyze with Looker
  1. You bringYour LookML project
  2. CoDash helps youInspect models, views, explores and dependencies
  3. You take forwardA project assessment

Use the available project metadata to identify complexity and the definitions that need attention.

Find where definitions can be brought together.

Rationalize with Looker
  1. You bringRelated reporting assets
  2. CoDash helps youCompare shared fields and calculation evidence
  3. You take forwardCandidates for a more focused portfolio

Owners confirm the intended meaning and reporting coverage before consolidating assets.

Make the next metric a reviewed definition.

Reporting Studio with Looker
  1. You bringA business question or existing LookML
  2. CoDash helps youRefine views, dimensions, measures and explores
  3. You take forwardLookML changes ready for validation

Continue into dashboard and Look development within the project workspace.

Take the reviewed project to your Looker instance.

Manage with Looker
  1. You bringYour updated LookML project
  2. CoDash helps youValidate references and prepare the deployment
  3. You take forwardA LookML download or deploy handoff

Download the project as a ZIP or deploy through the selected Looker connection.

Keep the metric definitions in the migration review.

Migrate with Looker
  1. You bringTableau assets or an existing LookML project
  2. CoDash helps youMap the supported source to its target
  3. You take forwardLookML or Power BI assets to validate

Supported directions are Tableau to Looker and Looker to Power BI. Each has its own conversion scope.

Your team reviews the result and decides what reaches production. For recurring work, explore Automate workflow design (preview); execution scope is confirmed per workflow.

Choose the right focus

Which part of the reporting logic needs attention?

Scroll to compare all columns

Looker: priorities, capabilities and review
Your priorityCoDash supportsYour team reviews
Define a metricLookML view, dimension and measure developmentBusiness meaning and calculation behavior
Improve explorationExplore, dashboard and Look editingRelationships, references and the questions users can answer
Deliver the projectLookML validation, download and deploymentReadiness for the chosen Looker environment

An example in practice

A revenue definition the team can review together.

An illustrative Looker scenario. Your team confirms scope and acceptance for its own reporting.

A possible Looker review journey
  1. UnderstandTrace the revenue measure through its view and explore.
  2. Work through the changeRefine the definition and the reporting that uses it.
  3. Review the resultValidate the project before downloading or deploying the change.

When a platform move is part of the plan

Supported directions involving Looker.

Source versions, accepted inputs and conversion scope vary by direction.

Connected platform journeys

See the work in its next context.

Your next step

Explore the next definition in your LookML project.

Bring a Looker reporting challenge and explore a scoped workflow with our team.

Explore Looker with us