Configuring Dimension and Analysis Fields in SRP
SRP can automatically populate dimension and analysis information on Accounting documents created from PSA records. When an Accounting document is posted, these values are copied to the relevant transaction line items. You can then use the values for reporting purposes.
What Is the Difference between Dimension and Analysis Fields?
Dimensions and analysis fields relate to the same accounting concept. The main difference between the two is the field type. Dimension 1-4 are lookup fields, while Analysis 1-4 are text area fields. Depending on your requirements, you can optionally use the Analysis 1-4 fields alongside Dimension 1-4.
Dimensions are FinancialForce Accounting objects. Other Accounting objects contain lookups to Dimension 1-4 objects. For more information, see
SRP adds Analysis 1-4 text area fields to the following Accounting objects:
- Journal Line Item
- Payable Credit Note
- Payable Credit Note Expense Line Item
- Payable Invoice
- Payable Invoice Expense Line Item
- Sales Credit Note
- Sales Credit Note Line Item
- Sales Invoice
- Sales Invoice Line Item
- Transaction Line Item
How Are the Field Values Retrieved from PSA?
If you create Analysis 1-4 and Dimensions 1-4 fields for PSA objects, when you create ClickLink and integration rules in legacy mode When SRP runs in legacy mode, it uses the older mechanism that were introduced before Spring 2021. Some features and modern user experience components aren't available in legacy mode. Legacy mode is enabled when the Run Integration in Enhanced Mode field in the SRP Integration Settings custom setting is deselected., SRP automatically adds the relevant mappings. That way, you don't need to manually create the additional mappings. For this to work, you must manually create unmanaged fields with the exact API names as detailed in the table below.
API Name of the Unmanaged Field |
API Name of the Mapped Managed Field |
---|---|
Analysis1__c | ffpsai__Analysis1__c |
Analysis2__c | ffpsai__Analysis2__c |
Analysis3__c | ffpsai__Analysis3__c |
Analysis4__c | ffpsai__Analysis4__c |
Dimension1__c | c2g__Dimension2__c |
Dimension2__c | c2g__Dimension2__c |
Dimension3__c | c2g__Dimension2__c |
Dimension4__c | c2g__Dimension2__c |
While creating the fields from Setup, enter Analysis1, Dimension1, and so on, as the API name. When you save the changes, Salesforce automatically appends __c. For more information about creating custom fields, see the Salesforce Help.
You can create these fields for the source objects listed in the table below.
Source Object | Related Flow | Target Objects |
---|---|---|
Billing Event | Billing Events to Sales Invoices or Credit Notes |
Sales Invoice Sales Credit Note |
Billing Event Item | Billing Events to Sales Invoices or Credit Notes |
Sales Invoice Line Item Sales Credit Note Line Item |
Miscellaneous Adjustment | Miscellaneous Adjustments to Journals | Journal Line Item |
Vendor Invoice |
Vendor Invoices to Payable Invoices or Credit Notes Employee Expenses to Payable Invoices or Credit Notes |
Payable Invoice Payable Credit Note |
Vendor Invoice Item |
Vendor Invoices to Payable Invoices or Credit Notes Employee Expenses to Payable Invoices or Credit Notes |
Payable Invoice Expense Line Item Payable Credit Note Expense Line Item |
When manually creating the fields for PSA objects, you must ensure that you use the correct field type. The following table details the supported field types.
Field |
Text or Text Area |
Lookup |
Formula (Text) |
---|---|---|---|
Analysis 1-4 | Yes | No | Yes |
Dimension 1-4 | No |
Yes. This must be a lookup to the Dimension 1-4 objects. |
Yes |
For more information about field types, see the Salesforce Help.
Mapping Examples
The following examples provide more information about potential implementations of dimension and analysis fields. You can apply the same basic principles to more complex scenarios.
You might want to store the names of the region, practice, group, and project related to a billing event item in the Analysis 1-4 text fields for sales invoice line items. In that case, you can create formula fields on the Billing Event Item as listed in the table below.
Field Label |
Field API Name |
Formula |
---|---|---|
Analysis 1 | Analysis1__c | pse__Project__r.pse__Region__r.Name |
Analysis 2 | Analysis2__c | pse__Project__r.pse__Practice__r.Name |
Analysis 3 | Analysis3__c | pse__Project__r.pse__Group__r.Name |
Analysis 4 | Analysis4__c | pse__Project__r.Name |
You might want to associate regions with dimension 1 records, practices with dimension 2 records, groups with dimension 3 records, and projects with dimension 4 records. You can then use formula fields to populate the dimensions on the related vendor invoice items. SRP can leverage this to automatically link payable invoice expense line items to the appropriate dimensions.
To do this, you must first create the lookup fields as detailed in the table below.
Object |
Field Label |
Field API Name |
Lookup To |
---|---|---|---|
Region | Dimension 1 | Dimension1__c | Dimension 1 |
Practice | Dimension 2 | Dimension2__c | Dimension 2 |
Group | Dimension 3 | Dimension3__c | Dimension 3 |
Project | Dimension 4 | Dimension4__c | Dimension 4 |
You can then create formula fields on the Vendor Invoice Item object as detailed in the table below.
Field Label |
Field API Name |
Formula |
---|---|---|
Dimension 1 | Dimension1__c | pse__Project__r.pse__Region__r.Dimension1__r. |
Dimension 2 | Dimension2__c | pse__Project__r.pse__Practice__r.Dimension2__r. |
Dimension 3 | Dimension3__c | pse__Project__r.pse__Group__r.Dimension3__r. |
Dimension 4 | Dimension4__c | pse__Project__r.Dimension4__r. |
You might want to enable your users to select dimensions and enter analysis values when creating a miscellaneous adjustment. In that case, you can create the fields on the Miscellaneous Adjustment object as listed in the table below.
Field Label |
Field API Name |
Field Type |
---|---|---|
Analysis 1 | Analysis1__c | Text (255) |
Analysis 2 | Analysis2__c | Text (255) |
Analysis 3 | Analysis3__c | Text (255) |
Analysis 4 | Analysis4__c | Text (255) |
Dimension 1 | Dimension1__c | Lookup (Dimension 1) |
Dimension 2 | Dimension2__c | Lookup (Dimension 2) |
Dimension 3 | Dimension3__c | Lookup (Dimension 3) |
Dimension 4 | Dimension4__c | Lookup (Dimension 3) |