Skip to main content
Version: Cloud

Ownership synchronization

Synchronization in Data Warehouse

Omada Identity and the Data Warehouse are synchronized to ensure matching ownerships.

This is done in the Master data import, which is run for all imports, and can be run separately as a Synchronization import. This is done to give access to the owned objects in the Historical reports (SSRS), and KPIs based on the Tabular Model.

The Explicit owner property is used to hold authoritative ownership which has been exported from the Data Warehouse (i.e. imported from a source system). RoPE merges explicit ownership into the Effective owner properties.

Moreover, the Master data import imports ownership from the Effective Owner properties, but excludes ownership that exists in the Explicit Owner property as this information is already in Data Warehouse. The data flows are illustrated below.

Synchronization managed in Omada Identity

Data Warehouse will import the ownership because there is a value in Effective owner that is not also in Explicit owner.

info

If the Explicit owner property is updated in then RoPE will calculate a resource assignment and update the Effective owner. However, the Data Manager Groups Warehouse will not import the ownership because there is a value in Effective owner that is also in Explicit owner. Therefore, you should not implement manual or automatic processes that update the Explicit owner from within Omada Identity. Use the Manual owners property instead to achieve the same outcome.

Ownership managed in source system

Data Warehouse will import ownerships from the source system, and export them to Omada Identity's Explicit owner. This will cause RoPE to calculate an assignment and update the Effective owner.

The Data Warehouse synchronization will not import the ownership (again) because there is a value in Effective owner that is also in Explicit owner.