Prepare Your External Applications

Before June 1, 2026, review and update your external semantic model to meet these latest standards and make sure your external applications continue to work without interruption.

Note:

On June 1, 2026, Oracle Fusion Data Intelligence will upgrade semantic modeling to improve the platform's capabilities.

Verify your external semantic model

What you need to check and update Perform these tasks…
Hierarchy (logical dimension) based on more than one logical table
  • Ensure that the hierarchy (logical dimension) is based on only one logical table (dimension table). Semantic Modeler enforces that a hierarchy (logical dimension) is sourced from one logical table.
  • Before you migrate the model, go to Model Administration Tool, combine the logical tables, and then delete the logical table that you merged the data from.

    For example, if you have a Snowflake model that has a hierarchy (logical dimension) sourced from a dimension table and a dimension extension table, go to Model Administration Tool and add the dimension extension table data to the dimension table. After you've combined the logical tables, delete the dimension extension table.

Logical foreign key joins
  • Ensure that the semantic model doesn't contain logical foreign key joins. Logical foreign key joins don't exist in Semantic Modeler and won't be included with the migration.
  • Before you migrate the model, replace the logical foreign key joins with logical joins.
Primary keys
  • Ensure that the semantic model's logical levels contain primary keys.
Application Roles
  • Ensure that the semantic model uses application roles for object permissions and data security.

    Because the user-level security was deprecated for semantic models developed in Administration Tool, Semantic Modeler won't migrate any user-level security. In Administration Tool, you can use the Identity Manager to check that the model uses application roles and not users.
Display Folders
  • Search the semantic model to find and delete all display folders in the Physical layer and Business Model and Mapping layer.

    Display folders contain shortcuts to objects. When you delete a display folder it deletes only the shortcuts to the objects and not the objects themselves.
Consistency
  • Ensure that the semantic model passes the consistency check before migration.
  • In Model Administration Tool, run consistency check on the model and fix any errors before migration.

Verify if your external semantic model complies with the standards

To ensure uninterrupted service for your external applications, review and update your external semantic model to comply with these standards. Failure to meet these requirements might result in Oracle ignoring changes, system errors, or the deletion of non-compliant objects.

General:

  • The size of external semantic model must be less than 25 MB.
  • Catalog folder and objects names must be unique and must not conflict with prebuilt entries.

Connections:

  • The external semantic model must connect only to the Oracle Autonomous AI Lakehouse associated with Oracle Fusion Data Intelligence.
  • Don't add any additional connections to the external semantic model.
  • Before uploading, reset the prebuilt connections to their original settings. Set the data source name to "DSN" and leave the user name and password fields blank.

Joins and Lookups:

  • Logical lookups aren’t supported in the external semantic model.
  • Logical foreign key joins aren’t supported in the external semantic model.

Facts

  • Logical facts must contain at least one aggregated measure.
  • Descriptive attributes must be modeled as degenerate dimensions rather than direct fact attributes.

Dimensions

  • Every logical dimension created must be paired with an associated logical hierarchy.
  • Dimension granularity must match data. Otherwise, query results will be inaccurate.
  • The primary key of the lowest or detail level of a dimensional hierarchy must match the primary key of the logical dimension table that the hierarchy is based on.

Hierarchies

  • A hierarchy (logical dimension) must be derived from one and only one logical table (dimension table).
  • The parent-child hierarchies defined in external semantic model can't be used for subsequent modeling within the Branch or Sandbox frameworks. Use level-based hierarchies instead.
  • Level-based hierarchies require a defined grand total level and a detail level. Set the number of elements at each level to one or more.
  • Logical foreign key joins will be deprecated. Delete the logical foreign key joins and replace them with logical joins.
  • All logical levels must have a primary key defined.
  • Optimize hierarchy performance by limiting available attributes to essential fields.

Columns

  • Data types of the conforming columns must match.
  • Limit your derived column expressions to 1499 characters to ensure they remain valid.

Security

  • User-level security will be deprecated. Update the external semantic model to exclusively use application roles for all object and data security permissions.
  • You must provide a display name and description for all custom roles created within the external semantic model.
  • If the external semantic model references application roles and groups, then you must create them manually. The merge capability imports only the mappings and doesn't import the roles and groups definitions. Create the applicable groups in your identity provider. Create application roles using the Security page in Oracle Fusion Data Intelligence.
  • Use application roles to secure object access and not to manage data security.

Data Augmentations

  • Don't enable the SME Options for Data Augmentation under the Generally Available Features tab on the Enable Features page unless you have already created data augmentation types such as Create Dimension, Create Fact, and Extend Entity. These augmentation types are no longer recommended and might be removed in a future release. SME Options for Data Augmentation directly updates the semantic model, which can trigger errors due to synchronization failures. If you encounter these errors, replace the SME augmentation with a Dataset type augmentation and configure user-defined semantic model extensions instead.

System Variables

  • Don't reference system variables in your external application extensions. System variables are allowed in the Sandbox framework.

Bundle Deployment

  • You must ensure that the functional areas enabled in the target environment and the development environment from where the template semantic model was extracted are the same to avoid failure of the external application merge.