Skip to main content

Process Metadata Changes

The Process Metadata Changes activity triggers the Una metadata processing job, which applies pending structural changes to the model (dimension member additions, renames, hierarchy changes) and waits for it to complete.

Purpose​

Use the Process Metadata Changes activity to:

  • Apply dimension member changes synced from an ERP or Salesforce integration before running calculations
  • Rebuild the model structure after a bulk import of new members
  • Ensure the model is structurally consistent before downstream data loads or report generation

Configuration​

This activity has no configurable fields. It always runs the full metadata processing job.

Behavior​

  1. The metadata processing job is started asynchronously.
  2. The activity polls for job status using incremental wait intervals.
  3. Status transitions and any messages are logged to the workflow run log.
  4. On Complete status the activity returns Success.
  5. On Failed status the activity logs the failure message and returns Error.
  6. On any other unexpected status the activity logs a warning and returns Error.

Usage Patterns​

After ERP Dimension Sync​

ERP Integration ──> Process Metadata Changes ──> Run Calculation
  (syncs dimension members)   (applies structure)   (uses updated members)

After Bulk Import of New Members​

ETL ("Import_NewMembers") ──> Process Metadata Changes ──> Run Report Book

Usage Notes​

  • This activity is a blocking operation — the workflow waits for metadata processing to complete before continuing.
  • Processing time varies with the size of the model. For large models with many dimensions, allow for several minutes.
  • If metadata processing fails, the failure message from the processing service is written to the workflow run log. Check there for details on what caused the failure.
  • Running Process Metadata Changes when there are no pending changes is safe — it will complete quickly with a success status.

Best Practices​

  • Always place Process Metadata Changes after any activity that modifies dimension structure (ERP Integration, dimension imports) and before any activity that depends on that structure (calculations, ETL, reports).
  • Wire an error arrow so metadata processing failures are surfaced to the relevant team.

JSON Reference​

{
  "discriminator": "ProcessMetadataChangesWorkflowActivity",
  "activityId": "<uuid>",
  "name": "Process Metadata Changes",
  "positionX": 0,
  "positionY": 0,
  "advanceRule": 2
}

This activity has no additional configurable properties beyond the common base properties.