Skip to main content
Version: Omada Identity Cloud

Exporting custom contexts to ODW

Exporting custom contexts to the Omada Data Warehouse (ODW) requires configuring two data objects in the correct sequence. Completing them out of order can require manual intervention to initiate the export. For more details, go to the Export behavior section.

Required configuration steps​

Configure these two data objects, in order:

  1. Context object data object type - the data model holding your context objects.
  2. Context type data object - registers the data object type as a context and enables the export.

Context object data object type​

The context object data object type is the data model that holds your context objects, for example, Projects or Org. Units. For detailed step-by-step instructions on how to create and configure a data object type, go to Configure context type (Example).

Ensure your context object data object type includes the following:

  • Name property with ODWAttributeNames configured - required for context identification and export mapping.
  • ComposedBusinessKey property with ODWAttributeNames configured - enables the context to be properly identified and tracked in the ODW.
  • Parent property - only required if your contexts form a hierarchy, for example, nested organizational units. Flat context structures don't need one.

Context type data object​

After configuring your context object data object type, register it as a context type. For more information, go to the Context types documentation.

Navigate to Setup > Master Data > Organization... > Context types, then click New to create a new context type.

Configure the context type data object with the following settings:

  • Configured object type - specify which data object type represents this context. Select the context object data object type you created in the previous step.
  • Sync to ODW enabled - activate the export of this context type to the Data Warehouse. This is the critical setting that triggers context export to ODW.

If your context object data object type has a parent property, configure the Configured parent property setting to reference it. This is only needed for hierarchical context structures.

Export behavior​

The timing of when context objects are exported to ODW depends on the presence of existing data and the order of configuration:

  • If existing data exists: When you enable Sync to ODW for a context type that already has data in Enterprise Server, the objects will be sent to ODW immediately upon activation.

  • If no existing data: The export will begin once data is imported after all configuration steps are complete. No additional action is required.

  • If configuration order differs: If you enable Sync to ODW before completing all configuration steps, you may need to perform manual adjustments and restart the Enterprise Server timer service to trigger the export.

    tip

    To avoid this, complete all configuration steps before enabling the sync. Configure your context object data object type and context type fully before enabling Sync to ODW.

Context assignments​

How context assignments are exported depends on your configuration approach:

  • With a Context assignment data object type: If you configure a dedicated Context assignment data object type and import it, assignments are exported to ODW automatically without additional steps.
  • With a Membership property only: If you define only a Membership property in the context type, without creating a separate Context assignment data object type, context assignments are still exported automatically. The system re-exports affected identities as needed to keep assignments current in ODW.

Best practices​

To ensure a smooth and user-friendly custom context export process, follow this sequence:

  1. Define all required configuration elements first - set up the context object data object type with the name, and the ODWAttributeNames mapping, and a parent property if your contexts are hierarchical, before enabling any exports.

  2. Configure the context type data object - complete the object type and synchronization settings. Include the parent property setting, if applicable.

  3. Only then begin importing data - after all configuration is done, start the data import process.

This approach avoids manual interventions, Enterprise Server restarts, and ensures that all context objects and assignments are exported correctly on the first attempt.