Preview Feature: Create Mosaic Schema

Starting in Strategy (July 2026), you can use a preview feature to create Mosaic schema in Mosaic Studio to use auto modeling to create Mosaic schema objects.

Use schemas as a logical and physical definition of warehouse data elements, physical characteristics, and relationships, derived from the logical data model. The Mosaic schema refers to an internal map that Strategy uses to keep track of attribute relationships, fact levels, table sizes, and so on within a project.

Preview features are early versions of features and are not to be used in a production environment as the core behavior remain subject to change between preview and GA. By selecting to expose preview features, you can access these features and use them as you would any other functionality. This preview is for experimentation and feedback.

Prerequisites

To create a Mosaic schema, you must have the Architect privilege.

Enable the Feature

To enable the feature flag from the Library server:

  1. Open configOverrides.properties.

    configOverrides.properties may be in the following file path: /usr/local/tomcat/webapps/0/WEB-INF/classes/config.

  2. Add the following setting: features.save-to-mosaic-schema=true.

  3. Restart the Library server.

Recommendations

To try this preview feature, Strategy recommends:

  • Create a new project specifically for Mosaic schema testing.

  • Avoid using the feature on existing or production projects.

  • Use only test or non-critical data.

Create a Mosaic Schema

  1. Open Strategy Library.

  2. Choose Create New > Mosaic Model.

  3. Choose a Project.

  4. Click OK.

  5. Choose an existing source from the Sources grid or click Add Database.

    For more information on adding data from a database, see Import Data from a Database.

    Databases are the only supported source for Mosaic schema and external models are not supported.

  6. Expand the Query Mode drop-down list in the top-right of the window and choose Live.

  7. Click Proceed.

  8. Map your Mosaic model to the Mosaic schema.

  9. Click Hierarchy in the top left and view your mapped objects.

  10. Create and edit attributes, as needed.

    You can not edit attributes or attribute forms that are mapped to the Mosaic schema.

  11. Expand the drop-down list next to Save and choose Save To Mosaic Schema.

  12. If your schema includes unmapped objects (for example, attributes, metrics, and advanced metrics), they will be converted to standalone objects in the Mosaic schema. Review the objects and click OK.

    • All security filters created in the model will be removed. You can create project-level security filters.

  13. Expand the drop-down list next to Save and choose Save and Update Schema to confirm the final schema update process.

    If you do not click Save and Update Schema, saved objects can not be consumed in the project.

  14. After you click Save to Mosaic Schema and Save and Update Schema, you will lock the current schema at the project level. If the schema is already locked, you may receive an error. In that case, follow the steps below to unlock the schema:

    1. In Workstation, click Schema in the Navigation pane.

    2. Right-click your project and click Unlock Schema.

Save a Mosaic Model to Mosaic Schema

You can also convert an existing Mosaic model to a Mosaic schema.

After saving, the Mosaic model is converted to a Mosaic schema. This action can not be undone.

  1. Edit an existing Mosaic model with the following requirements:

    • The model must use Live query mode.

    • The model must not have Mosaic model links.

    • The model must not be referenced by other Mosaic models from Mosaic model links.

  2. Expand the drop-down list next to Save and choose Save To Mosaic Schema.

  3. If your schema includes unmapped objects (for example, attributes, metrics, and advanced metrics), they will be converted to standalone objects in the Mosaic schema. Review the objects and click OK.

  4. Expand the drop-down list next to Save and choose Save and Update Schema to confirm the final schema update process.

    If you do not click Save and Update Schema, saved objects can not be consumed in the project.

Merge Attributes in a Mosaic Schema

  1. Edit a Mosaic schema and click Model in the top-left.

  2. Click the Tables tab and click Merge Attributes in the top-right.

  3. Expand the Mosaic Object drop-down list and choose an object in the current Mosaic schema.

  4. Expand the Mosaic Schema drop-down list and choose the attribute you want to merge with.

  5. Click Apply.

  6. Expand the drop-down list next to Save and choose Save and Update Schema to confirm the final schema update process.

    The mapped attribute merges to the existing attribute in the schema.

View Merge Attributes in Workstation

  1. Open Workstation.

  2. In the Navigation pane, click Objects and locate the attribute.

  3. Right-click the attribute and choose Edit.

  4. At the bottom of the attribute editor, click the Mosaic Models tab and view the merged attribute.

Known Limitations for Save to Mosaic Schema in the Strategy (July 2026) Preview

  • Object migration in Mosaic schema is not supported.

  • If the Mosaic model applies a table-level filter directly to a physical table, the filter is removed after in-place conversion. Because the Mosaic schema no longer enforces the filter, the dataset exposed to the dashboard changes, potentially altering dashboard results.

  • If you save a Mosaic model to a Mosaic schema, security filters defined directly on the model are removed. Security must then be enforced via standalone security filter objects on the schema, which may expose data.

  • Dashboards, reports, and intelligent cubes support Mosaic schemas. Agents and MCP do not support Mosaic schemas.

Engine Limitations

Mosaic model saved to schema has known limitations for SQL correctness, backward compatibility, time-based analytics, and model lifecycle management that users should be aware of before adopting.

Join Resolution

In certain configurations, the engine may fail to establish the correct join paths between tables, which results in incorrect query results (cross joins):

  • Using count-distinct aggregations on extension attributes combined with time dimensions can trigger incorrect join behavior with the calendar table.

  • Setting a metric guide after converting a model to an extension may produce unexpected cross-join behavior.

Backward Compatibility with Existing Dashboards

Dashboards created before a model is promoted to a schema may encounter errors:

  • Some dashboards may display misleading metadata errors that suggest data corruption.

  • Dashboards that use hierarchy or lookup table resolution may fail with internal engine errors.

  • Applying derived attribute filters on pre-existing dashboards can produce "fact does not exist at a level" erros.

Time and Period-Based Metrics

Time transformation functions do not fully resolve within models saved to schema:

  • PreviousPeriod metrics may fail with fact resolution errors.

  • Average metrics combined with Set qualifications may resolve to null instead of computing correctly.

Derived Attribute Performance

After in-place conversion to a Mosaic model saved to schema, derived attribute pushdown may no longer occur at the SQL layer. Instead, evaluation falls back to the Analytical Engine, which can significantly degrade query performance for complex expressions.

Developer Workflow Compatibility

Base metrics that originate from a Mosaic model saved to schema are not currently visible in the Developer Object Browser, limiting their use in Developer-based reporting workflows.

Model Lifecycle

  • Saving a model as a schema is irreversible: Once a model is promoted to a Mosaic model saved to schema, it cannot be detached or deleted from the schema.

  • Schema refresh is required: Using promoted objects before updating the project schema produces a generic error without actionable guidance. Users must update the project schema before referencing new extension objects.

Recommendations

  • Do not promote models that back existing production dashboards without first validating those dashboards in a test environment.

  • Avoid combining time-based metrics (PreviousPeriod, period-to-date) with Mosaic model saved to schema attribute until these limitations are resolved.

  • Treat model saving to schema as a one-way operation - ensure the model design is finalized before converting.

  • After saving a model to schema, always update the project schema before building new visualizations against extension objects.

These limitations are expected to be addressed in upcoming releases.