Creating a Static Mapping for the PSA Resource API

When setting up subscriptions to create PSA resources via the REST API, you can map the Static key to any field that requires a constant value. This enables you to automatically enter additional information for each resource, saving time on data entry.

You can use a data transformation table (DTT) in Foundations to specify the target value you want to enter for a particular mapping from the Static key.

To do this:

  1. Create a DTT in Foundations.
  2. In the Source Value 1 field, enter the value for the Static key: TRUE
    Tip:

    When creating a DTT for the Static key, always use the source value TRUE, regardless of the field type you want to map to.

  3. In the Target Value field, enter the value you want PSA to enter automatically.

For more information, see Data Transformation Tables and Creating a Data Transformation Table.

On the relevant PSA Resource API relationship, do the following:

  1. Create a mapping between the Static key and the target field.
  2. Specify the data transformation table you want to use.

If required, you can map the Static key to more than one field as long as you link each mapping to a unique DTT.

The following table displays some examples of how you can use the Static key to enter constant values.

Aim

Key

Source Value 1

Target Field

 

Target Value
Create all API resource records using a particular record type on Contact object (Resource). Static TRUE Record Type ID

Resource

Note:

For record types, the DTT value must match the record type name, not the record type label. For example, if your record type label is Resource, but the name is Resource_HCM, enter Resource_HCM as the target value in the DTT.
Include a static description for all API resource records. Static TRUE Contact Description Created via PSA API
Include a static account name on all API resource records. Static TRUE Account Name Merlin Technologies

For more information about Foundations mappings, see Adding Mappings to a Messaging Relationship.