Skip to main content
Users can model and query in the workbook model layer and leave all the content they create isolated to that workbook. If users want to make the changes in that workbook reusable and accessible to other users, the changes need to be promoted to the Shared Model. This action pushes the workbook model changes to the model layer and new workbooks will include the changes that were pushed.

​
Promotion

​
Branch Mode

More structured than [document drafts](/content/develop but less complex than the git integration, Branch Mode allows you to test changes to models and content before making them visible to your teammates. By creating a separate space to experiment with updates, you can develop confidently without disrupting production data. This approach supports scalable and reliable workflows, reducing the need for reactive fixes while improving traceability and accountability in the development process. Refer to the [Using Branch Mode for collaboration guide](/content/develop/branch-mode for more information.

​
Validating models against content

The Content Validator, accessible by clicking the (checked document icon) in the IDE’s left navigation, helps you keep your content accurate and up-to-date as your data model evolves. If a field is renamed, a table is swapped, or a topic is removed, the validator makes it easy to spot where things broke and quickly fix them - either one by one or in bulk. Additionally, the Content Validator is a powerful discovery tool: you can search for all the content that references a specific field, view, or topic to see how widely it’s used before making changes. This way, you can make updates with confidence and ensure nothing slips through the cracks. Refer to the Content Validator guide for more information.

​
Editing models

​
Incorporating database changes with schema refreshes

​
Export to dbt

We want to make model management easy both in Omni and below the BI layer. To this end, we offer the ability to export a view file’s dbt SQL. This will allow users to build fact tables, or virtualized fields into their dbt models beneath Omni. Currently this will require some rework of your Omni model, because new dbt views will then be populated into the model upon schema refresh. This means field references would need to be remapped to maintain continuity. In the future the intent is for this promotion to become button-click.