IHC Mappings Concur to PSA Fields

The metadata type records are used when you enable the Integration Hub Connector: Concur - PSA feature in the Feature Console, to push keys and mappings from PSA to the Integration Hub.

Here is a description of the fields and buttons that are available for Integration Hub Connector: Concur - PSA mapping, including fields and buttons that are available on the Concur - PSA Configuration Lightning page.

Notes:
  • To use the Concur - PSA Configuration Lightning page and Foundations Mapping component, you must have the IHC - Configure Mappings and FDN Core - Mapping permission sets assigned. Contact your administrator if you require these permission sets. For more information, see Permission Sets and Other Technical Documentation.
  • You must also assign permissions to the PSA Assignment, Expense, Expense Report, Project, and Resource objects and fields. Even if you do not assign object and field permissions for the PSA PSA Assignment, Expense, Expense Report, Project, and Resource, you can still view the existing mappings while adding or editing the mappings, but you cannot select any objects and fields.

The custom metadata type is used for defining the mappings between objects and fields in PSA and Concur in the Integration Hub. If needed, you can change the default mappings or add new ones. For more information, see Customizing Concur - PSA Mappings.

The following fields and columns are displayed in the Concur - PSA Mappings section of the Concur - PSA Configuration Lightning page.

IHC Mappings Concur - PSA Fields on Lightning Page
Field Description
Source Object The source object for the selected Concur report.
Target Object The target object for the selected PSA expense report.
Key The identifier for the mapping. This is unique in each level of the mapping hierarchy.
Source The data source.
Target The target for the data.

The metadata type records are used when you enable the Integration Hub Connector: Concur - PSA feature in the Feature Console, to push the keys and mappings from PSA to the Integration Hub.

Here is a description of the fields available on IHC Mappings Concur to PSA records.

Note:

The fields listed in the table are visible only in Custom Metadata Types and not on the Concur - PSA Configuration Lightning page.

IHC Mapping Concur to PSA Custom Fields
Field Description
IHC Mapping Concur to PSA Name Unique API name of the mapping.
Label Name of the mapping. By default, it is the concatenation of the VDR Name and the VDR Key.
PSA Field

The name of the PSA field you want to map to the third-party application.

Notes:
  • You must ensure that the PSA field type matches the third-party application field type. For example, you must map a Boolean PSA field (checkbox or formula field) to a Boolean field in the third-party application.
  • If you want to change the default mapping for the Project Manager field, you must specify a field that exists on the Contact object using the appropriate relationship from the Project object. For example, to sync a custom Employee ID field, enter pse__Project_Manager__r.Employee_ID__c.
PSA Object The name of the PSA object that contains the PSA field.
Third Party Application The name of the third-party application that you want to map PSA fields to. For example, "Concur".
Third Party Application Field The name of the third-party application field that you want to map to.
Third Party Application Object The name of the third-party application object that contains the third-party application field.
VDR Key

Virtual data resource key used to identify the mapping in the Integration Hub. You can enter any value for the VDR key.

When creating a new mapping, the following restrictions apply:

  • The VDR key and VDR name combination must be unique.
  • The VDR key must not contain white spaces.
Tip:

We recommend using the name of the source field or the target field as the VDR key, so that the mapping can be easily identified. For example, if you are mapping a Concur field named Payment Type to a PSA field named Payment Type, we recommend using PaymentType as the VDR key.
VDR Name Name of the virtual data resource in the Integration Hub.

The following buttons are displayed in the Concur - PSA Mappings section of the Concur - PSA Configuration Lightning page.

Button Description
Add Mapping Create a new mapping for the Concur - PSA Integration.
Push Mappings Push mapping updates for the Concur - PSA Integration to the Integration Hub.

The following actions are available for rows in the table.

Button Description
Edit Edit the details of the mapping.
Delete Delete the mapping.
Add Child Mapping Create a new child mapping for this child relationship.

The following fields are available when you click Add Mapping. Depending on your selections, different combinations of fields are visible.

Key: F – Field; CR – Child relationship; S – Static source; L – Lookup; CM – Child mapping; AL – Advanced lookup.

Field   Description
Message Key   The identifier for the mapping on the message type.
Source Type   The type of data being sent, such as a value from a field, a static value, or a child relationship.
Source Field Path F The field on the source object or a related object that contains the source data.
Source Description S The description of the fixed data to send in the mapping.
Source Data S The exact value to send in the mapping.
Source Child Relationship

C

R

 The related object that provides child source data.
Target Type   The type of target, such as a field, child record, or a lookup that contains a non-unique name.
Target Field   The field in which to store the data from the source.
Target Child Relationship

C

R

 The related target object for which you want to create records.
Child Filter Field

C

R

 The checkbox or formula field that determines whether to create or update child records. If specified, records are created or updated when the field equals true.
Record Creation Method

C

R

The way you want to create and maintain linked records:

  • Always Add
  • Always Replace
  • Update Matching
  • Update Matching and Delete
Target Lookup

A

L

 The field that stores the data from the advanced lookup.
Additional Identifier on Concur Report

A

L

 The additional identifier on Concur report field to compare to identify a unique record.
Additional Identifier on User

A

L

 The additional identifier on user field on the related object to compare to identify a unique record.
Data Transformation Table   The data transformation table to apply to the target field.