Loading Assignments and Resource Requests Incrementally in Work Planners

You can incrementally load records in Work Planner when the maximum results limit has been reached.

To load records incrementally in Work Planner:

  1. In the Allocation view, select your filter criteria in the filters panel and click Apply.
  2. If additional records can be loaded, this is indicated by one or both of the following:
    • + after the number of records in the toolbar
    • A warning message displays to indicate that some records are not displayed due to the maximum results limit.
  3. Click Load More. The Work Planner page displays the next set of records. Click Load More until all the assignments or resource requests grouped by project, resource, or RPG are displayed.

To view record details of assignments and resource requests, see Viewing Record Details.

For more information, see Using Work Planners.

Limitations

To ensure consistency in determining which results are displayed and those that are omitted, the following rules apply:

  • You can easily load approximately 6,000 records on the Work Planner page. However, if you encounter performance issues while loading more than 6,000 records, we recommend that you refine your filtering criteria.
  • We recommend that you save the changes before loading more records. If you try to save records in bulk, you may hit Salesforce limit issues.
  • A maximum of 200 additional resources that have no assignments or resource requests in the date range specified in the filters panel are displayed in a single load. Clicking the Load More button loads the next 200 additional resources. These resources all have 100% availability according to the specified date range. The Utilization Engine object is used to determine availability of resources in work planners. If there are no records of the Utilization Engine object associated with a specific resource, the resource is not displayed in the work planner.
  • When grouped by project, assignments and resource requests are ordered by Project Name, then Project ID, then Record ID. Data is omitted based on alphabetical order.
  • When grouped by resource, assignments and resource requests are ordered by Resource Name, then Resource ID, then Record ID. When Shield Platform Encryption is enabled in an org, if the Contact Name field is encrypted via Salesforce's Shield Platform Encryption, assignments and resource requests are ordered by Contact ID. Data is omitted based on alphabetical order.
  • When grouped by resource or project, any records that you retrieve are added to the end of the page. These records are alphabetically ordered by name. If the associated assignments and resource requests can only partially be displayed due to the maximum limit being reached, you can load more records incrementally in the Allocation view using the Load More button.
  • When grouped by region, practice, or group, assignments and resource requests are sorted by Record ID in descending order. Any records that you retrieve are added to the existing parent records or new parent records. If you prefer to display more records in the Allocation view, the order of the displayed records may change.