Skip to main content
Import effects

Learn how to import effect data to Falcon from spreadsheets such as Excel and CSV files

Philipp Spahn avatar
Written by Philipp Spahn
Updated over a year ago

Which permissions are required for this function?

Write permission or higher



With Falcon's import function, you can import effects decentrally across any number of measures. The basis for this is an import file. The file has no defined structure, other than a set of column headers (see here). A template with a possible structure that you can customize is available via the download button:


Download the effect import template here


How to import

Select Import from the main menu at the bottom left and Effects from the dropdown. Then select the file you want to import.

Now select "Import". The data is then imported in the background. Once the import has been successfully completed, Falcon will ask you to refresh.


File structure and format

The import function reads a file, searches for specific column headers, and imports the information stored in the rows. The basis is an XLSX, XLS, or CSV file with at least the following columns:

Column header

Type

Example

Measure-ID

Integer

13456

Position-ID

Integer

98765

Type

Integer

Plan (or Actual)

Periods

Text

2021-Apr

Period types and format

The periods of the import file must be directly assignable to existing periods in Falcon. For this Falcon needs a special period format:

Period type

Type

Format

Example

Result

Weekly

String

JJJJ-CW-##

2021-CW-20

20. CW 2021

Monthly

String

JJJJ-MMM

2021-Mar

March 2021

Quarterly

String

JJJJ-QQ

2021-Q1

First Quarter 2021

Yearly

String

JJJJ

2021

2021

Financial year

String

JJJJ-JJJJ

2021-2022

Financial year 2021/22

Creating periods for import via Excel can be a bit tedious. To make your life a little easier, we have provided the most common periods for you to simply copy from an Excel file. The file offers templates for weekly, monthly, and quarterly periods for the years 2020 to 2030.


Import Notes

Update via import and "0" vs. "empty"

Falcon does not take empty cells into account during import. This has the advantage that you do not always have to re-import past effects if you regularly update data via the import. If you really want to set values to "zero", you can pass "0" in the import file.

Scaling of effects

The scaling of the effects in Falcon (e.g. in thousands (k) or millions (m)) determines what is entered during the import and is thus analogous to the handling of Falcon itself. Ensure that - if, for example, "k€" was selected as the scaling in Falcon - you also directly track "in thousands" in the import file.

Column and Excel spreadsheets

Falcon searches import files dynamically. You can therefore create multiple Excel spreadsheets with multiple measures. The columns can also be stored in any order. You can even list additional columns in the import file. Falcon skips everything that does not belong to the import.


Impact of permissions

The permission determines if Plan and or Actual values can be imported. So, for example, a user with only write permissions can perform an import, but in this case, only ACTUAL values and no PLAN values are transferred.


Errors & Limits

Falcon allows you to import effects with file sizes of up to 10 MB in one go. Furthermore, the import is limited to 5,000 rows per Excel spreadsheet. No data is imported if errors are detected during the import - e.g., in the file structure. Falcon automatically sends an error report via mail showing you why the import could not be performed.

Common errors

  • References to other files and sheets: Although the import allows Excel calculations (such as B1=A1+A2), Falcon excludes references to other files for security reasons. In addition, references to other sheets within the same file (e.g. A1=Table1!A1) lead to a cancellation of the import.

  • Periods incorrectly formatted: Only periods defined exactly according to the template and as a string can be recognized by Falcon. Read how the periods must be formatted here.

  • Missing ID(s): Falcon can only fill rows whose position IDs and measure IDs are stored in the import file.

  • Different scaling: Make sure that - if e.g. "€k" was chosen as scaling in Falcon - you also directly track thousands of values in the import file.

  • Empty rows and missing identification columns: Falcon assumes a consecutive array of the identification columns (Measure-ID, Position-ID, and Type). Hence, structuring your file with blank rows does not work.


Read also our best practice resource on the topic of effects:


For more information on effects, click here.

Did this answer your question?