What are models?

Models are configurable objects that combine data queries with spreadsheet-like templates, enabling you to build advanced reporting and interactive planning models. You can give each model a name, define the template, create formulas and logic, add queries, and set user permissions.

Once created, you can run models as often as you want. XLReporting will always pull the latest data into your templates.

You can also watch the tutorial video.

When you sign up, your tenant already has a number of predefined models, aimed at financial reporting. They contain example data of a fictitious company. You don't have to start from scratch, you have working examples which you can start with, and you can add or change models at any point in time.

Some common examples of models are:

  • Management dashboard
  • Annual budget form
  • Monthly reforecasting form
  • Sales planning form

Unlike spreadsheets, XLReporting models enforce proper separation between logic and data. When creating models, you should not enter data into a model, but use queries instead.

Types of models

Models are typically used for 2 different purposes:

  • Reporting - build your own custom reports. You can combine very diverse types of data into one model, apply your own format, add formulas, functions, and calculations, and integrate charts, icons, links, and images in your model (watch the tutorial video).
  • Planning - build interactive planning models. You can pull data into your model, define cell editors, and allow users to enter data into the model in designated cells. You can apply formulas, functions, range filters, and calculations, and save the results back into data sets (watch the tutorial video).

Create a model

You can create a model in two ways (watch the tutorial video):

  • Click on Define - New in the sidebar menu.
  • Click on the Actions - Create new button of an existing model. This also enables you to make a copy of an existing model.

Either way, the rest of the process is the same, and you can enter a name for your new model, set user permissions for it, and define its sheets and queries:

screenshot define models

When you create a model, you should focus on the template, don't enter real data. You can integrate data through queries, which we'll explain below. The above example -with just a few rows- is a fully functional model.

You can use the toolbar to populate and format the cells, create formulas, set named ranges and conditional formatting - all in the same way as in Excel. You can also insert objects, such as cell editors, named ranges, sparklines, images, web links etc. XLReporting supports all common spreadsheet functionality. You can create multiple sheets if needed.


You can define the settings for the model via these fields:

  • Name - enter a name. This must be unique within all your models.
  • Group - select how this model is to be shown in the menu navigation.
  • Active/locked - activate or lock a model. When locked, the model can not be used.
  • User roles - select one or multiple user role(s) to restrict access to this model. If you leave this blank, all users have access.
  • Import batch - combine other imports into a batch together with the import queries of this model.
  • Sort - define an (optional) sort order (1-9999) that determines where this model is displayed in the menu. If you leave this blank, the model is ordered alphabetically.
  • Description - enter an (optional) description to explain the use of this model to users. The text can contain basic html tags to format your text (e.g. <br> for a next line, <b> for bold text). The text can also contain functions to include dynamic information or images in the text.
  • Script - create a script to process query data before it is being inserted into the model. This option is for advanced use, and only visible if your user role has the relevant permissions. Read more about scripts.


Models can contain multiple sheets. Each sheet can contain its own content and layout. You can add sheets by clicking on the + icon. You can rename or delete a sheet by clicking on the arrow behind the sheet name. You can also re-arrange the order of sheets by simply dragging them.

If you prefix a sheet name with an underscore (e.g. _test), that sheet will be hidden in Run models. This is useful for sheets that are used for calculations or data processing but which you don't want to show to the user when running the model.


XLReporting has a powerful built-in spreadsheet, fully compatible with Microsoft Excel, in which you can build your models. You will find familiar tasks, such as sheets, columns, rows, cells, styling, functions, and a toolbar. You can create models in the same way you would build spreadsheets, with one major difference: models only contain logic and layout, they do not contain data. The data is retrieved in realtime through queries and functions.

The toolbar gives you access to all common tasks. Read more about the toolbar.

screenshot define models toolbar


Queries enable you to define how data sets will be integrated into your model. A model can contain multiple queries. During Run model, all its queries are simultaneously executed against the XLReporting database and the resulting realtime data is inserted into the model.

You can define queries by clicking on the Define button:

screenshot define models queries

This opens a dropdown menu with further options:

  • Add a new query - create a new query.
  • Edit this query - edit the definition of the currently selected query.
  • Delete this query - delete the currently selected query.
  • Hide the preview - hide the preview with query results.

When you add a new query, or edit an existing query, the first step is to choose the type of query and determine the name and settings for that query:

screenshot define models queries add

You can choose between 3 types of queries:

  • Report - read data from your data sets, and insert the entire formatted report into a designated cell range in your model.
  • Data list - read data from your data sets into memory, which enables you to use cell functions to insert data into individual cells in your model.
  • Import - read cell ranges in your model and import the information into your data sets.

If you select Report or Data list, you need to select the source data set: this is the primary data set that you want to retrieve information from. All its linked data sets will be automatically included, and you can create a report in exactly the same manner as Define reports, including converting the data, filtering the data, and setting the report options and fields position.

If you select Import, you need to select the target data set: this is the data set into which you want to import the data from your model. You can create the column mapping in the exactly the same manner as Define imports, including mapping the columns, converting the data, filtering the data, and the settings for inserting or replacing data.

In Options when running the model you can select a number of features:

  • Insert data rows - should the data be placed in dynamically inserted rows, or should the data overwrite the existing rows? This choice depends on the design of your model.
  • Insert data columns - should the data be placed in dynamically inserted columns, or should the data overwrite the existing columns? This choice depends on the design of your model.
  • Repeat grouped values - this is useful if you want to show values for every report column and row (as opposed to the normal report mode which leaves grouped row fields blank, rather than repeat them).
  • Subtotalise adjacent columns - this is useful if you want subtotals to be automatically applied to columns adjacent to the query range. The subtotals will be applied based on the grouping of the rows fields in the query.
  • Show the query description - choose whether the query description will be shown when running the model.

Once you completed the query definition, a special function will be inserted into the current cell: =QUERY(ID, range), where ID is the query number, and range is the cell range into which the query data will be inserted. The function shows the description of the query.

After every change, the preview of the query results is automatically refreshed, which helps to integrate the query into your model.


The cell that contains the =QUERY(ID, range) function indicates where the query data will be dynamically inserted during Run model:

screenshot define models queries insert

The 3 rows below the placeholder are templates for the actual query data:

  • Headers - the query column headers will be placed on this row.
  • Data rows - the query rows with data. Dependent on the options that you selected:
    • the data will be placed into dynamically inserted rows (✭) in your model, or:
    • the data will be copied over the existing rows.
  • Totals row - the query report totals will be placed on this row.

✭ Notes: The default setting is to Insert rows, enabling you to place additional content in your model underneath the query. Everything will be shifted down when the data rows are inserted, and all formula references will be adjusted accordingly. Cell values on columns adjacent to the query range (i.e. to the left and to the right of the query) will be copied down.

You can set the cell styles (i.e. font, size, cell format, colors, borders etc.) for each of the 3 template rows. If left blank, default cell styles will be applied.

During Run model, realtime data will be inserted and the above template produces the following result:

screenshot define models analyze


You can use functions to pull selected data from report or data queries into individual cells. Unlike report queries, which insert an entire formatted report into a range of cells in the model, functions enable you to insert a single value or an aggregate total (e.g. a sum or count) into one cell. You can create as many functions as you want, to populate multiple cells with varied data:

screenshot define models queries functions

The example in this screenshot retrieves the sum of column 4 of query ID 1 for all rows where column 2 = "Revenue"

There is a collection of query functions that you can choose from. All query functions require the same parameters between brackets:

  • The 1st parameter is the value or cell reference that you want lookup in the query data.
  • The 2nd parameter is the ID of a report or data query. You can define queries within your model, and once defined the ID of a query is shown in the dropdown list in the query preview.
  • The 3rd and 4th parameters are optional: By default, all functions assume that column 1 in the query data contains the key value, and that column 2 contains the values that you want to retrieve. You only need to give the column numbers for the values and key as a parameter when different from these defaults.

Cell objects

Cell objects are components that you can insert into a model to create advanced functionality in a model.

To add cell objects, you need to select a cell or range of cells, and click one of these buttons in the toolbar:

screenshot define models objects

You can choose from various types of objects:

  • Icons and images - add icons or external images into your model.
  • Sparklines and charts - add sparklines (mini-charts) into a cell, or add embedded charts to your model. Sparklines and charts visualize a given cell range in your model. This cell range can be populated by a query, by data entry, or by calculations.
  • Links - add navigation links to other objects (e.g. for drilldown into another report or model) or to external documentation.
  • Cell editor - create editable cells to make your model interactive (e.g. planning models).
  • Row actions - buttons to insert and delete rows (use this to build planning models).
  • Comment - add comments to cell, which will popup when the user hovers over the cell.

Once you click the toolbar icon, a popup window will guide you through the process of defining the object.

Planning models

By default, models are read-only in Run model (i.e. all cells will be locked and filters are inactive).

But you can also create planning models that allow users to enter and edit information into the model during Run model. You can create these type of models in 2 or more steps:

  1. Add cell editors in cells.
  2. Add row actions in cells (optional).
  3. Add planners in cells (optional).
  4. Add Import queries to the model.

Cell editors

Cell editors are definitions that you can insert in a cell (or in a cell range) to make a cell editable (remember: by default, all cells are locked) and define both the type of cell value and the method by which users will be able to enter or select cell values.

To add a cell editor, you need to select a cell or range of cells, click the relevant button in the Insert section of the toolbar, and select the desired editor:

screenshot define models editors

You can choose from 9 types of editors:

  • Cell input (text) - allow the user to enter any text.
  • Cell input (number) - allow the user to enter numbers only.
  • Dropdown (list) - shows a dropdown, with the list of values referring to a cell range or a static list of values.
  • Dropdown (query) - shows a dropdown, with the list of values sourced from a query on the database. By default, the user can only select a value from the query results, but you can optionally allow the user to enter new values by enabling the option Add new.
  • Dropdown (planner) - shows a dropdown, with a list of configurable planners.
  • Popup (comment) - shows a popup into which the user can enter long text comment.
  • Popup (table) - shows a popup table into which the user can enter multiple rows with 2 columns (text and value), for example to enter a specification.
  • Date picker - shows a dropdown calendar from which the user can select a date.
  • Checkbox - shows a checkbox (use this in combination with the Yes/No cell format).

When you add a cell editor in a cell or range of cells, those cells are unlocked, and the user can enter or edit data in the model (and validated by the selected editor) during Run model.


Planners are configurable patterns that can be used to distribute amounts across a range of cells (for example, to apply a seasonal revenue pattern to a series of financial periods).

Adding planners to a model requires 2 steps:

  1. Create one or more Cell editors (Dropdown planner) - you can define multiple planners in each cell editor. A planner consists of a name and a numerical pattern.
  2. Enter one ore more PLANNER functions in cells, to populate cells with the required result for each index in the pattern.

The below example defines 4 patterns for a cell editor: monthly, quarterly, every half year, and a custom pattern:

screenshot define models editors planners

The absolute values of the numeric patterns are irrelevant, what matters is each relative value as a proportion of the sum of all values. You can define as many indices in the patterns as you need.

You can also use one of the below aliases for common patterns:

  • @month - every month (1,1,1,1,1,1,1,1,1,1,1,1)
  • @quarter - every quarter (0,0,1,0,0,1,0,0,1,0,0,1)
  • @soquarter - start of every quarter (1,0,0,1,0,0,1,0,0,1,0,0)
  • @halfyear - every half year (0,0,0,0,0,1,0,0,0,0,0,1)
  • @sohalfyear - start of every half year (1,0,0,0,0,0,1,0,0,0,0,0)
  • @year - every year (0,0,0,0,0,0,0,0,0,0,0,1)
  • @soyear - start of every year (1,0,0,0,0,0,0,0,0,0,0,0)
  • @period445 - based on 4-4-5 weeks (4,4,5,4,4,5,4,4,5,4,4,5)

In addition to defined static planners, you can also refer to a data query. Your data query can include multiple rows, with each row being treated as a separate planner. The first column on every row needs to contain the planner name, and the other columns need to contain the numeric patterns.

By default, the user can only select of the predefined patterns, but you can optionally allow the user to manually enter custom patterns on every row by enabling the option Add new. When selecting the option Custom the user can manually enter the pattern:

screenshot define models editors planners

The PLANNER function returns a proportion of data according to the selected planner and the selected index. The returned value is calculated as follows:

data * value of given planner index / sum of all planner values

If the given index does not exist in the planner, the function will use the given ratio (which can be a cell reference, a formula, or a given value) and will return the result of data * ratio.

If neither the index or a ratio exists, the function will return 0 (zero).

PLANNER(data, planner, index, ratio)

PLANNER(1000, "Months", 6) = 83.33 (1000 * 1 / 12
PLANNER(1000, "Weeks445", 6) = 96.15 (1000 * 5 / 52)
PLANNER(1000, "Summmer", 6) = 111.11 (1000 * 4 / 36)
PLANNER(1000, "", 0, B3/C3) = 200.00 (1000 * 1/10, assuming B3=1 and C3=10)

Dropdown table

Using a dropbox table you can enable end users to fill in multiple rows with 2 columns (text and value), for example to enter a specification.

The result is stored as text into one single cell on the current row, and can therefore be saved to a data set using an import query, and retrieved into the model again using a query or DGET function. You can use the function UNWRAP to retrieve the total value of the table (just a reference to the cell without further parameters), or a selected row (with the row number as an additional parameter), as follows:

screenshot define models dropdown table

Row actions

Row actions are are configurable buttons that you can insert in a cell in a model to allow rows to be inserted, copied, or deleted.

To add row actions, you need to select a cell or range of cells, click the relevant button in the Insert section of the toolbar, and select the desired action:

screenshot define models row actions

This option enables you to define precisely where rows can be inserted, copied, or deleted in the model during Run model. Typically you would only enable this in the data entry section of your model.

Once created, you can call the row actions by clicking on one of the icons. Row actions are only active in Run models.

Import queries

By creating an import query in your model, you can save information back into a data set.

For every import query, you can select how new data will be imported into the data set:

  • Add to - add new data to the existing content of the data set.
  • Overwrite - overwrite the entire existing content of the data set.
  • Replace in - selectively replace existing content of the data set. For example, anytime you import a certain financial period, you might want to overwrite the previous content for that same period. If you select this option, you also need to indicate which column(s) will trigger the replacement. Read more here.
  • Update in - update the given columns in existing rows in the data set. This option will only update rows that already exist in the data set, and ignore any other data in the import source. The target data set must have a defined Key column, because that is used to determine whether a given row already exists or not.
  • Upsert in - update the given columns in existing rows in the data set, and insert rows that don't yet exist in the data set. The target data set must have a defined Key column, because that is used to determine whether a given row already exists or not.
  • Delete from - selectively delete existing content from the data set. Data that matches your data source will be deleted. No new data will be imported. If you select this option, you also need to indicate which column(s) will trigger the deletion. Read more here.

Once you have added an import query to a model, a Save button will automatically be added to the Run models screen, and the user can enter and edit data (in cells where you have created the above cell editors) and click the Save button when done.

XLReporting expects the row below your query to contain columns headers, and you can specify how many rows of data you want to import. If you combine import queries with report queries, the number of rows will be automatically expanded based on the results of the report query.

For each column in your target data set, you can either select the relevant column in your model, a static value, or a function. You can also transpose columns into rows, convert the data, and filter the data. It works in the same way as Define imports.

When saving, XLReporting will try to process every row it encounters, up until the number of rows you have specified.

The option Keep silent suppresses non-critical notifications during the save process. Only real errors will be shown. Regardless of this setting, all results will always be shown in Actions - View saved results when running the model.

When defining models, you may often lay out information across columns, for example period-by-period amounts. The option Transpose data will transpose the selected column data into rows and you can use the 2 special columns TRANSPOSE in the column mapping to your data set. By default, the transpose operation will skip empty values and zeros. If you want to transpose all columns onto all rows even if they are empty, you can do so by selecting the Also include empty option.

The option When empty enables you to define the action when a field has no source value: either skip the entire row, abort the entire import (nothing will be imported), or repeat the value from the previous row (which is useful if your import data is grouped).

screenshot define models queries save

Define import batch

Click on the Import batch field to combine multiple imports into a batch which are then run as one single action together with the import queries of this model.

screenshot define imports batch

You can insert or delete imports at any time, and re-order them, using the dropdown menu in the last column.

By default, imports will be started in the order that you define them, and processed in parallel (i.e. near simultaneously). This gives the fastest performance in general, but if you have certain imports that require other imports to be completed first, you can set Wait in line. When this option is set for an import, it will only be started and processed once all its predecessor imports have completed.


When defining a model, you can use the Save and Actions buttons in the right-top of the screen:

screenshot define models actions

These buttons enable you to do the following:

  • Save - save your changes
  • Actions - open a dropdown menu with further options:
    • Create a new model (or copy one)
    • Delete this model
    • Import from file
    • Export data or print
    • Review this model
    • Mark this version
    • Add to dashboard
    • Run this model

Review this model

Click on Actions - Review this model to review a number of aspects of this model and its currently selected query:

  • Data model - shows a diagram with all linked data sets. This is derived from columns that are set to data type Linked values.
  • Linked objects - shows all linked imports, reports, and models that are using this data set, and the total number of data rows in this data set.
  • Linked data - shows the results of checks on the Key values and Linked values that are used to link data sets. Because linked values need to correspond with key values, this integrity check is important.
  • Defined fields - shows a summary of all defined columns and data types.
  • Recent activity - show all recent user activity relating to this data set.

You can also watch the tutorial video.

screenshot define models datasets review

Add to dashboard

A dashboard is a personal page with your own favorite reports and models. You can create multiple dashboards, and each dashboard can contain multiple reports or models.

Click on Actions - Add to dashboard to add this model to either a new dashboard, or to a new dashboard (watch the tutorial video):

screenshot dashboard models edit

Recommended reading:
Back to top | Data sets | Videos