Shared Data Model Mappings in SPM Control Center

Edit online

Overview

Shared Data Model (SDM) mappings connect the entities and fields in your Targetprocess account to the entities and fields that SPM Control Center requires. These mappings are necessary when a Targetprocess environment uses non-standard configurations, custom fields, or partial solution setups.

SDM mappings define how your account’s entities and fields align to the Shared Data Model. This helps to ensure that SPM Control Center can:
  • Read data consistently from your Target process account
  • Process data correctly, even when the Targetprocess configuration does not match the default structure

SPM Control Center relies on the data stored in Targetprocess. The information displayed on dashboards such as Priorities, Workforce, Work, and Funding Requests is retrieved directly from the underlying Targetprocess work items. Accurate SDM mappings ensure that the displayed data is correct and aligned with the expected Shared Data Model.

SPM Control Center requires a specific account setup, including the correct solutions and compatible OKR/WFM versions. However, many customer environments, use customized configurations such as renamed fields, custom entities, or different solution versions. This mismatch can lead to data-fetching errors on SPM Control Center dashboards.

For example, a team may replace standard fields like Team Allocation with Resource Capacity or use custom work item types, or use a older OKR version that SPM Control Center does not recognize. SDM Mappings solve this by allowing users to map their unique Targetprocess configuration to the data model SPM Control Center expects, ensuring accurate workforce, work, priorities, and funding data across all dashboards.

Benefits of SDM Mappings

SDM mappings let you:
  • Identify mismatches between what SPM Control Center expects and what the user account contains
  • Allows you to fix missing or mismatched items
  • Ensures SPM Control Center dashboards load without errors
  • Provides options to remap fields to alternatives (when appropriate)
  • Disable unavailable entities or fields
  • Prevent SPM Control Center from throwing API errors due to missing configurations

Accessing SDM Mappings

Before you begin, ensure that SPM Control Center is enabled.

To access SDM Mappings:
  1. Log in to Targetprocess.
  2. Click System Menu > Settings.
  3. From the left navigation menu, select Shared Data Model.

Using SDM Mappings

The SDM Mappings page lets you define which Targetprocess entities and fields SPM Control Center uses. The Shared Data Model column in the SDM Mappings table shows the standard data schema that SPM Control Center requires to work properly. Each mapping connects an entity in your Targetprocess account to the corresponding entity in the Shared Data Model used by SPM Control Center.

For example, when SPM Control Center retrieves data about Agile Release Trains, it expects the corresponding entity in your workspace to include at least an ID, a Name, and a reference to the related structures. If your workspace uses different entity names or field names, you can use the SDM configuration screen to map your custom setup to the format SPM Control Center needs.

Default View
  • Only conflicting or modified items are shown.
  • You can enable Show unmodified to display everything.

    sdm mappings show unmodified checkbox

Warnings (Exclamation Marks) warning
A warning appears when:
  1. Entity type exists but a required field is missing

    Sometimes SPMCC can recognize an entity in your Targetprocess account, but one or more of the fields it expects are not available.

    Example:Agile Release Train exists, but the field Solution Train does not.

    In this situation, the entity is present, but when you expand it in the SDM configuration, you notice that a required field is missing. This means that the corresponding solution or feature is not installed in the account. For example, Agile Release Trains may be installed, but Solution Trains are not.

  2. Entire entity type is missing

    Example: Traditional Projects or certain WFM entities may not be installed.

To address a missing mapping, select a Targetprocess entity or field to map to the Shared Data Model. If your Targetprocess account does not include a comparable entity or field, select No Mapping. This prevents SPM Control Center from generating errors during data fetches.

Note:

In many cases, setting the field to No mapping is enough to allow dashboards to load successfully.

Shared Data Model Mapping Profiles

For new SPM Control Center configurations, the <Default> profile is selected.

Default profiles:
  • Cannot be modified or overwritten
  • Display errors when your account configuration does not match the expected schema
  • Do not allow you to save any changes

To apply an alternative profile, select the profile from the menu and click Save to apply the selected profile.

To create an additional mapping profile, edit an existing profile and use Save as to create the new profile.

To save a custom mapping:
  1. Click Save As.
  2. Name the profile (standard: SPMCC).

  3. Once saved, you can edit it based on your requirement.
You can perform the following actions:
  • Delete: To delete a profile, click the bin icon.
  • Import from clipboard: Click the three dots to access options.
  • Export to clipboard: Click the three dots to access options.
profile configurations
Entity mapping details
To review the entity mapping details, click the arrow on the left side of the entity listing. The details for each entity mapping indicate how Targetprocess fields are mapped to fields in the Shared Data Model.
  • A circled 1 indicates identity mapping, meaning there is a one-to-one match between fields.
  • An arrow indicates that the field mapping is custom.
  • A No mapping symbol indicates that the field mapping is absent.

No Mapping

For any field or entity showing a warning, set it to No Mapping

No mapping allows you to get rid of the errors when SPM Control Center is trying to fetch information that may not be configured on a target account

No Mapping allows SPM Control Center to:
  • Ignore the unmapped field or entity and not attempt to fetch it
  • Treat missing values as empty instead of generating API errors

Examples

Scenario Solution
Missing field on an existing entity Set that field → No Mapping
Entire entity type missing Set entity → No Mapping
Missing WFM fields (Labor ID, mandays, etc.) Set → No Mapping

To set a field or entity to No Mapping:

  1. From the left menu, select Shared Data Model.
  2. On the SDM Mappings page, check for all warnings.

    shared data model mappings screen showing all the entities and fields

    By default, SDM mappings only shows mappings that are in conflict or modified. Select the Show unmodified checkbox to display all entity mappings for the profile. Clear the checkbox to focus on entity mappings that have been modified.

  3. For each warning:
    1. Set field or entity → No Mapping.
    2. Save configuration as a new profile.
    3. Use that profile in SPM Control Center.

    This ensures SPM Control Center does not break, even if your account is partially configured.

After you set a field or entity to No Mapping, dashboards in SPM Control Center displays:
  • Empty lists
  • Zero counts
  • Blank relationships

For Example:

If Portfolio Epic → Strategic Objective is unmapped, the Priority dashboard in SPM Control Center will show zero linked items instead of errors.

Field-Level Remapping

In some situations, you might need to remap fields so that SPM Control Center can correctly interpret your account’s data.

Remapping is useful when:
  • A custom field is used instead of the standard field expected by SPM Control Center.
  • A field with a compatible data type exists in a different entity.
  • A semantically equivalent field is available and can serve as a substitute (for example, using a Start Date field from another entity).

Example:

If the Capacity entity does not have a Planned Start Date field, you can map it to the Start Date field from Team Assignment, as long as the meaning aligns with how SPM Control Center uses the data.

Important Considerations When Remapping

When creating alternative field mappings, ensure that:

  • Data types match (e.g., date fields to date fields, text to text)
  • The scenario is simple

For complex cases, it is best to seek assistance from the SPM Control Center support team.

Limitations

SDM mapping does not work for:

  • Heavily customized account structures
  • Unusual data models
  • Unique customer-specific workflows outside the SAFe/SPM model

Remapping is limited and should be coordinated with the SPMCC team for complex cases.