Managing the Custom Columns, Groupings, and Custom Mappings Used When Creating Resource Requests from Project Tasks (Lightning)

You can reference field sets in the Task-Based Resourcing custom setting to control the columns in the Create Resource Requests from Project Tasks and Create Held Resource Requests from Project Tasks Lightning windows. For more information, see Task-Based Resourcing Settings and Creating Resource Requests from Project Tasks.

To create a field set that contains the fields that you want to use:

  1. From Setup, open Object Manager, and then open the Project Task Assignment object.
  2. Select Field Sets, and then click New.
  3. Enter the details, and then click Save.
  4. Add the relevant fields to the list, and then click Save.

To add the name of this field set to the custom setting:

  1. From Setup, click Custom Code | Custom Settings and open the Task-Based Resourcing custom setting. Using Classic:Closed From Setup, click Develop | Custom Settings and open the Task-Based Resourcing custom setting.
  2. Click Edit for the relevant field:
    • Held Resource Request Groupings: Defines the field set containing the list of fields for grouping project task assignments that users can select from when they click Grouping Criteria when generating held resource requests:
      • If you do not add a field set, the options of Resource, Resource Role, External Resource, and Milestone are displayed.
      • If you add an empty field set, the options of Resource and Resource Role are displayed in the list.
    • Resource Request Groupings: Defines the field set containing the list of fields for grouping project task assignments that users can select from when they click Grouping Criteria when generating unheld resource requests:
      • If you do not add a field set, the options of Resource, Resource Role, External Resource, and Milestone are displayed.
      • If you add an empty field set, only the option of Resource Role is displayed in the list.
    • Resource Request Columns: Defines the field set used to display custom read-only columns. Your columns are added between the existing columns and the Notes column. Only values in the following columns are populated if added to the field set:
      • Region
      • Practice
      • Group
      • Currency
      • Opportunity
      • Average Cost Rate Number
      • Average Cost Rate Currency Code
      • Suggested Bill Rate Number
      • Suggested Bill Rate Currency Code
    • Resource Request Editable Columns: Defines the field set used to display custom editable columns. Your columns are added between the read-only columns and the Notes column. The following core fields are displayed by default, but are editable if added to the field set:
      • Start Date
      • End Date
      • Requested Hours
      • Notes
    Notes: The following field types are unsupported in the read-only and editable fields sets. Unsupported field types are: ID, Geolocation, Text (Encrypted), Time, Formulas, Auto Number, Roll-Up, Picklist (Multi-Select), and Summary. Text Area field types are supported but do not support line breaks.

    Users cannot edit the Resource Role, Resource, Status, or Resource Held fields, even if you add them to an editable field set. In addition, users cannot edit the Suggested Resource and Milestone fields if used as grouping criteria, even if you add them to an editable field set.
  3. In the field, add the API name of the field set that you created.
  4. Click Save.

For information about how to maintain field sets, see the Salesforce Help.

Column Ordering

When you use your custom field set in the custom setting fields detailed in the procedure above, the column order from left to right is:

  1. Core fields, excluding Notes: These are editable if they are also in the editable field set.
  2. Fields in the read-only field set: These are editable if they are also in the editable field set.
  3. Fields in the editable field set.
  4. Notes: This is editable if it is also in the editable field set.
Note: Core fields follow the order of the core group, and read-only fields follow the order defined in the read-only field set, even if they are also in the editable field set.

Grouping Criteria and Field Sets

The following fields on the resource request record are mapped from the default Resource Role, Resource, and Milestone fields on project task assignments:

  • When generating unheld resource requests, the Resource Role, Suggested Resource, and Milestone fields.
  • When generating held resource requests, the Resource Role, Resource, and Milestone fields.

If you are using the above fields to group resource requests, they are shown in read-only columns in the table, even if they are in the editable field set.

If users remove any of these fields from the grouping criteria list and they are not in the editable field set, the corresponding column is removed from the table.

If users remove any of these fields from the grouping criteria list and they are in the editable field set, they are shown in the table in an editable column.

Creating Custom Mappings from Project Task Assignment Fields to Resource Request Fields

Click Task-Based Resourcing Mappings in the PSA Custom Mappings section of the PSA Administration page to map additional project task assignment fields to resource request fields.

If a field used in the grouping criteria list has a custom mapping, read-only columns for the corresponding resource request fields are shown in the table.

For information on how to configure custom mappings, see PSA Custom Mappings.