Skip to main content

Managing views in the Viewmaker

Elena Damiani
  • Updated
The Viewmaker allows you to generate and manage multiple views of a project for export and downstream use. Recent enhancements introduce more control over how views are handled, enabling you to decide which views are exported and how views are named, without affecting the internal structure of the project.
These capabilities help you tailor Viewmaker output to specific use cases while keeping all generated views available inside the project.

 

What you can do with view management

With the updated Viewmaker capabilities, you can:
  • Include or exclude individual views from the exported output
  • Rename views using custom aliases for clarity and presentation
  • Maintain all views internally, regardless of export settings
  • Regenerate views when the project changes, ensuring consistency with the latest data

 

Including or excluding views from export

How view inclusion works

Each view listed in the Viewmaker panel is associated with an eye button:
  • Selected: the view is included in the exported Viewmaker output
  • Unselected: the view is excluded from the exported output

 

Note! By default, all views are included.
Changes are applied immediately in the user interface.
 
 

What inclusion and exclusion affect

  • Inclusion or exclusion applies only to exported output (for example, data sent to downstream tools).
  • Views are not removed from the project.
  • All views remain available internally, even if excluded from export.
This design ensures that you can control output without losing access to any generated view.

 

Renaming views using aliases

What aliases are

An alias is a custom name assigned to a view for presentation and export purposes. Aliases do not replace the system-generated view identifiers.

How to rename a view

  1. In the Viewmaker list, select the Edit name action next to a view.
  2. Enter a custom name.
  3. Confirm the change.

 

Once confirmed:
  • The alias is displayed in the Viewmaker panel.
  • The alias is included in the exported Viewmaker data.

 

What happens when you regenerate views

When you select Regenerate Views, Viewmaker rebuilds the entire view list to reflect the latest project state.
As part of this process:
  • All inclusion and exclusion selections are reset
  • All view aliases are removed
  • System-generated view names are restored
After regeneration, you must manually:
  • Re-select which views to include or exclude
  • Reapply any custom aliases
This behavior ensures regenerated views are always fully aligned with the current project configuration.

 

How these settings affect exported output

View inclusion and aliases influence only the exported Viewmaker output:
  • Views marked as excluded are omitted from export
  • Aliases are included for views that are exported
  • All views remain stored internally within the project, regardless of inclusion state
 
For technical details about how these settings are represented in configuration files, see Viewmaker export and configuration settings.

 

Best practices

  • Apply inclusion and alias changes after your project structure is stable.
     
  • Avoid regenerating views unless the project model has changed.
     
  • Use aliases to make exported views immediately understandable for downstream users or tools.
     
  • Recheck inclusion settings after regeneration, as all manual selections are cleared.

 

Version requirements

These capabilities require:
  • Core version: 4.46.1 or higher
  • Backend version: February 11th, 2026 build (or later)

Related articles