How to Configure Advanced Resource Plan Settings in OnePlan

  • Updated

Direct Answer: How to Configure Advanced Resource Plan Settings in OnePlan

To configure advanced resource plan settings in OnePlan, click Setup in the left navigation bar, select the pencil icon next to Resource Plan, and locate Advanced. From there you can set Capacity Month Range, FTE Hours, Pre-Filters, Enable Private/Public Entries, Match Field, External ID Field, and Ignore Time Off Cost Types. Select each setting’s control to change its value; changes take effect immediately for the Resource Plan App.


What This Article Covers: Advanced Resource Plan Settings

This article explains how to open the Resource Plan settings page and configure its Advanced settings, including capacity calculation ranges, FTE conversion, private/public entry visibility, named-resource matching, external ID mapping, time-off display, and Pre-Filters.

What you will accomplish By the end of this article, you will be able to locate the Advanced settings on the Resource Plan settings page, configure each available setting, and add a Pre-Filter to control which resources load into a resource plan.


Before You Begin: Configuring Advanced Resource Plan Settings

Before you begin, make sure you have:

  • A OnePlan account with administrator-level access to the Resource Plan App settings (Needs SME confirmation: exact required permission/role name)
  • Access to the Modify Navigation and App Settings panel in OnePlan
  • The Resource Plan App enabled in your environment

Why This Matters: Advanced Resource Plan Settings

Context: How Advanced Settings Affect the Resource Plan App

The Advanced settings on the Resource Plan settings page control how capacity, FTE conversions, private entries, and resource matching behave across the Resource Plan App. Because these settings apply system-wide, changes made here affect how resource plans calculate and display data for all users.

Context: How Pre-Filters Work

Pre-Filters narrow the number of resources loaded into a resource plan, showing users only the kinds of resources they need and improving query performance. Without pre-filters, a resource plan loads all available resources, which can slow performance in larger organizations.


Step-by-Step: Configuring Advanced Resource Plan Settings

Task: Access the Resource Plan Settings Page

Starting from anywhere in OnePlan:

  1. Click Setup in the left navigation bar. accessadmin.png

  2. Select the pencil icon next to Resource Plan. rpadmin.png

Task: Configure the Advanced Settings

Under the Advanced heading, configure any of the following settings as needed:

Setting Description
Capacity Month Range Controls how far in the future capacity is calculated in the OData reporting feed (5 years maximum; 2 years or less is recommended for better OData feed performance). The number of months selected starts from the current month.
FTE Hours If left blank, the default calendar’s hours-per-day value is used for FTE-to-hours conversions.
Pre-Filters Narrows the resources loaded into the resource plan. See the Add a Pre-Filter task below.
Enable Private/Public Entries When enabled, each row added to the resource plan is private.
Match Field Sets the method for matching named resources with generic resources. Default is Role. Options include Business Unit or Role.
External ID Field Specifies a plan-level field to use as the unique key for each plan. If no field is specified, the plan ID field is used.
Ignore Time Off Cost Types Specifies resource plan types (cost types) where time off should not be displayed. If no cost type is selected, time off displays in all types.

Advanced Settings.png

Task: Add a Pre-Filter

Starting from the Advanced section of the Resource Plan settings page:

  1. Select the Add Pre-Filter (+) button.

  2. Complete the Add Filter form:

    • Field: Select the field used to filter resources. Options include Business Unit, Location, Manager, Resource Type, Role, Timesheet Administrator, Timesheet Manager, Generic, and plan-level fields (choice, people picker, and yes/no fields), which are labeled with the field name followed by (Plan) — for example, State (Plan).
    • Required: Select the check box to make the pre-filter required.
    • Max Items: Enter the maximum number of items returned in a query. There is no upper limit, but returning fewer items improves performance.
  3. Select ADD.

    145c5835-c04e-4394-ac33-813ae838e5d8.png


Frequently Asked Questions: Advanced Resource Plan Settings

Q: How do I control how far in the future capacity is calculated in OnePlan? A: In OnePlan, open the Resource Plan settings page, expand the Advanced topic heading, and set the Capacity Month Range value. Up to 5 years can be selected, though 2 years or less is recommended for better OData reporting feed performance.

Q: What happens if I leave the FTE Hours setting blank in OnePlan? A: If the FTE Hours setting is left blank on the Resource Plan settings page in OnePlan, the default calendar’s hours-per-day value is used for FTE-to-hours conversions.

Q: What are Pre-Filters used for in the OnePlan Resource Plan App? A: Pre-Filters in the OnePlan Resource Plan App narrow the number of resources loaded into a resource plan so users see only relevant resource types. This also improves query performance by limiting the number of items returned.

Q: What does the Match Field setting control in the Resource Plan App? A: The Match Field setting on the Resource Plan settings page controls how OnePlan matches named resources with generic resources. The default is Role, and the other available option is Business Unit.

What to Do Next: Advanced Resource Plan Settings

Get started with related tasks: - How to Add Named Resources in OnePlan - How to Configure Resource Plan Custom Fields in OnePlan - How to Configure Timesheet Billable Settings in OnePlan

Learn about related topics: - How to Configure Calendar Settings for the Resource Plan in OnePlan - How to Configure Resource Plan Types in OnePlan

Was this article helpful?

0 out of 1 found this helpful

Comments

0 comments

Article is closed for comments.