Save to Mosaic Schema Limitations

After saving the Mosaic model to the Mosaic schema, the following limitations apply:

• Missing privilege experience: To save a Mosaic schema, architect-level privileges are required. After saving a schema, the model becomes a schema object. Therefore, the original model owner may lose access and be unable to open it unless they also have the required architect privileges.

• Data calculation scope: Data calculations may be outside the original Mosaic model. Your model then requires extending data calculations to outside the Mosaic model, using more tables from the project schema when there are mapped attributes. For a dashboard with attributes only, the result depends on the project schema lookup table that contains the full set of attribute values.

• Engine behavior and calculation consistency: There may be engine calculation differences between Mosaic models as a dataset and intelligent cubes as a dataset. These differences are due to potential gaps in how the engine evaluates calculations across Mosaic models and live intelligent cubes, even when the Mosaic model has the same schema as the project schema.

  • Auto join behavior: Enabled by default in Mosaic models but is not enabled in project schema. Therefore, after conversion, the auto join behavior is disabled automatically.

  • Left outer join: Default attribute join behavior at the model level will not be used again, it will rely on attribute join behavior from the project schema.

• Functionality gaps:

  • YAML export and restore functionality and git versioning functionality is no longer available.

  • Options such as Auto Join, Attribute Join Behavior (which defaults to the data source level behavior), and Calendar (which defaults to the project-level calendar) are no longer available.

  • When there is any hyper using the in-memory Mosaic model, if the user changes it to Live model and the saves to Mosaic schema, after conversion, the hyper can not be used anymore.