Forecast Driver Import Interface validations

When you are importing a forecast driver using a CSV file, take note of these validations:

  • As of the 2026.03 release, there is no designated primary key for drivers. The driver's and team's names are combined and used to create a unique identifier. In this approach, you must update the team associated with each driver manually because the import process does not support updating the team for drivers. If the combination of team and driver name does not exist, a validation message is shown during update and delete operations
  • You cannot import a forecast driver if a driver with the same name and team name already exists in the system. You can only update or delete driver data. An error message indicating that a duplicate driver with the same name and team already exists is displayed upon import.
  • The update operation is supported for forecasts that were already generated using the driver or if the driver is associated to any staffing requirement.
  • The delete operation is not supported if forecasts were already generated using the driver. You must delete the forecast before deleting the driver through CSV import. An error message indicating that the record could not be deleted because forecasts in the system depend on it is displayed upon import.
  • The delete operation is not supported if the driver is linked to a staffing requirement. You must remove the link between the staffing requirements and forecast before deleting a driver. An error message indicating that the record could not be deleted because staffing requirements in the system depend on it is displayed upon import.
  • The delete operation is not supported for drivers linked to a data source.