Skip to content

Mapping Objects

The function of object mapping allows objects with varying names and IDs to be compared. While objects are compared, a user can replace a value in the source tenant with a new value. Object mapping also helps in locating referenced objects to the source object during the drafting process.

Object Mapping can be found by going to Advanced Settings > Object Mapping.

The following must be specified for effective mapping:

  • Object Type
  • JSON Path
  • Source Value
  • Target Value
  • Enabled Status

Create a Mapping

  1. From the dropdown Select a Tenant, choose the tenant you want to start mapping from.

    The different object types within that tenant displays.

    The JSON Path column identifies the specific field within a configuration object body that will be matched to the target value during the creation of the mapping.

    The values listed under Original Value provide the name of what the value was before it was mapped to something else.

    The values listed under New Value are editable. Hover over one you wish to change and a pencil icon displays. Select the pencil icon and change the value.

    The following is an example of a Configuration Hub object on the source tenant. To create a mapping of the owner's name field, you would enter the jsonPath "$.owner.name". The original value in this case would be "Imogene Mendez" The new value would be the identity name of the new owner in the target tenant.

    {
        "version": 1,
        "self": {
            "id": "5d09273380b2451e97d2d9c62b0992fb",
            "type": "ROLE",
            "name": "2 entitlement role"
        },
        "object": {
            "id": "5d09273380b2451e97d2d9c62b0992fb",
            "name": "2 entitlement role",
            "created": "2024-05-13T19:45:31.367466Z",
            "modified": "2024-07-11T19:20:19.676014Z",
            "description": "test update",
            "owner": {
                "type": "IDENTITY",
                "id": "ddabd13baa854bff97ced8f66499caee",
                "name": "Imogene M̩endez"
            }
        }
    

    The user has the ability to decide whether a particular mapping entry should be applied during the next draft creation process. To apply the mapping, select Enabled.

    Note

    When a new mapping is created, The Enabled column is turned off by default.

  2. To delete an object mapping from the tenant, select Delete.

To create a new mapping between objects, complete the following:

  1. Select Create New.

  2. To add a mapping, select Add Another. A row of empty values appears.

  3. From the dropwdown, select the Object Type.

  4. In the JSON Path field, type the specific field that needs to be matched to the target. This field value has to be started with $..
  5. In the Original Value field, type the old value.
  6. In the New Value field, type of the new value of the Object Type.

    Continue creating more mapping by selecting Add Another.

  7. If a new mapping is not needed, select Remove.

  8. When all mappings have been added, select Save Changes.

Important

Users cannot create duplicate mappings with the same object type, JSON path, and source value.

Note

During the draft creation, Configuration Hub uses Global Configuration Substitution Rules which are pre-configured logic for attribute value substitution. This helps reduce the manual adjustments of configuration settings which are required when comparing or migrating configurations between different environments:

  • Retain tenant specific attribute values of target tenant when deploying configurations (such as environment specific values, dates, owners)
  • Set default values for configuration attributes (such as state fields)
  • Attributes which should be ignored when comparing configurations between environments, to avoid false modify (such as dates, object owner, ids)
  • Array elements sorting rules

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.