Skip to main content
Preview projects will copy all spaces/charts/dashboards into your new preview project, so you can test the content and also run validation. This is only copied on preview creation, you can’t sync the content afterwards.

​
Run lightdash preview from inside your project

or
Both commands use partial compilation by default. Field, join, and set-validation failures that can be isolated are reported as warnings while the rest of the explore remains available; failures that cannot be isolated can still fail the preview. Add --no-partial-compilation when failures normally handled by partial compilation should fail the preview instead:
To also verify supported unquoted ${TABLE}.column references with warehouse queries that return no rows, add --validate-warehouse-columns:
These flags work with both lightdash preview and lightdash start-preview. Other generic compilation warnings remain non-blocking, and --ignore-errors allows preview creation to continue after strict compilation errors. See the CLI compilation options for details. Then cmd + click to open the preview link from your terminal. Once you’re in Lightdash go to Explore —> Tables, then click on the model(s) you just updated to see your changes and play around with them.
Updating your preview while it’s runningWhile your preview is running, you can run dbt compile in a separate terminal session to update your dbt models. After compiling, refresh your browser to see the changes in Lightdash. Note that this is not a hot reload - you need to manually refresh the page.
Problems with credentials?When you create preview projects, Lightdash will use the same warehouse connection settings you have in your profiles.yml file for your current dbt project. This can be a problem if you’re using a local database that your laptop can reach but your Lightdash instance cannot.