You can map a text field to a lookup field. If the text value matches the name of a record, the lookup is populated on the resulting record. Otherwise, an error displays and the resulting record is not created.
This can be useful if you have records of different objects with the same name. For example, if your regions have the same names as your dimension 1 records. In that case, you can map Region Name to Dimension 1. When creating the Accounting document, PSA – Accounting Connector tries to match the region to a dimension 1. If a matching dimension 1 isn't found or multiple dimension 1 records with the same name exist, the Accounting document is not created. Before using name to lookup mappings, you must ensure that the relevant records exist.
Return Mappings
After creating an Accounting record from a PSA record or vice-versa, PSA – Accounting Connector updates the originating record. For most flows a checkbox field is selected on the originating records to mark the record as processed. For the Billing Events to Sales Invoices or Credit Notes flow, several fields are updated on the billing event. These are defined as return mappings.
The following examples provide steps for creating different types of mappings. For a full list of the options available in the FDN Mappings Lightning component, see Adding Custom Mappings from the FDN Mappings Component.
This example demonstrates how to map the name of the related region from the Billing Event object to Dimension 1 on the Sales Invoices. Note that this only works if your region records have the same names as your dimension 1 records.
To create the mapping:
Open the mappings for the Billing Event to Sales Invoice flow. For more information, see Viewing Mappings.
In the Billing Event to Sales Invoice Mappings section, click Add Mapping.
This example demonstrates how to map the Project lookup field from the Vendor Invoice Item object to the Project lookup field on the Payable Invoice Expense Line Item object.
To create the mapping:
Open the mappings for the Vendor Invoice to Payable Invoice flow. For more information, see Viewing Mappings.
Within the Vendor Invoice to Payable Invoice Mappings section, in the row with the source of pse__Vendor_Invoice_Items__r and target of
c2g__PurchaseInvoiceExpenseLineItems__r, click and then click Add Child Mapping.
This example demonstrates how to map the Project lookup field from the Miscellaneous Adjustment object to the Project lookup field on the Journal Line Item object.
To create the mappings:
Open the mappings for the Miscellaneous Adjustment to Journal flow. For more information, see Viewing Mappings.
Within the Miscellaneous Adjustment To Journal Mappings section, in the row with the source of Miscellaneous Adjustment and target of
c2g__JournalLineItems__r, click and then click Add Child Mapping.
Set the following values:
Source Type: "Field"
Source Field Path: Project
Target Type: "Field"
Target Child Type: Default
Target Field: Project
Click Save & New. This saves the mapping for the default journal line item and enables you to create an additional mapping for the balancing line item.
Set the following values:
Source Type: "Field"
Source Field Path: Project
Target Type: "Field"
Target Child Type: Balancing
Target Field: Project
Click Save. This saves the mapping for the balancing journal line item.
When you create a billable miscellaneous adjustment from a payable invoice expense line item, you might want to ensure that it can be included in the billing process. You can achieve this by creating static mappings for the Payable Invoice Expense Line to Miscellaneous Adjustment Recharge Customer flow. This example demonstrates how to map a static value of true to the Approved for Billing and Include in Financials checkbox fields on the Miscellaneous Adjustment object.
To create the mappings:
Open the mappings for the Payable Invoice Expense Line to Miscellaneous Adjustment Recharge Customer flow. For more information, see Viewing Mappings.
In the PINELI to Misc. Adjustment Recharge Mappings section, click Add Mapping.
When you create a payable invoice from a vendor invoice, Accounting calculates the Due Date field on the payable invoice. You might want this value to be populated back on the vendor invoice to let your vendors know when the payment is due. This example demonstrates how to map the due date from a payable invoice to a custom field on the originating vendor invoice. Note that we assume that you have already created a custom date field on the Vendor Invoice object named Payment Due On.
To create the mapping:
Open the mappings for the Vendor Invoice to Payable Invoice flow. For more information, see Viewing Mappings.
In the Payable Invoice to Vendor Invoice Return Mappings section, click Add Mapping.
SECTIONS
and then click