Preparing the Data Environment for PSA Analytics

In order to ensure that PSA data displays correctly in PSA Analytics, you must complete the following setup steps.

Objects Accessed by the PSA Analytics Dataflow

The PSA Analytics dataflow requires data from several PSA related objects. To avoid conflicts, we recommend you to have at least one record for each of the following objects in your PSA environment before you create your PSA Analytics app.

Note: PSA Analytics doesn't support project hierarchies. Only data for top-level projects is displayed in the PSA Analytics datasets.

If you want to use the Billing Forecasts, Revenue Forecast (Embedded) and Project Margin dashboards, which are optional to PSA Analytics, the following objects are also required:

If you want to use the Utilization Analytics (Embedded) dashboard, which is optional to PSA Analytics, the following objects are also required.

Custom Settings Used by PSA Analytics

To perform the necessary calculations to your PSA utilization data used by PSA Analytics, ensure that the following PSA custom settings are enabled.

For more information, see Utilization Settings in the PSA Help.

Preparing the Calculations Used by PSA Analytics

To display your data in Analytics, PSA Analytics uses several PSA calculations.

To display the backlog data, PSA Analytics uses the most recent backlog calculation available. In order to display your information correctly, PSA Analytics requires you to create the backlog calculation in PSA as specified below:

  • Ensure the checkbox Calculate Project Backlog is selected.
  • In order to display the latest data in PSA Analytics, we recommend you select the most recent date as the start date for the calculation.
  • Ensure you have set up alternate backlog currencies in your org. PSA Analytics requires that Backlog Details Converted records exist in your org's environment.

Setting up Alternate Backlog Currencies

  1. From Setup, navigate to Custom Code | Custom Settings. Using ClassicClosed From Setup, navigate to Develop | Custom Settings.
  2. Click Backlog | Manage | Edit.
  3. In the Backlog Details Corporate Currencies field, enter your preferred reporting currency.
  4. Click Save.

For more information on working with Backlog, see see Setting Alternate Backlog Currencies in the PSA Help.

Note: In some cases, the PSA calculations can fail if the number of records is too large. If this happens and you receive an error executing the calculation, narrow the date range selected and try again. If the error persists contact your PSA administrator.

In order to display your information correctly, PSA Analytics requires you to create the utilization calculation in PSA as specified below:

  • Ensure the Is Report Master checkbox is selected as by default the PSA Analytics dashboards filter results by this criteria. If you want to display calculations that doesn't have the field Is Report Master selected, you need to manually edit the utilization calculation step in Analytics Studio.
  • If you enable Uncheck Master Based On Time/Parent Utilization setting in PSA, you must select a time period record. For more information, see Utilization Settings in the PSA Help.

We recommend you follow these steps when creating your utilization calculations:

  1. Select the Calculate Historical Utilization checkbox.
  2. Select a start date for the historical utilization.
  3. Select an end date for the historical utilization. This is your cut-off date for the historical period of this calculation, ensure the end date is the present date.
  4. Select the Calculate Scheduled Utilization checkbox.
  5. Select a start date for the scheduled utilization. This is the beginning of the scheduled period of this calculation, ensure the start date is the present date.
  6. Select an end date for the scheduled utilization.
  7. Click Calculate to start the utilization calculation job.
  8. After the job is complete, ensure the details generated by the calculation have resources associated with them.
Note: In some cases, the PSA calculations can fail if the number of records is too large. If this happens and you receive an error executing the calculation, narrow the date range selected and try again. If the error persists contact your PSA administrator.

Utilization Analytics calculations requires data from Region, Practice and Group records. For more information about configuring RPGs for use in Utilization Analytics, see Setting up Utilization Analytics in the PSA Help.

Preparing the Data Required by the Additional Features

If you want to enable additional features in PSA Analytics, such as the Project Margin (Workspaces) or the Forecasts dashboards, ensure you apply the necessary data preparation steps to the org before you create or upgrade your app.

This dataset requires PSA Winter 2021 or later. This is due to a dependency on the PSA Opportunity Probability (%) field on the Revenue Forecast Version Detail object required for this dataset. In addition, you must have one or more records on the Revenue Forecast or Revenue Forecast Version objects in your PSA data environment.

PSA Analytics Forecasts requires data from either or both PSA Revenue Forecasting and Billing Forecasting, depending on your reporting requirements.

  • Ensure you have installed a version of PSA that supports forecasting. This functionality was introduced in the Spring 2019 version of PSA in the form of PSA Enhanced Services Forecasting. This was subsequently renamed Billing Forecasting in the Spring 2020 version of PSA. However, it is recommended that PSA users adopt Revenue Forecasting as their forecasting solution. For more information, see About Forecasting in the PSA Help.
  • Ensure your data environment has at least one successful forecast calculation created and that you select the Current checkbox for this calculation.
  • Ensure the associated forecast records for the calculation exist before running the dataflow.

For more information on running forecasts, see the PSA Help.

The following steps are necessary in order to run the PSA Analytics dataflow with Project Margin enabled:

  • Ensure that your org corporate currency matches the integration user currency. This is the currency displayed in all Analytics data.
  • Add the corporate currency ISO code as a configuration value to the ProjectConvertionCurrencies configuration option in PSA.
  • Ensure your org contains project actual converted records for the currency that matches your integration user currency. For more information on how to create converted records, see Recalculating Resource and Project Actuals in the PSA Help.
  • By default the parameter ignoreLast is enabled in the Project Margin dashboard. To prevent display errors, we recommend you generate project actual converted records for the current month even if the month is starting.