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.
- Start withLookML models, views and explores
- Work with CoDashAuthor, inspect and validate
- 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.
- You bringYour LookML project
- CoDash helps youInspect models, views, explores and dependencies
- 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.
- You bringRelated reporting assets
- CoDash helps youCompare shared fields and calculation evidence
- 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.
- You bringA business question or existing LookML
- CoDash helps youRefine views, dimensions, measures and explores
- 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.
- You bringYour updated LookML project
- CoDash helps youValidate references and prepare the deployment
- 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.
- You bringTableau assets or an existing LookML project
- CoDash helps youMap the supported source to its target
- 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
| Your priority | CoDash supports | Your team reviews |
|---|---|---|
| Define a metric | LookML view, dimension and measure development | Business meaning and calculation behavior |
| Improve exploration | Explore, dashboard and Look editing | Relationships, references and the questions users can answer |
| Deliver the project | LookML validation, download and deployment | Readiness 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.
- UnderstandTrace the revenue measure through its view and explore.
- Work through the changeRefine the definition and the reporting that uses it.
- 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.