In addition to entering forecast overrides interactively using the override grid, Forecast Pro allows you to import overrides from other Forecast Pro projects, from Excel spreadsheets (both row and transaction-style) and from databases using ODBC.
Excel/CSV
The sample file shown below is installed into the Forecast Pro input directory and is named 123 Bakery – Overrides.xlsx. Note that this file is for the standard override mode (TRAC version 8.3 or later).
The first columns (A through D in our example) define the attributes and name of the item (i.e., the hierarchy information).
The next column (E in our example) must have “Date” as the header. Dates may be entered in an Excel format, or in a Year-Period format ( e.g. 2026-July or 2026-52).
The next column (F in our example) must have “Override” as the header. The override value is entered here. Please note that you may use formula overrides as well as number overrides. Formulas must begin with an equal sign (if using Excel, use an apostrophe before the equal sign to prevent Excel from executing the formula).
The next column (G in our example) has “Comment” as a header. This is where override comments are entered.
The final column (H in our example) is optional. If used, it must have “Locked” as the header. To lock an override in standard mode, simply enter “Yes” here.
If you are using TRAC v8.2 or earlier or are using Multi-row Override or Multi-row Incremental mode, there is an additional column (column F in our example) to specify the Override Row, as shown below in the sample file, 123 Bakery – Overrides – Multi-row Mode.xlsx.
The Override Row can either be a number field identifying the row number or a text field identifying the row name.
Multi-row modes do not support locking. If you are using a multi-row mode, do not include a locked column in the file.
ODBC
If you plan to import your overrides using ODBC, examine the Overrides table in the sample Access database file 123-Bakery-ODBC.mdb located in the Forecast Pro input directory.
Notice that the attribute fields are present.
- FC_Period and FC_Year are number fields identifying the forecast date for the override.
- (Multi-row modes and TRAC v8.2 and earlier) Override_Row can either be a number field identifying the row number or a text field identifying the row name. This column should be excluded for TRAC Standard mode.
- Override_Value is a numeric field for the value of an override. It does not need to be included if Override_Formula is present and populated for all rows. If Override_Value and Override_Formula are included, only one should be populated for each row.
- Override_Created is a date/time field identifying when the override was created. If the entry is blank the override report will list the date/time that the override was loaded into the project.
- Override_Comment is a text field containing the comment you wish to associate with the override. If the entry is blank, no comment will be associated with the override.
Formatting rules
In a spreadsheet, a header row is required. The Row and Comment fields must be present and labeled accordingly.
In a spreadsheet, the dates in the header row need to be either in an Excel format, or in a Year-Period format, e.g. 2026-July, or 2026-52.
Overrides can be assigned at any level.
The override row can be specified by either the row number or the row name. Please note that the override row should only be included for multi-row modes and TRAC v8.2 and earlier.
Overrides can be entered as values or formulas. In ODBC, values should be included in the Override_Value field and formulas in the Overide_Formula field. Only one of these field should be populated for each row.
If an item has no overrides, it does not need to be included in the spreadsheet, table or query.