Editing Existing Mappings on Custom Metadata Types
The new Concur - PSA Configuration Lightning tab allows you to edit mappings on the PSA objects, but you can also manually edit mappings in the Setup.
The following examples provide steps on how to edit an existing mapping:
Example 1 - Map Project Manager Custom PSA Field
The following example contains the necessary steps for editing the existing mapping for the Project Manager field in Concur. You can edit other mappings following the same steps.
By default, the project manager's email is synced to Concur. You can change this to any custom field.
- In Setup, click Custom Code | Custom Metadata Types.
- Next to IHC Mapping Concur to PSA, click Manage Records. A list of existing mappings displays. For a description of all the available fields and the accepted values, see IHC Mappings Concur to PSA Fields.
- Next to PSAProject ProjectManager, click Edit.
- Next to PSA Field, enter pse__Project_Manager__r. followed by the API name of a field on the Contact object. For example, pse__Project_Manager__r.Employee_ID__c.
- Leave the remaining values unchanged.
- Click Save. The changes to the mapping are now saved.
Example 2 - Use Custom Checkbox Field to Send Projects to Concur
The following example contains the necessary steps for editing the existing mapping that controls which PSA projects are eligible for sending to Concur. You can follow similar steps to change the fields that control which assignments and resources are sent to Concur.
- In Setup, click Custom Code | Custom Metadata Types.
- Next to IHC Mapping Concur to PSA, click Manage Records. A list of existing mappings displays. For a description of all the available fields and the accepted values, see IHC Mappings Concur to PSA Fields.
- Next to PSAProject SendToThirdPartyExpensesAppli, click Edit.
- Next to PSA Field, enter the API name of your custom field, for example, Sync_with_Concur__c.
- Leave the remaining values unchanged.
- Click Save. The changes to the mapping are now saved.