# Welcome to Alpha Information for those participating in the Alpha trial Thank you for joining us in testing our first product, Models. We're hoping to use the Alpha rollout to get quality feedback on features, bugs, usability and, in general, your thoughts about the product. To get you started, here are a few useful steps: 1. See our [**installation and setup**](/alpha-testing/installation-and-setup) guide if you haven't already installed Models. 2. Read about how to send [**error reports**](/alpha-testing/support-and-help#error-reports) (yep, there might still be some bugs), and how to get [**support**](/alpha-testing/support-and-help#support) from the team 3. Check out our extensive documentation, beginning with the [**Start Here**](/start-here/what-is-models) section ## Feedback All feedback and comments are welcome and highly valued, so please feel free to email us at [**alpha@taglo.io**](mailto:alpha@taglo.io) to start a conversation. For error reports and help solving specific issues, please raise a support ticket as explained [**here**](/alpha-testing/support-and-help). # Installation and Setup How to get Models up and running ## Downloading Models You'll receive a link to download Models in the email that you received when you signed up for the Alpha Trial. {% hint style="info" %} If you do not have the download link, contact us at [**alpha@taglo.io**](mailto:alpha@taglo.io) {% endhint %} Follow your browser's instructions to open the download link. ## Installation {% hint style="warning" %} Models is currently a Windows-only application {% endhint %} Once you have clicked on the download link, you will be presented with an installation screen, as shown in the screenshot below.

A screenshot of a dialog asking users whether they want to install the Models application — Models Installation Screen

Simply click **Install** to run the process. You will then see a screen as below - on completion, Models will be installed to your computer.

A screenshot of the Models in-progress installation window — Models Installation in Progress screen

## Setup When you install Models for the first time, a data storage folder will be created in *\[CurrentUser]/AppData/Roaming/Taglo*. We recommend that you continue to use this folder for storage, though you can change storage folder at any time - see [**here**](/using-taglo-software/data-storage) for more information. ## Updates/Pinning to taskbar Models will automatically check for and install updates each time it runs. {% hint style="warning" %} As Models is currently Alpha software, we cannot support out of date versions of the application, so ensuring that your software is up to date is critical. {% endhint %} If you want to pin Models to the Windows taskbar, you should only do so from the Windows start menu, as shown in the image below. If you pin Models to the taskbar from a running instance of the app, you won't receive automatic updates and you will see a warning each time you run the software.

Screenshot showing the Windows start menu, with "Models" searched for. The Models app is display with a list of options, including "Pin to taskbar" — Pinning Models to the taskbar

# Support and Help How to send error reports and get help with Models ## Support You can email [**support@taglo.io**](mailto:support@taglo.io) to create a support ticket, and we will get back to you as soon as we can. If you are reporting a bug, please include as much relevant information as you can. ## Error reports If you encounter a crash while using Models, an email should automatically be created for you containing diagnostic information relating to the crash, as in the screenshot below. Simply send this email to [**support@taglo.io**](mailto:support@taglo.io) to create a ticket.

An Outlook email creation dialog, showing a support email that has been automatically created by Models in response to an error. The email contains a code trace from the software with details of the error. — Error report email from Models

# Terms and Licence How you can use our software ## Disclaimer {% hint style="warning" %} Except as expressly set forth in this agreement, to the maximum extent permitted by applicable law (a) Models ("the product") and any third-party products are provided and distributed on an “as-is” and “as-available” basis without warranties of any kind whatsoever, (b) Taglo and its suppliers do not make any other warranty of any kind, whether express, implied, statutory, or otherwise, and specifically disclaim any and all other warranties, including without limitation (i) the implied warranties of merchantability, fitness for a particular purpose, non-infringement, satisfactory quality and quiet enjoyment, and (ii) warranties arising out of any course of dealing or usage of trade, (c) Taglo and its suppliers are not responsible or liable for the deletion of or failure to store any content, data and other communications maintained or transmitted through use of the product, and (d) Taglo and its suppliers do not warrant that the products or third-party products will be uninterrupted, secure, error-free, or free of harmful components. {% endhint %} ## Licence Agreement ### End-User License Agreement (EULA) of Models This End-User License Agreement ("EULA") is a legal agreement between you and Taglo Ltd. This EULA agreement governs your acquisition and use of our Models software ("Software") directly from Taglo Ltd or indirectly through a Taglo Ltd authorized reseller or distributor (a "Reseller"). Please read this EULA agreement carefully before completing the installation process and using the Models software. It provides a license to use the Models software and contains warranty information and liability disclaimers. If you register for a free trial of the Models software, this EULA agreement will also govern that trial. By clicking "accept" or installing and/or using the Models software, you are confirming your acceptance of the Software and agreeing to become bound by the terms of this EULA agreement. If you are entering into this EULA agreement on behalf of a company or other legal entity, you represent that you have the authority to bind such entity and its affiliates to these terms and conditions. If you do not have such authority or if you do not agree with the terms and conditions of this EULA agreement, do not install or use the Software, and you must not accept this EULA agreement. This EULA agreement shall apply only to the Software supplied by Taglo Ltd herewith regardless of whether other software is referred to or described herein. The terms also apply to any Taglo Ltd updates, supplements, Internet-based services, and support services for the Software, unless other terms accompany those items on delivery. If so, those terms apply. #### License Grant Taglo Ltd hereby grants you a personal, non-transferable, non-exclusive licence to use the Models software on your devices in accordance with the terms of this EULA agreement. You are permitted to load the Models software (for example a PC, laptop, mobile or tablet) under your control. You are responsible for ensuring your device meets the minimum requirements of the Models software. You are not permitted to: * Edit, alter, modify, adapt, translate or otherwise change the whole or any part of the Software nor permit the whole or any part of the Software to be combined with or become incorporated in any other software, nor decompile, disassemble or reverse engineer the Software or attempt to do any such things * Reproduce, copy, distribute, resell or otherwise use the Software for any commercial purpose * Allow any third party to use the Software on behalf of or for the benefit of any third party * Use the Software in any way which breaches any applicable local, national or international law * Use the Software for any purpose that Taglo Ltd considers is a breach of this EULA agreement #### Intellectual Property and Ownership Taglo Ltd shall at all times retain ownership of the Software as originally downloaded by you and all subsequent downloads of the Software by you. The Software (and the copyright, and other intellectual property rights of whatever nature in the Software, including any modifications made thereto) are and shall remain the property of Taglo Ltd. Taglo Ltd reserves the right to grant licences to use the Software to third parties. #### Termination This EULA agreement is effective from the date you first use the Software and shall continue until terminated. You may terminate it at any time upon written notice to Taglo Ltd. It will also terminate immediately if you fail to comply with any term of this EULA agreement. Upon such termination, the licenses granted by this EULA agreement will immediately terminate and you agree to stop all access and use of the Software. The provisions that by their nature continue and survive will survive any termination of this EULA agreement. #### Governing Law This EULA agreement, and any dispute arising out of or in connection with this EULA agreement, shall be governed by and construed in accordance with the laws of the United Kingdom of Great Britain and Northern Ireland. # What is Models? A beginner's overview of the Models app **Models** is an app designed for working with timeseries-based calculations. It's an incredibly powerful tool, and can be used in countless situations, but typically we use it for tasks such as: * Creating financial forecasts and budgets * Building business plans * Modelling market trends Models works as a standalone application, in which you can create your models, and view and flex outputs through compelling dashboards, but it will also generate fully-working, formatted Excel spreadsheets that you can share with colleagues and clients. # Quick start Things to do before you dive into Models 1. Watch our [**2 minute Models overview video**](/start-here/tutorials#id-2-minute-models-overview), so that you quickly get an idea of what can be done in Models. 2. Read about [**The Taglo Interface**](/using-taglo-software/the-taglo-interface). It will save you a lot of time down the road. 3. Watch our [**Introduction to Models tutorial**](/start-here/tutorials#introduction-to-models-by-taglo). We walk through: * Creating a Model * Generating a revenue forecast * Applying multiple Dimensions * Visualising your Model in a Dashboard * Setting up a Layout and generating Excel Have fun! # Tutorials We have created a range of video tutorials to help you get started {% hint style="info" %} We will be adding tutorials throughout the Alpha trial rollout. If you are subscribed to our newsletter, you will receive notifications when a new tutorial is added. {% endhint %} Find all of our tutorials on [**our YouTube channel**](https://www.youtube.com/@tagloltd/featured) at any time. ## 2-minute Models overview {% embed url="" %} Quick overview of Models features {% endembed %} ## Introductory tutorials ### Introduction to Models by Taglo {% embed url="" %} 30 minute introductory tutorial {% endembed %} # The Taglo Interface How to navigate and complete tasks in Taglo software Taglo software is designed to perform both simple and complex tasks, while handling both small and large amounts of data. Our UI is designed to: 1. Cope with any scenario you might throw at it (within reason!) 2. Allow you to stay within your current train of thought at all times without having to constantly switch between interfaces to complete related tasks. You can find lots of real-life examples of how the UI works in our [**Tutorials**](/start-here/tutorials) section. The rest of this section goes through the key things you need to know to become a Taglo UI expert. # Navigating in Models How to navigate between different functions in Models ## Models tabs Models is structured as a number of "applets" sitting inside the main Models application. You can navigate between these applets by using the navigation bar which is always visible at the bottom of the application. Any Models that you open for editing can be found in the [**Model Editor**](/models/model-editor) tab, which is where you will spend most of your time.

Screenshot showing the Home tab of Models. The navigation bar, at the bottom of the application, is highlighted. — The Models Home tab

# List Views How we display lists of things that you create ## Overview In Taglo software, you'll be spending much of your time creating and editing items that belong in lists. Examples of these from Models are: * A list of [**Variables**](/variables/variable-basics) * A list of [**Assumptions**](/assumptions/introduction-to-assumptions) * A list of [**Sheets**](/layout/sheets) in your [**Layout**](/layout/generating-excel) * A list of [**Calculation Parts**](/calculations/calculation-parts) in a [**Calculation**](/calculations/introduction-to-calculations) Given that you'll be spending so much time working in lists, we provide a consistent way of viewing, searching, and managing the items in these lists. ## View types The default type of view for a list of items will vary with the item. There are 2 main views that you will usually see, Basic and Tree. You may sometimes also see a Grid view.


Basic
Tree
Grid

## Switching views Taglo allows you to view most lists in multiple ways. For instance, you may want to view an item that is presented in a Tree View as a Basic List, or in a Grid View. You'll find the Switch View control (shown below) at the bottom of all lists that have multiple views enabled. Simply click on one of the buttons to select a view.

A list of Variables, shown in a Tree View, with the Switch View control highlighted. — The Switch View control

{% hint style="info" %} If you are currently working in a list, you can also switch between views with the keyboard shortcut **`Ctrl+Number`***.* e.g. To switch to the second available view, press **`Ctrl+2`** {% endhint %} # Adding Items How to add new items to a list Most lists allow you to add new items at any time. There are 3 ways to add an item to the list: ## 1. New item button If adding items is enabled, you will always see a Screenshot of the "New item" button

button in the top right of the list. Click this button to bring up an "Add new item" dialog. ## 2. Keyboard shortcut If you currently have an item in a list selected, or your cursor is in one of the Search boxes of a list, you will be able to bring up the "Add new item" dialog by pressing `Ctrl+N`. ## 3. From an empty list If a list is empty, or your Search has returned no results, you will see a prompt similar to the one below. Click on this button to bring up the "Add new item" dialog.

A screenshot of the prompt shown when no search results are returned — The empty list prompt

# Deleting Items How to delete items ## Overview Most items in Models can be deleted. If deletion is available, you will be able to delete an item by selecting it in the list, and pressing the `DEL` key, or by using the [**Delete button in the item Preview**](/using-taglo-software/the-taglo-interface/previewing-and-editing#preview-actions). ## Preventing deletion of referenced items Taglo automatically stops you from deleting items that are referenced elsewhere in your work. If you try to delete an item that is referenced elsewhere, you will see a screen like the below. This view shows you where the item (in this case a [**Tag**](/tags/introduction-to-tags)) is referenced, so that you can decide whether to remove those references and delete the item, or to keep the item. {% hint style="info" %} Note, for some items within a Model, such as a [**Variable**](/variables/variable-basics) or [**Assumption**](/assumptions/introduction-to-assumptions), you can delete the items without seeing the warning screen, even if it is referenced. In this case, Models will automatically remove references so that your Model does not break. You can always [**undo**](/using-taglo-software/the-taglo-interface/save-undo-redo) a deletion if you did not mean to do remove the item. {% endhint %}

# Searching and Filtering How to find things in lists Your lists might get big, so we provide several ways to sort and find your items. 1. [**Searching with Tags**](#searching-with-tags) 2. [**Searching with Text**](#searching-with-text) 3. [**Filtering**](#filtering) 4. [**Sorting**](#sorting) Read on to understand each of these. ## Searching with Tags {% hint style="info" %} Tags are central to how Taglo products work - for more information about Tags, look at the [**dedicated Tags section**](/tags/introduction-to-tags) of this documentation. {% endhint %} Many of the items that will be presented to you in list form will either be tagged directly or related to Tags in some other way. To filter by Tags, just type in the Tag search box and select all Tags that you want to include in your search. You will be presented with all results that are directly tagged with the selected Tags, or are tagged with descendants of the selected Tags. > For instance, if you have an item that is tagged with `Spain`, it will appear in results for the Tag `Spain`, but it will also appear in results for the Tag `Europe`, because `Europe` is a parent of `Spain`.

GIF showing a list of Variables being filtered by Tags. The user first selects the "Region" tag, and then the "GBP" tag. Each time a tag is selected, the list is refined to show only relevant items. — Filtering a list using Tags

## Searching with Text To search by text, just type in the search box. To search for multiple terms, select the search item from the dropdown list to "lock-in" the search term, as shown in the GIF below. You can add as many search terms as you want, and clear them at any point using the Clear

button. {% hint style="info" %} Use the **`Up`** and **`Down`** arrow keys to move between the search box and items in the list {% endhint %}

GIF showing a list of Variables being filtered using text search. The user enters the word "Revenues" into the search box, and selects the search item from the drop down, which filters the list to only Variables containing the word "Revenue". The user then types in the search box again, with the word "region". This further filters the list. — Filtering a list using Text Search

## Filtering by Properties Most lists allow you to filter items by a property of the item. To use, simply click on the filter

icon, select the property you wish to filter by, and the desired value of the property. The example below shows the user filtering for Variables that have not yet been added to the [**Layout**](/layout/generating-excel).

GIF showing a list of Variables being filtered by properties. The user presses the Filter icon, which brings up a list of properties. They choose the "Is in Layout" property, and then the value "False". This filters the list to only Variables that are not yet in the Layout. — Filtering a list using Properties

## Sorting by Properties Most lists allow you to sort items by a property of the item. To use, simply click on the sort

icon, select the property you wish to sort by, and select the sort order (ascending/descending). You can select multiple properties to sort by, and rearrange them by dragging and dropping.

GIF showing a list of Variables being sorted by property. The user presses the sort (A to Z) button, which brings up a list of properties to sort by. They then select the "Name" property, followed by the "Unit" property. They then change the order of the sorters and the direction of the sort. — Sorting a list using Properties

# Previewing and Editing How to view and edit information about items in lists ## Showing and Hiding Previews Most lists in Taglo software follow the same approach to displaying information about their items. Clicking on an item in the list (or anywhere next to the item) will bring up a **preview panel** on the right-hand side of the list. {% hint style="info" %} The only exception to this is when you are selecting an item from a list [**within a Dialog**](/using-taglo-software/the-taglo-interface/using-wizards#selecting-items-in-dialogs), in which case, clicking directly on the item will select the item - you will need to click next to the item to preview it. {% endhint %} Clicking on the close button ( Screenshot of the "Collapse preview" button

Screenshot of the "Collapse preview" button

) in the preview panel will collapse the preview to the right hand side of the list. To reopen the preview, press the open preview button ( Screenshot of the "Expand Preview" button

Screenshot of the "Expand Preview" button

) in the collapsed preview.

GIF showing use of the Preview Panel in a list of Variables. The user selects several Variables in turn, which details of each Variable being shown in the Preview Panel, which appears on the right hand side of the interface. The user then closes the preview panel and reopens it. — Showing and collapsing the Preview Panel

## Preview Actions You will also usually see a standard set of buttons at the top of the preview Screenshot of the Edit, Copy and Delete buttons

that will allow you to perform common actions: 1. **Edit** the item - clicking here will open an Edit [**Wizard** ](/using-taglo-software/the-taglo-interface/using-wizards)\[or use `Ctrl+E` keyboard shortcut] 2. **Copy** the item - clicking here will create a duplicate item \[or use `Ctrl+D` keyboard shortcut] 3. **Delete** the item - \[or press `Del` key with one or more items selected in the list] Edit, Copy and Delete controls are also shown on the collapsed preview. {% hint style="info" %} In some lists, you may be able to edit multiple items simultaneously, and the preview panel will show a different view for single and multiple selections {% endhint %} # Using Wizards How to use Taglo wizards ## Overview Many actions in Taglo software are performed through a wizard-like dialog. We try to provide non-wizard shortcuts for the most common tasks, but you will still find yourself using wizards throughout your work. Our philosophy behind these wizards is to provide a way for the user to enter complex and situation-dependent information, without creating barriers to the flow of the user's thought process. {% hint style="success" %} In Taglo, you should (almost) never see a pop-up window that stops you performing your next task! {% endhint %} ## Navigating Wizards A Taglo wizard is simply a series of steps that need to be completed in order to perform an action or create/edit an item. Depending on the complexity of each step, it may be presented in a vertical list on the same page with other steps, or on its own page of the wizard.


Wizard Page with Multiple Steps
Wizard Page with Single Step

Steps will be shown and hidden depending on options you select as you progress through the wizard. If any data you have entered is invalid, you will be unable to navigate to the next page of the wizard or finish the wizard. You can always cancel changes you've made by clicking the Cancel Screenshot of the "Cancel wizard" button

Screenshot of the "Cancel wizard" button

button at the top-right of the wizard. {% hint style="info" %} On a page with multiple steps, you can quickly access different steps by pressing `Ctrl+[Number key]` where `[Number key]` is the number of the step as it appears on the page. For example, to quickly jump to the third step on the page, you'd press `Ctrl+3`. See [here](/using-taglo-software/the-taglo-interface/keyboard-shortcuts#dialog-shortcuts) for a full list of keyboard shortcuts that you can use in dialogs. {% endhint %} {% hint style="info" %} If the **Finish** button is enabled at any point (as in the image below), you can successfully exit the dialog by clicking **Finish**, even if you haven't entered information into all steps.

{% endhint %} ## Selecting Items in Wizards You will often need to select from a list of items when in a wizard. > For instance, you may need to assign one or more tags to the item that you are creating/editing. In this case, you will be presented with a list of tags, using an adaptation of the familiar **List View** that was discussed [**earlier in this section**](/using-taglo-software/the-taglo-interface/list-views). You will be able to use these list views similarly to how you use them in the main interface, including previewing items and creating/editing items. ## Launching new Wizards **List Views** within a wizard behave in the same way as normal list views. That means that if the item you want to select doesn't exist yet, you can create it immediately and then select it. If the item you want to select needs editing, you can edit it right there and then, without having to move to another part of the application first. When you open a new wizard from within a wizard, the new one will appear on top of the old one, with a visual indication that the previous wizard is waiting for you once you have finished. You can keep stacking wizards until you have finished all the tasks you need. {% hint style="success" %} This is how we help you stay within your train of thought. You should never have to worry about the order in which you perform tasks. When you find that an item you need doesn't exist, just open a new wizard and create the item **from wherever you are in the application**, and select it once you're done. {% endhint %} The GIF below shows this workflow in action:

GIF showing a user following a train of thought by stacking dialogs. The user is creating a tag. When it wants to create a relationship from the new tag to another tag, if the other tag does not yet exist, the user can just open a new dialog on top of the old one. The user does this twice, before returning to the original dialog. — The Stacked Wizard workflow

# Save/Undo/Redo How you can undo/redo changes and restore old versions Any time you make a change in Taglo software, the change is saved, so you never have to worry about losing work. {% hint style="info" %} For information about how your data is saved, and how to deal with it manually, see the [**Data Storage**](/using-taglo-software/data-storage) page. {% endhint %} Models includes Undo and Redo functionality, which can be accessed through the Menu bar.

A screenshot showing the Undo/Redo buttons in the Edit menu. — Undo/Redo in Edit menu

You can use the keyboard shortcuts `Alt+E, U` and `Alt+E, R`, from wherever you are in the application to Undo/Redo. Each **Model** also has a [**dedicated file history**](/models/home-tab/version-history) which you can use to return to a specific date/time. # Keyboard Shortcuts A list of common shortcuts ## Application shortcuts General shortcuts:

Shortcut	Action
`Alt` + `e`, `u`	Undo (see Undo/Redo)
`Alt` + `e`, `r`	Redo (see Undo/Redo)

## List shortcuts When working in any [**list of items**](/using-taglo-software/the-taglo-interface/list-views):

Shortcut	Action
`Ctrl` + `n`	Create a new item (opens new item dialog)
`Ctrl` + `[Number]`	Switch view (e.g. `Ctrl` + `2` to switch to second view)

When one or more items in a list are selected:

Shortcut	Action
`Ctrl` + `e`	Edit the currently selected item(s)
`Ctrl` + `d`	Duplicate the currently selected item(s)
`Del`	Delete the currently selected item(s)

## Wizard shortcuts When working in a [**wizard**](/using-taglo-software/the-taglo-interface/using-wizards):

Shortcut	Action
`Alt` + `n`	Go to next page (if available)
`Alt` + `b`	Go to previous page
`Alt` + `i`	Finish and exit (if available) from any page
`Alt` + `[Number]`	Go to sub-step on page (e.g. `Alt` + `2` to go to second step)
`Alt` + `0`	Collapse all sub-steps on page

## Model Editor shortcuts Shortcuts in the [**Model Editor**](/models/model-editor):

Shortcut	Action
`Ctrl` + `q`	Cycle through tabs
`Ctrl` + `Shift` + `q`	Cycle backwards through tabs

# Data Storage How your data is stored and what this means for collaborating with others ## Data Overview Taglo applications currently store data locally on your machine. You can set the location of this data from **File > Change data location**, which will bring up a prompt to choose a folder in which all of your data will be stored. Taglo data is designed to be stored in a single folder, which all applications will access. ## Manipulating and Sharing Data {% hint style="warning" %} Taglo data is stored in human-readable files but should not be manually edited by the user, as this risks corrupting the files. {% endhint %} Taglo stores all of your data in a series of files that make up a local database, making it easy to search and organise your data. As an example, **Tags** are accessible from all Taglo applications, so are not stored in the same files as, say, a **Model**. For your Model to function correctly, the software will need to access both Models and Tags data. This means that you can't simply move and access an individual Models file and expect it to work. Unfortunately, this means that sharing a file via email, like you might be used to in Excel, is not straightforward. (Of course, you can still share non-Taglo outputs, such as the Excel spreadsheets that Models produces). {% hint style="info" %} We would like to enable formal sharing and collaboration tools in Taglo software as the product matures. Until then, if sharing and collaboration is required, we recommend storing data in a shared drive location (e.g. using a file-sharing tool such as OneDrive or Dropbox). Each collaborator should then set their file location to the shared folder. In this model, **ensure** **that collaborators do not work on the same data simultaneously**, which could cause conflicts. You can help avoid conflicts by working in different [**Namespaces**](/using-taglo-software/namespaces). Data from different namespaces are always stored in separate files. {% endhint %} ## Refreshing Data In all Taglo applications, pressing `F5` will reload the data from file - this should only be necessary if you or another user has altered the underlying data simultaneously from another application instance # Namespaces How to use Namespaces to organise data ## Overview of Namespaces Namespaces are how Taglo allows you to organise your data into different "areas". ## Defining Namespaces You can add and edit Namespaces from any list of namespaces, or use the Namespaces applet, accessible from the [navigation bar](/using-taglo-software/the-taglo-interface/navigating-in-models). Give the Namespace a name, and select any other Namespaces that should be referenced by your new Namespace (explained below). ## Namespace References Namespaces can reference other Namespaces. This ensures that the referenced Namespace is always loaded when the referrer is loaded. As an example, you might have a Namespace called **Fruit**, which contains data and Tags about apples, bananas and oranges. You then create a new Namespace called **Recipes** which has data and Tags about all the things you like to cook, some of which contain apples, bananas and oranges. By referencing the Fruit Namespace from the Recipes Namespace, you ensure that when you're working with Recipes, you always have access to the apples, bananas and oranges data. Conversely, you might build a [**Model**](/models/home-tab) to budget for your stamp collection over the next 5 years, so you create that Model in a **Stamp Collection** Namespace. This Namespace does not need to know about Recipes or Fruit, so you don't reference either of those Namespaces, which ensures you don't see irrelevant information when working on your Model. {% hint style="info" %} It's up to you how to manage your Namespaces. Keeping them specific (like the Fruit example above) allows you a lot of flexibility, but means you will end up with a lot of Namespaces to keep track of and manage. Putting everything in a few large Namespaces means you may have less to think about initially, but you will see more irrelevant items when working on a Model. {% endhint %} # Inbuilt data Overview of data that comes built into Models ## Overview Models comes with some data that is always available to you when using the software. This includes: * Some Model templates * Number Formats * Useful Tags You won't be able to edit or delete inbuilt items, though some inbuilt items (like Models) can be copied. Inbuilt data can be easily identified by looking for the padlock icon, as shown in the example below:

A screenshot of a section of the Home Tab, highlighting inbuilt Models as indicated by a locked padlock icon next to each inbuilt Model — Examples of inbuilt Models

## Inbuilt Namespaces You cannot add items to the inbuilt Namespaces. If copying an inbuilt item, you will be asked to choose a Namespace of your own to copy the item to. # Introduction to Tags Understanding key Tag concepts ## Overview **Tags** are fundamental to how Taglo software works. As their name suggests, they can be used for "tagging", helping to categorise and search items, but with some extra layers of power built in: Tags can be linked to other Tags, creating a network that makes both tagging and searching easier and more effective. The relationships between Tags makes them useful in other places too, and they form the basis for other concepts in [**Models**](/models/home-tab), such as [**Units**](/units/introduction-to-units) and [**Dimensions**](/dimensions/introduction-to-dimensions). ## Abstract vs. Concrete Tags can be one of two types: `Abstract` and `Concrete`

Tag type	Description	Example
`Abstract`	Describes a type of object or concept that there can be one or more instances of (e.g., a `city`, a `country`, an `apple variety`, a `Taglo product`, an `emotional state`)
`Concrete`	Describes a specific instance of an object, or a general concept of which there can be only one instance (e.g., `London`, `United Kingdom`, `Granny Smith` , `Models`, `happiness`)

## Tag Relationships Tags can have unlimited parents (and children). There are two types of parent relationships: 1. `Is A`: Links to `Abstract` parents (e.g.,

`Is A`

) 2. `Relates To`: Links to `Concrete` parents (e.g.,

`Relates To`

) {% hint style="info" %} Use the [Tags Applet](/tags/tags-applet) to quickly navigate between Tags and explore relationships {% endhint %} {% hint style="warning" %} There is also an `Is Same As` relationship, which should only be used when duplicate Tags have been created and it would be difficult to remove one of the duplicates. In this case each Tag in the `Is Same As` relationship will inherit all parents of the other. {% endhint %} # Tag Basics How to create and edit a Tag ## Setup step You can create or edit a Tag from any list of Tags in a Taglo application. A dialog will be displayed as shown in the below screenshot.

Screenshot showing the Tag setup wizard. The user has entered a full name and a short name for the Tag. — Setup step of Tag wizard

### Name A Tag name can be any non-blank text. ### Type Choose between `Abstract` and `Concrete` Tag types (see explanation [**here**](https://help.taglo.io/tags/pages/xKXxhPqflNveH4QpWCHU#abstract-vs.-concrete)). This option may not be available in all Tag wizards, dependent on context (sometimes the Tag type will be pre-determined). ### Namespace Each Tag must be assigned to a [**Namespace**](#namespace). ### Short Name Optionally, you can enter a Short Name for your Tag. In some places, this name will be displayed instead of the full name. If left blank, the full name will always be displayed. ## Relationships

Screenshot showing the relationships page of the Tag wizard. The user is creating a Tag for London, and has added an "Is A:" relationship to the "City" tag, and a "Relates to:" relationship to the "UK" tag — Relationships step of Tag wizard

`Is A`, `Relates To`, and `Is Same As` relationships can be edited in the **Relationships** page of the dialog. There are no limits to the number of each relationship type that you select. {% hint style="info" %} Remember, you can create new Tags directly from each of the Relationship steps, so you can create a whole hierarchy of Tags on the fly. {% endhint %} # Tags Applet Overview of the dedicated Tags applet ## Overview

Screenshot showing the Tags applet, with the Tag for "South America" previewed, showing it's child Tags (the counties in South America) — Tags applet

The Tags application can be accessed from the navigation bar in [**Models**](/models/home-tab). The Tags application is simply a display of all Tags in all [**Namespaces**](/using-taglo-software/namespaces). As with other Tag lists, the Tags can be displayed in a hierarchical view (as shown in screenshot above), as well as flat lists of all Tags. {% hint style="info" %} Note that a Tag may appear in multiple locations in the hierarchical view, as Tags can have multiple parents {% endhint %} ## Previews and Navigation In the full preview for a selected Tag you can see both parent and child relationships. Clicking on these parent and child Tags will take you to a preview of that item, and navigate to the Tag in the list. If you are in the hierarchical view, the first instance of the Tag in the list will be shown. Parent relationships can be edited using the **Edit** functionality of the list to open a Tag wizard. Child relationships can be edited by clicking on the specific Edit

buttons in the Preview, which will open a dedicated dialog for editing either the `Concrete` or `Abstract` children. ### Reordering Children Within the Child relationships wizard, children can be reordered by dragging and dropping. ## Direct children filter Tags in the Tags application are searchable by Tags. The results shown depend on whether the **Direct children only** option is selected.

By default, this option is selected, and filtering by a Tag will show only the direct children of that Tag. If this option is deselected, all descendants will be shown. # Advanced Tags Advanced Tag options ## Tag Properties {% hint style="info" %} Applicable to `Abstract` Tags only {% endhint %} Tag Properties can be used to add additional context to `Abstract` Tags in specific situations, primarily for performing complex [**Dimension**](/dimensions/introduction-to-dimensions)-based calculations in [**Models**](/models/home-tab). > Tag Properties are best understood by seeing example use cases, such as using [**repeated Dimensions in a Variable**](/dimensions/dimension-setup#selecting-repeated-dimensions). Tag Properties can be added from the **Advanced** step of the Tag dialog. ## Auto-create Tag Links {% hint style="info" %} Applicable to `Abstract` Tags only {% endhint %} When creating an `Abstract` Tag, you may want to simultaneously create a `Concrete` equivalent, and link it to parents of the Abstract Tag, as demonstrated in the example below ### Auto-create Example ![](https://2847533834-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVy65sax6FVoNo2UTlJ0x%2Fuploads%2F53rRcneqKhrhL0AkJAIN%2Fimage.png?alt=media\&token=c59d058c-b619-4038-8a01-293ba95c0840) Let's say we currently have two Tags, an `Abstract` Tag called `Fruit (a piece of)`, and a `Concrete` parent of `Fruit` called `Fruits`, which represents the general concept of all fruit. Now let's say I want to add a new `Abstract` Tag called `Apple`, which will have `Fruit (a piece of)` as an `Abstract` parent (an Apple is a piece of Fruit). I might simply add the new Tag, with the parent relationship and end up with the below. ![](https://2847533834-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVy65sax6FVoNo2UTlJ0x%2Fuploads%2FV1wRzIuTKqdb3mRyXhrU%2Fimage.png?alt=media\&token=8cdc2e8f-02d0-4dcb-8884-514c6080769c) However, if I later want to create a `Concrete` Tag to represent the general concept of `Apples`, I should also edit the `Apple` Tag (Apple relates to Apples), and link the new `Apples` Tag to `Fruits` (Apples relates to Fruits). **Auto-create Tag Links** automates this step so that you don't need to think about it. To achieve this, you would do the following when adding the `Apple` Tag: 1. Add `Fruit (a piece of)` as an `Is A` relationship in the relationships step 2. In the **Advanced** step, set **Auto create abstract tag links?** to `Yes` 3. In **Create parent or pick existing?**, select `Create new` (assuming there is no pre-existing `Apples` Tag) 4. The **Edit name for parent** text box should be pre-populated with "Apples" - this is the name for the `Concrete` parent that it will create 5. Click **Finish**. This will produce the following result: ![](https://2847533834-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVy65sax6FVoNo2UTlJ0x%2Fuploads%2FCNTqjtjV2WUQNoG3YTiV%2Fimage.png?alt=media\&token=fc7724fd-09b1-4efb-a5f9-c702200edcd1) `Apple` is now linked to `Apples` and also to `Fruit (a piece of)`, and the auto-created `Apples` Tag is linked to `Fruits`. {% hint style="info" %} It's up to you to decide how much detail to create in your Tags, depending on what you use them for. In some situations, it's good to keep Tags as organised as possible, as in the example above, in which case this function is useful for consistency, and a timesaver. In other situations, this level of organisation is overkill. **Auto-create Tag Links?** is set to `No` by default, so if needed, you can create an `Abstract` Tag simply by entering a Name, choosing a Namespace and pressing **Finish**. {% endhint %} # Home Tab The starting point for Models

Screenshot showing the Home Tab of Models. There are several Models shown in a list - the user has selected the first Model, a preview of which is being shown on the right hand side. — The Models Home Tab

The **Home Tab** in Models is the first screen that you see when you open the application. In the Home Tab you can: 1. Search for existing Models 2. [**Create a new Model**](/models/home-tab/creating-a-model) 3. Edit the name, [**Namespace**](/using-taglo-software/namespaces) and [**Timings**](/models/home-tab/creating-a-model/timings) of a Model, and apply [**Tags**](/tags/introduction-to-tags) 4. Open a Model for editing 5. [**Restore previous versions**](/models/home-tab/version-history) of a Model 6. Edit Application settings # Creating a Model How to create a new Model [**The "Add New Item"**](/using-taglo-software/the-taglo-interface/adding-items) wizard for Models comprises 2 pages. ## 1. Setup To create a Model, you must at a minimum give it a **Name** and select a [**Namespace**](/using-taglo-software/namespaces)**.** Optionally, you can add Tags to your Model, which will help you find it and related Models in the Home Tab. You are free to select any Namespace for your model, but we recommend using a new Namespace for each Model. This gives you maximum flexibility without worrying about the impact of your work on other Models/Namespaces. {% hint style="info" %} If you want to reuse Tags/Dimensions across Models, you can put those Tags in a common Namespace which you then reference from the Model's Namespace. See [**here**](/using-taglo-software/namespaces) for more information on how to use Namespaces. {% endhint %} ## 2. Timings New Models have default [**Timings**](/models/home-tab/creating-a-model/timings) of 10 years, starting in the current year. You can change Timings when creating the Model, or in the [**Model Editor**](/models/model-editor) at any point. Read on for more details on how Timings work in Models. # Timings Setting up Model Timings ## Overview Each **Model** performs its calculations over a period of time that you define, whether that be 5 days, or 20 years. Every [**Variable**](/variables/variable-basics) in the Model will have a value for each separate time interval in the model. You can choose: 1. The [**Interval Type**](#interval-type) of the model (Days, Months, Years...) 2. The [**Start/End/Duration**](#start-end-duration) of the model 3. The [**Fiscal Year End**](#fiscal-year-end) ## Interval Type Models offers 5 interval types: Day; Week; Month; Quarter; Year This determines the length of an individual period of the Model. {% hint style="info" %} Individual Model periods are always consecutive, and of the length of 1 interval. e.g. if the first period of a Model is a Week, ending on Friday 6th January 2023, the second period will be the week ending Friday 13th January 2023. {% endhint %} ## Start/End/Duration You must define the beginning and end of your Model Timings, which you can do by setting **any 2** of: 1. Start date 2. Duration (in number of intervals) 3. End date Setting any 2 of these will automatically update the third. {% hint style="info" %} There is no defined limit to the number of intervals to use in your Model, but be aware using a large number of intervals (e.g. >100) may cause performance issues, depending on Model complexity. {% endhint %} Start/End dates are entered as text, with the format determined by the selected Interval Type, as shown in the example image and table below.

### Start/End Date text formats

Interval Type	Text Format	Notes
Day	yyyyMMdd	Year/Month/Day
Week	yyyyMMdd	Refers to the 7-day period ending at the entered date
Month	yyyyMM	Year/Month. Precise date will depend on Fiscal Year End settings.
Quarter (Option 1)	yyyyQ[1-4]	Precise date will depend on Fiscal Year End settings. e.g. 2020Q4 refers to the last quarter of the 2020 fiscal year. If Fiscal Year End is set to March (End of Month), the precise date will be 31st March 2020.
Quarter (Option 2)	yyyyMM	Precise date will depend on Fiscal Year End settings. e.g. 202003 refers to March 2020. If Fiscal Year End is set to March (End of Month), this will be equivalent to 2020Q4 (31st March 2020). A quarter entered in this format must be a valid quarter end month.
Year	yyyy	Precise date will depend on Fiscal Year End settings.

## Fiscal Year End The Fiscal Year End (FYE) is how a business defines the end of its operating year, for accounting purposes. e.g. a company's FYE might be 31st March, meaning that its company accounts will cover the period from 1st April one year to 31st March the next. In the vast majority of instances, the FYE is at the end of the month (e.g. 31st Dec, 28th/29th February, 31st March). However, Models allows you to define an FYE at a specific day in a month (from 1-31). If a quarter ends in a month that has fewer days than the day specified, the end of that month will be used. {% hint style="info" %} Not all Models will be financial in nature, but you can still use the FYE to define when your intervals end. e.g. if you want a yearly model that starts on March 5th every year, you would set the FYE as shown in the image below. {% endhint %}

Shows Fiscal Year End month entered as 3 (March), End of Month option selected as "Day in month", and day of month entered as 4 — Fiscal Year End entry

# Version History How to restore previous versions of your Models ## Restoring old versions By default, we will store a new version of your Model for **every** change that you make. You can use [**Undo**](/using-taglo-software/the-taglo-interface/save-undo-redo) to quickly undo changes, but to access old versions more easily, you can use the **History** panel in the Model preview in the Home Tab. The History panel shows you all available previous versions of the Model, with the date and time at which they were created. For each version, you have the option to **Restore as new**, or **Restore**. **Restore as new** will create a new Model, starting at the restore point. **Restore** will overwrite the current version with the previous, ***so use this option with care***.

## Reducing history size If you want to reduce the size of the version history on disk, you can run a clean up of old files, by clicking on **File > Clean old files** in the Home Tab. This will keep one version per day for all Models, and delete all other versions. Currently, **Clean old files** can only be used across all Models simultaneously. # Application Settings Home Tab settings Access Models application settings by clicking **Edit > Edit Settings** from anywhere within the application. A wizard will be opened in which settings can be edited. ### Default Theme Choose a Default Theme to use for new Models. Themes are used to format generated Excel spreadsheets. Read more about Themes [**here**](/layout/excel-formatting/excel-themes-and-styles). # Model Editor Overview of the Model Editor

Screenshot of the Model Editor interface showing a Model with a Variable selected, and a preview of that Variable shown — Screenshot of Model Editor interface

The Model Editor is the primary applet you will use when editing Taglo Models. Viewing some of our [**video tutorials**](/start-here/tutorials#introductory-tutorials) is a great way to get to know the interface. ### Editor Tabs You can access the various functions of the Model Editor by navigating through the tabs on the left-hand side of the application from **Variables** to **Excel Outputs.** {% hint style="info" %} Use the `Ctrl + q` and `Ctrl + Shift + q` [**shortcuts**](/using-taglo-software/the-taglo-interface/keyboard-shortcuts) to move quickly between tabs {% endhint %} Each tab displays a [**List View**](/using-taglo-software/the-taglo-interface/list-views#overview) showing different components of your model. Continue reading the documentation to understand each one. ## Model settings bar

Screenshot of the Model Settings bar — The Model Settings bar

The Model Settings bar is positioned at the top of the Model Editor, and can be hidden or shown as desired using the expander button at the top left. The settings bar allows you to edit Model Timings, Scenarios and Sensitivities, and perform various other functions, each of which is described in more detail in the relevant section of documentation. ## Model settings Clicking **Edit** in the **Model Settings** section opens a wizard in which you can edit other Model-specific settings including: * Model [**Theme**](/layout/excel-formatting/excel-themes-and-styles#default-and-model-themes) * Default [**Number Format**](/number-formats/number-formats) * Default [**Unit**](/units/introduction-to-units) * Various Excel formatting settings # Variable Basics What are Variables? ## Overview **Variables** are the items that form the logic of your model. Imagine you're building a forecast budget for your business. Examples of Variables might be: **Total Revenues**; **Number of Employees**; **Office Costs.** {% hint style="info" %} If you're used to working in Excel, you can think of Variables as like the lines in your model, but a lot more powerful {% endhint %} Variables can reference inputs to the model (called [**Assumptions**](/assumptions/introduction-to-assumptions)), or they can reference other Variables, through [**Calculations.**](/calculations/introduction-to-calculations) A Calculation might look something like: ``` Profits = Revenues - Costs ``` In this way, you can link Variables to each other and develop the structure of your model. The rest of this section explains how to configure Variables and the huge range of ways you can work with them. ## The Variables list view By default, Variables are shown in a [**Tree View**](/using-taglo-software/the-taglo-interface/list-views#view-types), but you can also view them in a flat list, or a grid.

In the Tree View, as shown above, the tree represents the relationships between the Variables. In this example, `Revenues by region` references `Revenues by region and membership type`, which in turn has a Calculation of `Gym members * Revenue per member`, hence these two Variables are shown as its children. Using the Tree View, you can quickly navigate the relationships between Variables to understand and interrogate Calculations. ## The Variables preview Each Variable in the list can be [**previewed**](/using-taglo-software/the-taglo-interface/previewing-and-editing) in detail, as per the example below:

# Variable Setup How to create and configure a Variable The items on this page can all be configured on the **Name and Setup** step of the Variable dialog.

A screenshot of the Setup step of the new Variable dialog, containing several steps — Variable dialog | Name and Setup step

## Name There are no restrictions to how you name your Variables, as long as the name isn't blank. Make them as readable and self-explanatory as possible and thank yourself later! {% hint style="info" %} Bear in mind that if you will be generating Excel from your Model, Variable names will be written in the spreadsheet, meaning you should avoid choosing a name that Excel will interpret as a formula, otherwise you will run into problems. But if you really want to start a name with an "=", we won't stop you. {% endhint %} ## Variable type There are three types of variables in Models: 1. Assumption 2. Calculation 3. Aggregation The **Variable type** you choose determines the default way that the Variable will calculate its value. Variables can calculate values from both **Assumptions** and **Calculations** in different periods of the model by using Time Segments. See the [**dedicated help section on Time Segments**](/variables/time-segments) for more details. **Aggregation** Variables must calculate value via aggregation for the entire model period. ### Assumption Variables Assumption Variables are usually the starting point of your Model. They reference the basic inputs, called Assumptions, that underpin your Model's calculations. Read more on how Assumptions work [**here**](/assumptions/introduction-to-assumptions)**,** and how to reference them from your Variable [**here**](/assumptions/creating-referencing-assumptions). ### Calculation Variables Calculation Variables obtain their values by referencing other Variables and performing a calculation. e.g. `Profits = Revenues - Costs.` Read more about Calculations [**here**](/calculations/introduction-to-calculations)**.** ### Aggregation Variables {% hint style="warning" %} You will only see the **Aggregation** option if you have already selected one or more [**Dimensions**](#dimensions) for your Variable ([see below](#dimensions)). {% endhint %} Aggregation allows you to bring values from several separate Variables together into a single Variable. Read more about Aggregation [**here**](/aggregation/introduction-to-aggregation). ## Dimensions Select any [**Dimensions**](/dimensions/introduction-to-dimensions) that you want to apply to your Variable. Dimensions allow you to work with a collection of items without having to repeat calculations. > For example, a Dimension might be: > > * **Widget Model** | Model A, Model B, and Model C > > or > > * **Sales Region** | North, East, West, and South Dimensions are extremely powerful, time-saving, and improve the quality of your Models. Read more about how to use Dimensions [**here**](/dimensions/introduction-to-dimensions). ## Number Format A Number Format determines how the calculated values for your Variable will be displayed. You can choose from inbuilt Number Formats or create your own. Any Assumptions you create from within the Variable will use the same Number Format by default. Read more about Number Formats [**here**](/number-formats/number-formats). ## Data Type Models works with several Data Types, which affect how values are treated in calculations. These include Data Types for working with numerical values, text values, date-time values and others. Read more about the different Data Types and how to work with them [**here**](/data-types/data-types). ### Validation Dimension The Validation Dimension step will only appear if you select the `Validation` **Data Type**. Validation allows you to select inputs from a list of values. > For instance, a Variable called `Include tax?` may be an Assumptions Variable where you want to choose between `Yes/No` options. To achieve this, select the `Validation` Data Type, and then select the inbuilt `Yes/No Option` Dimension in the Validation Dimension step. The Validation chosen here will be applied to any Assumptions created from this Variable. You can use any Dimension for Validation. ## Time Period You may want to see outputs from your Model on a different timescale to that defined in the Model [**Timings**](/models/home-tab/creating-a-model/timings). > For instance, for a Model built on a Monthly basis, you may want to see outputs in Quarters or Years How Models calculates the value for each aggregated period depends on the Unit of the Variable. `Balance` Variables will calculate the value at the end of the period, and `Flow` Variables will sum the values of intervening periods. Read more about `Balance` and `Flow` concepts in the [**Units documentation**](/units/introduction-to-units). {% hint style="info" %} If you select a Time Period other than `Default`, your Variable will automatically be a Calculation Variable, and you will not be able to edit [**Time Segments**](/variables/time-segments). {% endhint %} ## Tags You can Tag Variables just like any other taggable item in Taglo software, which will allow you to filter the list of Variables by those Tags. Read more about Tags and tagging [**here**](/tags/introduction-to-tags). # Unit and Calculations Entering Unit and Calculation for a Variable The **Unit** and **Calculation** of a Variable (if required), each have a dedicated step in the Variable wizard.

Two screenshots. The left hand side screenshot shows the Units step of the Variables dialog. The right hand side shows the Calculation step of the Variables dialog. — Unit and Calculation steps of the Variable dialog

{% hint style="info" %} If this is your first time defining a Unit, we recommend reading the [**Introduction to Units**](/units/introduction-to-units) first {% endhint %} ## Infer/Specify unit A Calculation Variable can derive its Unit automatically, based on the Variables that it references. > For instance, a Variable called `Revenues` has a Calculation `= Widgets Sold * Price`, where `Widgets Sold` has a Unit of `Widget`, and `Price` has a Unit of `US Dollars / Widget`. In this case, the Revenues Variable can infer that its Unit is `US Dollars` Sometimes you will want to specify the Variable's Unit explicitly. In this case, select the **Specify Unit** option, and the Unit-editing page of the dialog will be shown. > For instance, a Variable called `Customers` has a Calculation = `Customers [-1] + New customers`. This Variable references the previous period of itself, so cannot infer its Unit automatically. In this case, you will need to specify the Unit explicitly. Read more about Units [**here**](/units/introduction-to-units). {% hint style="info" %} You will only see the Infer/Specify unit step if you have selected the **Calculation** Variable type. **Assumption** and **Aggregation** Variables must specify Units explicitly. {% endhint %} # Time Segments Overview of Time Segments ## Overview **Time Segments** allow a [**Variable** ](/variables/variable-basics)to calculate its values differently depending on the period of the [**Model**](/models/home-tab).

Shows the preview panel of a Variable with two Time Segments — Example Variable with two Time Segments

For instance, in the example above, the `Monthly price per member` Variable calculates its value using an inflation [**Calculation**](/calculations/introduction-to-calculations): `Monthly price per member [-1] * (1 + Price inflation)`. This Variable references the previous period's value of itself (indicated by the `[-1]` part of the Calculation). At the start of the Model, we need to tell the Variable what that value should be, as there are no previous periods to obtain the value from. We do this by creating a new Time Segment for the first period of the Model, which will act as an `Assumption` segment, which we can link to the inputs of the Model. The second Time Segment is an `Auto` segment, meaning it performs the default Calculation of the Variable. The rest of this section explains the various ways of creating and manipulating Time Segments, and the implications of using them. # Time Segment Setup How to create and edit Time Segments ## Creating/Editing Time Segments Time Segments are managed in the Time Segments step of the **Variable** dialog.

Screenshot of the Time Segments step of the Variables wizard — Time Segment step of the Variable dialog

You can add, edit and duplicate Time Segments just like any other item in a [**list view**](/using-taglo-software/the-taglo-interface/list-views). ## The Time Segment Wizard ### Timings You must define the time period over which each Time Segment applies. This time period is defined in terms of three settings: 1. **From**: The period at which the segment starts 2. **Duration**: The length of the segment 3. **To**: The period at which the segment ends As shown in the screenshot below, these settings can be quickly edited by clicking on the relevant editing shortcut button

Screenshot showing two Time Segments with timings editing shortcut buttons highlighted — Timings editing shortcuts

**From** and **To** settings can be set to one of the following:

From/To setting	Details
`Auto`	Period dependent on context: If first segment, From will be set to the start of the model If last segment, To will be set to the end of the model If other, From/To will be based on end or beginning of adjacent segments).
`Fixed Period`	Choice of specific periods from the Model timings (e.g. Q2 2030)
`Periods from Start`	Number of periods from start (first period = 1 )
`Periods from End`	Number of periods from end (last period = 1)

**Duration** can be set to one of the following:

Duration setting	Details
`Fill`	Segment will stretch to end of previous period and beginning of next (or to start/end of the model if first/last segment)
`Number of periods`	Segment will occupy the specified number of periods

{% hint style="warning" %} You should apply a **maximum of 2** of the three settings. Which settings are applied depends on the Time Segment. For instance, the first Time Segment never needs to have the **From** setting applied, as it always starts at the first period. If you set **From** to a period that is not the first period, a warning will be shown. Likewise, if you set both the **Duration** and the **To** settings of the first Time Segment, one of these will be redundant, and they may clash. {% endhint %} ### Formula The **Formula** of a Time Segment determines how that Time Segment calculates its values. There are five possible formula types for each Time Segment:

Formula Type	Details
`Auto`	Applies the default Calculation of the Variable. (This option is not available for an Assumptions Type Variable).
`Assumptions`	Links to specific Assumptions. See Creating/Referencing Assumptions for more details.
`Calculation`	Applies a custom Calculation that cannot refer to other Variables. (See more details below).
`Aggregation`	Used for an Aggregation Variable. Cannot be manually selected - applied automatically when using Aggregation.
`Rearranged`	Used when Rearranging. Cannot be manually selected - applied automatically when Rearranging

#### Calculation Formula

As shown in the above example, a Time Segment with a Calculation formula acts similarly to an Assumptions Time Segment. In this example, `Price inflation` is a Variable of type `Assumptions`. In the first period, an Assumptions Time Segment links to an input. We then use a Calculation Time Segment for the remaining periods to reference the previous period, rather than linking to specific Assumptions for each period of the Model. {% hint style="info" %} `Calculation` Time Segments act similarly to `Assumptions`, in that they specify an **input** to the Model. For this reason, calculations in Time Segments cannot reference other Variables. If you want to perform a calculation referencing other Variables, the Variable itself must be of type `Calculation.` If you are not sure when to use Assumption/Calculation Variables and Assumption/Calculation Time Segments, you may want to read about the [**Rearranging feature**](/rearranging/rearranging-example), which helps deal with complex scenarios. {% endhint %} ## Time Segment shortcuts

Screenshot showing the Time Segments step of the Variable wizard, highlighting the shortcut buttons used for editing Time Segments — Time Segment shortcuts

Several shortcuts are provided in the Time Segment interface to speed up some common operations, as shown in the image above.

Shortcut	Details
1) Insert period	Inserts a period of duration 1 period at the start of the Model
2) Make all equal to first period	Inserts a single period segment of type `Assumptions` at the start of the Model, and a second segment with a `Calculation` of `Variable [-1]` for the rest of the Model timings (as per the example shown in the image above).
3) Change formula type	Opens a dropdown to quickly switch between formula types.
4) Reset to default segment type	For a Calculation Variable, resets Time Segment to `Auto`. For an Assumptions Variable, resets Time Segment to `Assumptions`.

# Summaries Editing Row and Columns Summaries of Variables ## Overview

Variables can be summarised in two ways, both accessible from the **Summary** step of the **Variable** wizard. ## Row Summary A **Row Summary** is only applicable when the Variable has one or more [**Dimensions**](/dimensions/introduction-to-dimensions) applied. For instance, in the example below, the Variable has a `Membership Tier` Dimension applied, with three items: `Basic`, `Premium`, and `Platinum`. The Row Summary determines how the **All** line is calculated (in this case, a `Sum`).

Sum summary of a Variable with a Dimension

{% hint style="info" %} Note, when you apply Dimensions to a Variable, Models will try to apply the most appropriate type of Summary automatically for you, so most of the time you will not need to manually set one yourself. {% endhint %} The following Row Summary types are available:

Row Summary type	Details
`None`	No summary applied
`Sum`	Sum of all row values
`Auto`	Applies calculation of Variable (see details below)
`Rearranged`	Calculates value based on parent Variables (see details below)

A `Sum` Row Summary is commonly the desired output, but there are situations where a Sum total of rows is not a meaningful calculation, in which case you should choose between an `Auto` or `Rearranged` Summary. ### Auto Row Summary An `Auto` Row Summary is only available for **Calculation** Variables. In this case, the Summary is calculated by applying the default Calculation of the Variable to the Row Summary lines of the referenced Variables. > For instance, if the Variable's Calculation is `Profit Margin = Profit / Revenues` across several items, a Sum of Profit Margin is not meaningful. In this case, a useful Summary is to apply the calculation `Profit / Revenues` to the summary line of `Profit` and `Revenues`. {% hint style="warning" %} An Auto Row Summary will only work successfully if all referenced Variables have a Summary row themselves (or do not have a Dimension applied) {% endhint %} ### Rearranged Row Summary A `Rearranged` Row Summary is used when a meaningful summary value depends on the Variable parents' values. To apply a Rearranged Summary, we select the `Rearranged` option, and then select the parent Variable which we would like to rearrange. > For instance, if we have a Variable `Price`, across the `Membership Tier` Dimension (`Basic,` `Premium,` `Platinum)`, a meaningful summary output is the weighted average price across all tiers. > > Elsewhere in the Model, we calculate `Revenues = Price * Customers`. > > In the Summary step of the Variables wizard, we select `Rearranged` and then choose `Revenues` as the rearranged parent. Models then calculates the weighted average price as `Price = Revenues / Customers`, based on the Calculation of the `Revenues` Variable.

Screenshot showing Summary page of the Variable wizard, with a rearranged summary selected — Rearranged Summary example

## Column Summary A **Column** Summary generates a value for a Variable based on all periods of the Model. Column Summaries can be applied to all Variables and any number of Column Summaries can be added. The following Column Summary types are available:

Column Summary type	Details
Total	Sum of values across all periods
Average	Mean average of values across all periods
Min	Minimum value across all periods
Max	Maximum value across all periods
Last	Value at last period
CAGR	Compound Annual Growth Rate across all periods

Additional options: * A specific [**Number Format**](/number-formats/number-formats) can be selected for each Column Summary. * A divisor can be applied, to make the output smaller. Options are: `None`, `Thousands`, `Millions`, `Billions`, `Trillions` ## Multiple Summary Editing The Summaries of multiple Variables can be edited simultaneously by selecting the Variables and clicking the **Edit Summaries** button in the Variables context menu.

The Edit Summaries button — Edit summaries button

The `Rearranged` Summary option will not be available if edited multiple Variables at once. # Default Assumptions How to use a Default Assumption to replace missing Assumptions ## Overview You do not have to specify every [**Assumption**](/assumptions/introduction-to-assumptions) of an Assumption [**Variable**](/variables/variable-basics). For instance, you might have a Variable called `One-off costs`, as in the screenshot below. There are 20 periods in our [**Model**](/models/home-tab), but we only want to enter Assumptions for two of those periods, March and December 2025. In this case, we can use a Default Assumption to provide a value for the other periods. The screenshot below shows that we have only selected 2 Assumptions in the [**Time Segment**](/variables/time-segments) **(1)**, but no warning is shown because we have added a Default Assumption that provides a value of `0` for any period without an Assumption.

## Adding a Default Assumption To add a Default Assumption, perform the following steps, as illustrated in the screenshots below. * In the **Variable dialog**, navigate to the **Default assumption step** **(1)** (this will only be shown if `Assumption` Variable type is selected in the **Name and Setup step** * If your Default Assumption does not already exist, ensure that the **Item statuses** table has its only cell selected **(2)** * Click the **New** button **(3)**, which will open an [**Assumptions dialog**](/assumptions/assumptions-wizard) **(4)** in which to create the Default Assumption * Enter any details and the value of the Assumption, click **Finish**, and the Assumption will be selected

# Introduction to Units How do Units help us build better Models? When we build models in Excel, we often use units only as an afterthought. Maybe we add a column in which we write a `$` symbol to indicate that a line is in US Dollars. But this is only done as a hint to the spreadsheet user and has no direct impact on any calculations. In [**Models**](/models/home-tab)**,** Units are built into the fundamental workings of the software. Each [**Variable**](/variables/variable-basics) has a Unit, and if a [**Calculation**](/calculations/introduction-to-calculations) produces an inconsistent Unit, you will see a warning, letting you know that there may be a logical error in your Model. Units in Models also allow you to automatically move between items of different size, e.g. $ to $000 to $m, (see [**Factors**](/units/key-unit-concepts#factors)). Units also enable much of the advanced functionality in Models, such as: * Automatically [**matching Assumptions**](/assumptions/creating-referencing-assumptions#time-segment-editing) to Variables. * [**Aggregation**](/aggregation/introduction-to-aggregation) of multiple Variables * Performing automatic and custom Dimension [**references**](/calculations/calculation-parts/variable-references/referencing-dimensions) in Calculations {% hint style="info" %} For the most part, you don't *have* to use Units to produce a working Model. Inconsistent Units will only produce warnings, not errors, and calculations will still be performed. And if you want to, you can create a Model with only `Unitless` Variables. The Models UI is designed to make the use of Units as easy as possible, and to add only a small overhead to your build process. We hope that once you understand how Units work, it will help you build better, more-readable Models, with fewer errors. {% endhint %} # Key Unit Concepts Understanding Units ## Calculation Consistency Units allow you to ensure that [**Calculations** ](/calculations/introduction-to-calculations)are consistent. As a simple example, it is logically incorrect to sum together two [**Variables**](/variables/variable-basics) which have a different unit. > Adding a Variable in `GBP` to a Variable in `USD` has no real meaning. If you attempt to do this, Models will warn you that it cannot determine the resulting Unit, which will prompt you to correct the Calculation. One of the two Variables should first be converted to the other currency, before summing, using an exchange rate Variable, with Unit `GBP/USD` or vice versa. Non-additive operations, such as multiplication, transform Units. > Multiplying an exchange rate with Unit `GBP/USD` by a Variable with Unit `USD` results in a Variable with Unit `GBP`. > > Squaring a Variable will raise the Unit to a power of 2: e.g., Distance in `metre` multiplied by itself will result in a Variable with Unit `metre^2` Models will automatically derive the Units of your Calculations and tell you the resulting Unit, or display a warning if the Unit is not as expected. ## Units and Tags Just like [**Dimensions**](/dimensions/introduction-to-dimensions) and other Taglo concepts, Units are based on [**Tags**](/tags/introduction-to-tags). Each Unit component (e.g. GBP, USD, metre) is itself an [**Abstract Tag**](https://help.taglo.io/units/pages/xKXxhPqflNveH4QpWCHU#abstract-vs.-concrete). When you create a new type of Unit, you simply create a new Abstract Tag. Use the Short Name property of a Tag to determine how the Tag will be displayed within a Unit (e.g., the `metre` Tag has a Short Name of `m`). {% hint style="info" %} Commonly used Units like currencies, units of time, and units of distance can be found in the built-in [**Namespaces**](/using-taglo-software/namespaces). {% endhint %} ### Inheritance {% hint style="warning" %} Unit inheritance analysis is available from Version 0.1.4.0 of Models {% endhint %} Because Units are based on Tags, they have access to all of the relationships you have created between Tags. This allows Models to make more intelligent inferences about the output Unit of a Calculation. > For instance, if you have a Variable with Unit `Apple`, and a second Variable with Unit `Banana`, you should not ordinarily sum these Variables together, as explained [**above**](#calculation-consistency), and Models will warn you about it if you do. > > However, if the `Apple` and `Banana` Tags both have a third tag, `Fruit` as a common parent Tag, Models can infer that the Calculation is adding `Fruit` together, rather than Apples and Bananas, resulting in an output Unit of `Fruit`. The above example will be represented in the Variable view as in the screenshot below. When a Variable is reliant on inheritance to calculate or correctly match its Unit, as is the case for Total Fruit below, Models will show a warning **(1)**, in the Variable.

Screenshot showing an example of Unit inheritance. There are three Variables: Bananas, Apples, and Total Fruit. Total Fruit is a parent of the Apples and Bananas Variables. The Total Fruit Variable has a visual warning that its Unit is only valid because its calculation components have a common ancestor. — Unit inheritance example

#### Disabling Inheritance Unit inheritance can be enabled/disabled in the [**Model settings**](/models/model-editor#model-settings-bar) wizard, as shown below. Open the settings wizard from the Model Settings bar, and select or deselect the **Allow Unit inheritance** option **(1)** as required.

Screenshot of the Model Settings dialog, highlighting the option to Allow Unit Inheritance — The Allow Unit Inheritance setting

## Compound Units Many Units are Compound Units: for example, the exchange rate `GBP/USD`. In Taglo, we refer to each component of the Unit as a **Unit Part**. {% hint style="info" %} In this example, the `USD` Unit Part has an **Order** of `-1`, making it the denominator of the Unit. {% endhint %} In the next section, [**Advanced Units**](#advanced-units), you will learn how editing each Unit Part adds functionality to Taglo software. ## Summary Units help you achieve logical consistency in your calculations. Models allows you to add extra time and contextual detail to your Units, which provide useful information about how the [**Variables**](/variables/variable-basics) and [**Assumptions**](/assumptions/introduction-to-assumptions) in your Model should be treated. As you read more about working in Models, you will see how these concepts are used to enable powerful functionality. > For instance, [**Dimensions**](/dimensions/introduction-to-dimensions) work by automatically applying context Tags to the underlying Unit of a Variable. Read on to learn how to create Units. # Advanced Units How to use Units to describe additional information ## Overview In addition to the the straightforward examples on the [**previous page**](/units/key-unit-concepts), Models applies factors, and concepts of time and context to Unit Parts. ## Unit Factors It is common for models to change between different "sizes" of unit. > For instance, a financial model for a large company may have a "standard monetary unit" of $000. This means that, unless otherwise specified, all monetary figures are in thousands of US dollars. > > Some Variables may need to be specified in a different unit, e.g. the price of a product may be in single US dollars ($). Unit Factors in Models allows you to move between different factors within the same Model, without needing to specify different versions of the same Unit. Read more about how to use Unit Factors [**here**](/units/unit-factors). ## Balance vs. Flow The concepts of Balances and Flows are commonly used in financial modelling (you may also have seen the term Stock used instead of Balance). > An example of a **Flow** is my annual wages - how much money I have coming in each year. A **Balance** is the amount of money I have in my bank account. A Flow must relate to a *period* of time (e.g. a day, month or year), whereas a Balance is a snapshot at a *point* in time. In Models, this concept is captured within a Variable's Unit, which allows Models to infer more context about a calculation. Models applies the following rules: * Adding a `Balance` to a `Balance` gives another `Balance` * Adding a `Flow` to a `Balance` gives a `Balance` at a later point in time (see [**Time Offsets**](#time-offsets)) * Adding a `Flow` to a `Flow` gives another `Flow` ## Time and Time Offsets Units also hold information about time. > Imagine you want to calculate the number of members who leave your gym business each year (called `Churn`), you would do this by applying a `Churn rate` to the number of customers at the end of the previous year: `Churn = Members [-1] * Churn rate`. > > Now let's say I have an [**Assumption**](/assumptions/introduction-to-assumptions) representing actual churn rate in 2021. The Unit for that Assumption would be `Member [Flow, 2021] / Member [Balance, 2020]`. > > Without these details in the Unit, we would probably label our Assumption as `Unitless, 2021`, which would exclude important information about the assumption and pose several questions: Does 2021 relate to the churned customers, or the starting balance?; What is being churned?; Is the Assumption a Flow or a Balance? (*answer: it is a combination of the two*). > > Including time information in the Unit answers these questions in a concise format. When creating the Unit for a Variable, it is rare to use specific dates - each Unit Part has a **Time Offset** defined, such as `This Period`, or `Offset [-1]`. Any Assumptions created for this Variable will then have specific dates applied to their Unit based on the Timings of the Model. See the [**next section**](/units/defining-a-unit) for more details on defining Units. ## Constants Units can also be defined as Constant, either as `Constant (Flow)`, or `Constant (Balance)`, to indicate values that are unchanging over time. ## Context (Unit Modifiers) Just as we add information about Time to Unit Parts, we can also add information about Context by using [**Concrete Tags**](https://help.taglo.io/units/pages/xKXxhPqflNveH4QpWCHU#abstract-vs.-concrete). Context Tags act as a *modifier* to the main Abstract Tag of the Unit part. > For instance, if we have a data point representing the population of the United Kingdom at the end of 2022, we would give it the Unit `Person [Balance, 2022, UK]` where `UK` is the Tag for the United Kingdom. > > Taglo interprets this Unit as `Person relating to the UK [Balance, 2022]`. This allows Taglo to infer relationships between different data points based on their Units. > For instance, let's say we have the following data points: `Person [2020, UK]`, `Person [2021, UK]`, `Person [2022, UK]`, `Person [2021, France]`, `Person [2021, Spain]`(all `Balance` Units). > > In this case, Taglo can identify two series from this data: 1) the UK population, changing over time from 2020 to 2022; 2) The population in 2021 of three countries, the UK, France and Spain. It can identify the second series by virtue of the fact that the `UK`, `France`, and `Spain` Tags all have `Country` as a parent. This method of applying Context to Units avoids the completion of multiple bespoke fields when entering data. You don't need to define a `time` field, or a `country` field - just include the Time and Context in the Unit. This is particularly powerful for [**Compound Units**](#compound-units), where the Context of one Unit Part might be different from another. > For instance, I might have data representing the ratio of one country's GDP to another, in `USD`. e.g., `USD [UK] / USD [USA]`, and `USD [France] / USD [USA]`. > > Normally, I might choose to call these data points *Ratio of GDP to USA GDP*, and then include a `Country` field for the country I'm comparing (`UK` or `France)`. > > But what happens if I introduce a third data point, `USD [France] / USD [UK]` to my dataset? > > I would have to call it *Ratio of GDP to UK GDP.* The information about the country I'm comparing France to is hidden in text, and software can't infer a relationship about the two France ratios (one to the USA, and one to the UK). > > One solution is to have two extra fields: `Compared country` and `Compare To country`. It doesn't take too much imagination to see that this could soon become unmanageable, and more importantly, not useful. By adding Context to Unit Parts, we take care of this problem. # Defining a Unit How to create and edit Units

Screenshot of the Unit step of the Variable dialog — Unit step of the Variable wizard

{% hint style="info" %} If this is your first time defining a Unit, we recommend reading the [**Introduction to Units**](/units/introduction-to-units) first {% endhint %} You will most commonly define [**Units**](/units/introduction-to-units) as part of the [**Variable wizard**](/variables/variable-basics/unit-and-calculations). You will only need to define a Unit if your Variable is an `Assumptions` Variable, or if you select the `Specify Unit` option for a `Calculation` Variable. The Unit step is simply a list of [**Unit Parts**](/units/key-unit-concepts#compound-units), in a standard [**List View**](/using-taglo-software/the-taglo-interface/list-views), in which you can *Add*, *Edit* and *Duplicate* Unit Parts. The resulting Unit is shown as a formula at the top of the step. Each Unit Part can be edited in a separate wizard, or specific properties can be edited individually by clicking on one of the shortcut buttons displayed.

Shortcut buttons (as per above image)

Change the base [**Tag**](/tags/introduction-to-tags) and/or [**Unit Factor**](/units/advanced-units#factors) *

Change the Order *

Change the Time Type (`Flow`, `Balance`, `Flow (Constant)`, `Balance (Constant)` *

`Change the Time Offset` *

`Add a Context modifier` *

Multiply the Order by -1 *

Make a copy of the Unit Part

{% hint style="info" %} Functionality of the Unit step depends on the context. You will find additional options if your Variable has [**Dimensions**](/dimensions/introduction-to-dimensions), or if you are creating a [**Data Point**](/assumptions/assumptions-wizard/linking-to-external-data) from scratch. These differences are covered in the relevant sections of documentation. {% endhint %} ## Default Unit You can set a default Unit for new Variables by navigating to [**Model Settings**](/models/model-editor#model-settings)**.** # Unit Factors How to move between different "sizes" of Unit ## Overview It is common for models to change between different "sizes" of unit. > For instance, a financial model for a large company may have a "standard monetary unit" of $000. This means that, unless otherwise specified, all monetary figures are in thousands of US dollars. > > Some Variables may need to be specified in a different unit, e.g. the price of a product may be in single US dollars ($). Unit Factors in Models allows you to move between different factors within the same Model, without needing to specify different versions of the same Unit. ## Defining Unit Factors Factors are applied to individual Unit Parts. When a Factor has been applied, it will be shown in brackets alongside the unit type, for example `GBP (000)` as shown in the screenshots below. To edit the Factor, click on the Unit within the Unit Part **(1)**, which will bring up a Unit editor popup, within which you should click the "More" button **(2)**. This will open a new wizard step in which you can edit both the base Tag of the Unit Part and the Unit Factor **(3)**.

Screenshot showing the Unit step of a Variable dialog, in which the Unit is currently set to GBP. — Shortcut to bring up the Unit editor

Screenshot showing a Unit Part editing dialog, with the Unit Factor dropdown highlighted. — Choosing a Unit Factor

## Moving between Unit Factors in Calculations Factors will be assessed by Models when analysing whether [**Calculations**](/calculations/introduction-to-calculations) are consistent. Models will show warnings if: 1. A Calculation produces a factor that is different from that of the specified Unit 2. You try to sum together items with different factors These warnings, and their remedies, are described in the following sections. ### Factor matching error The screenshots below show an example of how Models deals with a change in Unit Factors. In this case, we have a Variable, `Total revenues` of Unit `GBP`. A second Variable, `Total Revenues (000s)` **(1)**, has a Calculation that simply references the first Variable, but its Unit is in `GBP (000s)`. Models detects that the Calculation Unit (`GBP`) does not match the target Unit of `GBP (000s)`, so shows a warning. Models provides two options: *Apply Factoring?* **(3)**, and *Override unit error?* **(4)**. If *Apply Factoring?* is checked, the Calculation is automatically divided by `10^3 = 1000` **(5)**, and a tick mark **(6)** shows that the Variable Unit is now correct. {% hint style="warning" %} Selecting the *`Override unit error?`* option will remove the error, but the calculation will need to be modified manually. We recommend using the automatic factoring where available. {% endhint %}

Screenshot showing a Variable with a Unit matching error, due to non-matching factors — Error before Factoring applied

Screenshot showing a Variable with automatic Factoring applied — Error after Factoring applied

### Addition error The screenshot below shows the result of adding together (or subtracting) items with different Unit Factors. In this case, we have a Variable, `Total Profits` **(1)** whose Calculation is `Total Revenues (000s) - Total Costs` **(2)**. As `Total Revenues (000s)` has Unit `GBP (000s)` and `Total Costs` has Unit `GBP`, Models is unable to determine the resulting Unit of the Calculation.

Screenshot showing a warning when adding/subtracting Variables of different Unit Factor — Error when adding/subtracting Variables with different factors

In this case, the options are: 1. Manually edit the Calculation and select the *Override unit error?* option (see warning below) 2. Create a new Variable that converts one of the parts of the Calculation into the correct Factor first before using it in the Calculation (**recommended**). {% hint style="warning" %} We strongly encourage you **to use option 2** where possible. This will aid clarity of your Model and help other users understand the flow, while ensuring that you do not make a mistake manually converting between factors. {% endhint %} # Introduction to Dimensions How Dimensions allow us to build Models more efficiently ## Overview Dimensions allow you to work with a collection of items without having to repeat calculations. > A Dimension might be: > > * **Widget Model** | Model A, Model B, and Model C > > or > > * **Sales Region** | North, East, West, and South Dimensions are extremely powerful, time-saving, and improve the quality of your Models. In the example screenshot below, the `Revenues by membership type` Variable has the `Membership Tier` Dimension applied. The `Membership Tier` has 3 children: `Basic`, `Premium`, `Platinum`.

The Variable has a single formula, `Gym members * Revenue per member`. The `[Auto]` suffixes in the formula imply that the Calculation is able to automatically reference the appropriate line of the referenced Variables, which both also have the `Membership Tier` Dimension applied. Using Dimensions, you can replace multiple sets of calculations with a single one, without worrying about copy/paste errors. ## Multiple Dimensions You can apply as many Dimensions as you like to a Variable. In the example screenshot below, the `Revenues by region and membership type` Variable has two Dimensions applied: `Membership Tier` and `Region`. Models calculates a value for each combination of the children of the two Dimensions, in this case 6 lines in total.

## Summarising Dimensions Models can create summaries of Dimensions easily - you don't need to worry about referencing the correct lines in a Calculation. In the example screenshot below, we want to show the total Revenues across the `North` and `South` regions from the `Revenues by region and membership type` Variable (see above [**Multiple Dimensions**](#multiple-dimensions) example). To do this we simply create a new Variable with the `Region` Dimension applied, and reference the `Revenues by region and membership type` Variable. Models does the rest for us automatically.

# Dimension Setup How to create and edit Dimensions ## Based on Tags Just like [**Units**](/units/introduction-to-units), Dimensions are based on [**Tags**](/tags/introduction-to-tags). In fact, a Dimension *is* a Tag: an `Abstract` Tag with `Concrete` Children. > For example, `Sales Region` could be an example of an `Abstract` Tag, which has 4 `Concrete` Tag Children (`North`, `East`, `South`, `West`). {% hint style="info" %} For a more detailed explanation of Abstract and Concrete Tags, see [**here**](https://help.taglo.io/dimensions/pages/xKXxhPqflNveH4QpWCHU#abstract-vs.-concrete). {% endhint %} ## Selecting Dimensions In the Variable wizard [**Setup Step**](/variables/variable-basics/variable-setup#dimensions), you can select/create/edit any Dimensions to apply to your Variable. In the example screenshot below, the user is shown a list of Dimensions: 1. By default, the list is filtered to just show Dimensions (`Abstract` Tags) with children **(1)**. Remove this filter if you want to search through all Tags. 2. Dimensions that are already used in your Model are indicated with an asterisk, and shown at the top of the list **(2)**, for easy access.

Screenshot showing the Dimensions step of the Variables wizard — Dimension step of the Variable wizard

### Selecting repeated Dimensions You can select the same Dimension multiple times. When you do so, you will be asked to select a [**Tag Property**](/tags/advanced-tags#tag-properties) for each instance of the Dimension, as shown in the screenshot below. Each instance must have a different Tag Property selected - this enables Models to differentiate between the two instances.

Screenshot showing the Dimensions step of the Variable wizard. Two "Widget Supplier" dimensions have been selected - one has had the "From" Tag Property applied, and the other has had the "To" Tag Property applied. — Selecting repeated Dimensions

To select a Tag Property, click on the dropdown and select from an existing Tag Property, or create a new one, as shown in the screenshot below.

Screenshot showing the Tag Property dropdown control available when multiple instances of the same Dimension are selected — The Tag Property control

These Tag Properties will be visible in the Variable preview, and will indicate how the heading of each Variable item should be interpreted. In the below example, the Variable calculates the movement of customers between three suppliers - **from** each of the three suppliers, **to** each of the three suppliers. The titles of each row in Values table **(2)** can be interpreted as the "From" supplier followed by the "To" supplier, as indicated by the Dimensions description at **(1)**.

Preview of Variable with repeated Dimensions

## Creating/Editing Dimensions To create a Dimension, just add a new item to the list. Choose a name for the Dimension, and the [**Namespace**](/using-taglo-software/namespaces) the Dimension should belong to. By default, the new Dimension will be added to the same Namespace as your Model. {% hint style="info" %} When you create a new Dimension, you are actually creating a new `Abstract` [**Tag**](/tags/introduction-to-tags). You can use the Tags Application to manage Tags (and their associated Dimensions) all in one place. {% endhint %} As shown below, you can enter new Child names for your Dimension directly into the text box **(1)**, and a new `Concrete` Tag will be created for each one. You can edit existing Children by hovering over the Child, and clicking on the Edit Tag

button that appears **(2)**. This is where you can edit the Short Name property of the Tag, which is the name that will be displayed when the Child appears in your Model.

Screenshot showing the Dimension editor — Editing a Dimension

# Defining Unit Variance by Dimension How to use Dimensions with Units ## Overview When you use [**Dimensions**](/dimensions/introduction-to-dimensions) in a [**Variable**](/variables/variable-basics), you may need to specify how each part of the Variable's [**Unit**](/units/introduction-to-units) varies. > For example, in the screenshot below, our Variable has two (repeated) Dimensions replied: 1) Widget Supplier that a customer is moving **from**, and 2) Widget Supplier that a customer is moving **to**. > > In this case, the numerator (top) of the Unit refers to the "To" supplier, and the denominator (bottom) refers to the "From" supplier. The user indicates how the unit parts should vary by using the toggle controls highlighted. This means that Models can correctly infer how to create the Units for [**Assumptions** ](/assumptions/introduction-to-assumptions)and how to correctly reference Variables in [**Calculations**](/calculations/introduction-to-calculations).

Screenshot showing the Unit step of the Variable wizard, with two "Widget Supplier" dimensions applied — Selecting Unit Variance with Dimensions

# Data Types Understanding Data Types in Models ## Overview Models uses seven data types to perform calculations, described in the table below.

Data Type	Description	Link to Microsoft definition
`Double`	Double-precision floating point number (Excel default number type)	https://learn.microsoft.com/en-us/dotnet/api/system.double?view=net-8.0
`Integer`	Represents whole numbers from negative to positive 2,147,483,648 (32-bits)	https://learn.microsoft.com/en-us/dotnet/api/system.int32?view=net-8.0
`String`	Represents a text value	https://learn.microsoft.com/en-us/dotnet/api/system.string?view=net-8.0
`DateTime`	Represents a point in time	https://learn.microsoft.com/en-us/dotnet/api/system.datetime?view=net-8.0
`Date`	Represents a specific day	https://learn.microsoft.com/en-us/dotnet/api/system.dateonly?view=net-8.0
`Boolean`	Logical value (TRUE or FALSE)	https://learn.microsoft.com/en-us/dotnet/api/system.boolean?view=net-8.0
`Validation`	Represents a value from a list of choices - each value is the Child Tag of a Dimension

The default Data Type for a [**Variable**](/variables/variable-basics) is `Double`. ## Conversions Models calculates values based on the Data Type of each Variable - if you use different Data Types in your Model, values will be converted to the Data Type of their Variable. > For instance, if you have a Variable with Data Type `Integer`, which performs a Calculation based on two Variables with Data Type `Double`, the calculation will be performed with `Double` types, and then converted to an `Integer` (whole number). You should bear in mind the following notes on conversions when using multiple Data Types.

Data Type	Conversion notes
`String`	Text values cannot be converted to numerical values. An error will be shown.
`DateTime` and `Date`	See details below
`Boolean`	`TRUE` is converted to 1, and `FALSE` converted to 0 when performing calculations (e.g., 100 * TRUE = 100)
`Validation`	A `Validation` value is treated as the text value of the name of its associated Tag

### DateTime/Date treatments Both `DateTime` and `Date` are treated in the same way as Excel treats Dates (see [**here**](https://support.microsoft.com/en-us/office/datevalue-function-df8b07d4-7761-4a93-bc33-b7471bbff252#:~:text=Excel%20stores%20dates%20as%20sequential,date%20values%20to%20serial%20numbers.)), with 1st January 1900 stored as 1, with each subsequent day increasing the value by 1. Before performing calculations, Models converts Dates to serial numbers to ensure that calculations are performed identically to Excel. Models treats a `Date` as midnight at the end of the day when converting to `DateTime`.\ \ Note, that Excel has a bug (described [**here**](https://learn.microsoft.com/en-us/office/troubleshoot/excel/wrongly-assumes-1900-is-leap-year)), in which 1900 is incorrectly assumed to be a leap year. Models replicates this bug to ensure consistency with Excel. ## Comparison with Excel Excel uses a smaller set of Data Types than Models: * Number * Text * Logical (`TRUE` or `FALSE`) * Error Excel does not differentiate between `Double` and `Integer` types, so this should be taken into account when generating Excel. You will need to use a rounding function in your Model if you want to force Excel to output an `Integer`. Dates in Excel are stored as numbers, as described [**above**](#conversions). Excel does not automatically convert Logical values to 1 (`TRUE`) and 0 (`FALSE`). > For instance, if cells A1 and B1 have values TRUE and FALSE respectively, then A1 + B1 = 1, but SUM(A1, B1) = 0. > > Using an equivalent SUM formula in Models would produce the result 1; therefore, it is important, if generating Excel from Models, to check that such calculations produce the desired result. > > As a rule of thumb, applying an operator to a `TRUE`/`FALSE` value (e.g. +, \*) ensures that the value is converted to a number. # Introduction to Assumptions How Assumptions are used to store Model inputs ## Overview In [**Models**](/models/home-tab), input values are stored separately from [**Variables**](/variables/variable-basics) and their [**Calculations**](/calculations/introduction-to-calculations). This allows you to manage the inputs to your Model independently of the calculations within the Model, and to easily create variations on your inputs (through [**Scenarios**](/cases/managing-scenarios) and [**Sensitivities**](/cases/managing-sensitivities)). This separation means that you can create sets of Assumptions from scratch, without creating the Variables that will reference them, though in practice you will most often generate Assumptions from within a Variable as this is by far the fastest way to do so.

## The Assumptions Tab

Keeping Assumptions separate from Variables means you can thoroughly interrogate and quickly edit all inputs to your Model in one place. You can do this in the Assumptions Tab, where functionality includes (as per the above screenshot): * Search and Order your Assumptions with Tag filters, text search, property filters and sorting **(1)** * Directly edit Assumption [**Scenario**](/cases/managing-scenarios) values **(2)** - just click in a cell, type, and press Enter to save * Directly edit Assumption [**Sensitivity**](/cases/managing-sensitivities) values **(3)** * Visualise your assumptions in [**Charts**](/charts/introduction-to-charts) - just select any Assumptions that relate to each other, and Models will plot them on a chart which you can configure. {% hint style="info" %} Selecting a single Assumption will show you a preview including the details of that Assumptions Unit; Selecting multiple Assumptions will show you a chart (if the selected Assumptions' Units can form a valid series) {% endhint %} # Creating/Referencing Assumptions How to generate new Assumptions and reference them from Variables ## Creating Assumptions from Variables The easiest way to create new Assumptions, is from the [**Time Segments**](/variables/time-segments) of a [**Variable**](/variables/variable-basics). Any Time Segment of [**formula type**](/variables/time-segments/time-segment-setup#formula) `Assumptions` will show you how many Assumptions are required for that Time Segment, how many have been selected, and how many are valid. You will see these indicators in the Time Segment like in the screenshot below.

A Time Segment with six valid Assumptions

When a Time Segment does not have correctly selected Assumptions it will show you a warning, and you will have two options: 1. Use the **Create Missing Assumptions** shortcut (the fastest method) 2. Edit the Time Segment manually ### Create Missing Assumptions shortcut

Time Segment with six missing Assumptions

Any Time Segment with missing assumptions will show a **Create Missing Assumptions**

button, as shown in the screenshot above. {% hint style="info" %} In the above example, our Variable has two [**Dimensions**](/dimensions/introduction-to-dimensions) applied, with a total of 6 line items, and the [**Unit**](/units/introduction-to-units) is of [`Constant` **Time Type**](/units/key-unit-concepts#constants), meaning that only one Assumption is required for each item. {% endhint %} Pressing **Create Missing Assumptions** will bring up an [**Assumption value entry wizard**](/assumptions/assumptions-wizard/assumption-values-step), in which you can directly enter values. After entering the values and pressing **Finish**, an Assumption will be created for each value and added to the Time Segment. ### Time Segment Editing You can also Edit the Time Segment directly, in the Time Segment step of the Variable wizard, as in the screenshot below (1).

In the **Formula** step of the Time Segment dialog, you can select existing Assumptions for the Time Segment if they have already been created, or create new ones, as per the steps shown in the screenshot below: 1. Use the **Item Status** grid **(1)** to select the items that you want to create assumptions for - by default, all items are selected (selected items are indicated by the filter

symbol) 2. Press the **New**

button **(2)**, which will bring up an **Assumptions wizard**, in which you can enter values for the new Assumptions 3. On finishing the Assumptions dialog you will see the newly created Assumptions in the Time Segment wizard **(3)**. The Item Status grid **(4)** will now show a green background for each item, indicating that a matching Assumption is available. 4. **Select** the newly created Assumptions in the Assumptions list **(3)**, and note that each item in the Item Status Grid **(4)** now has a tick to indicate that an item has been selected. 5. Click finish

Screenshots showing the process of creating and selecting assumptions in the Time Segment wizard — Adding Assumptions in the Formula step of the Time Segment wizard

## Creating standalone Assumptions You can create Assumptions without an associated Variable. To do this, go to the **Assumptions** Tab of the Model Editor, and open a [**new Assumptions wizard**](/using-taglo-software/the-taglo-interface/adding-items). Read on to learn more about the Assumptions Wizard. # Assumptions Wizard How to use the Assumptions wizard for adding and editing assumptions ## Setup

### Name Enter a name for your Assumption. There are no restrictions to how you name your Assumptions, as long as the name isn't blank. {% hint style="info" %} Bear in mind that if you will be generating Excel from your Model, Assumption names will be written in the spreadsheet, meaning you should avoid choosing a name that Excel will interpret as a formula, otherwise you will run into problems. {% endhint %} ### Value Source Assumptions can take their value from 3 sources:

Value source	Description
`Local Input`	Manually entered values which are stored within the Model, and cannot be shared between Models
`External Data`	Values which are stored in a separate Data application; These values can be used by multiple Models
`Link to Plug-In`	Values stored in an Excel spreadsheet, which are added to the Model when generating Excel

The Assumptions wizard will update with the relevant steps according to the option chosen here. Instructions for entering data for each type of source can be found at the following locations: * [**Local Input**](/assumptions/assumptions-wizard/assumption-values-step) * [**External Data**](/assumptions/assumptions-wizard/linking-to-external-data) * [**Link to Plug-In**](/assumptions/assumptions-wizard/linking-to-excel-inserts) {% hint style="info" %} An Assumption can use different sources for each [**Scenario**](#scenarios) in the Model. e.g. you might link to External Data for the Base Scenario, and then enter Local Input values for alternative Scenarios {% endhint %} ### Dimensions Choose any [**Dimensions**](#dimensions) that you want to apply to your Assumptions. {% hint style="info" %} When editing multiple existing Assumptions, any Dimensions will be automatically detected and cannot be changed {% endhint %} ### Number Format Choose the [**Number Format**](#number-format) to apply to your Assumptions. ### Scenarios You can enter values for Assumptions for multiple [**Scenarios**](#scenarios) simultaneously. By default, the wizard will prompt you to enter values for the `Base` Scenario only, but you can select multiple Scenarios here, in which case you will need to enter values for all selected Scenarios. {% hint style="warning" %} For [**External Data**](/assumptions/assumptions-wizard/linking-to-external-data), you can only select values for one Scenario at a time. If you want to use External Data for multiple Scenarios for the same Assumption, you will need to select Data for each Scenario separately. {% endhint %} ### Data Type Choose the [**Data Type**](#data-type) for your Assumptions. ## Unit You will need to enter a [**Unit**](#unit) for your Assumptions. [**See here**](/units/defining-a-unit) for more details on how to use the Unit step of the wizard. # Assumption Dates Step How to define a Date range for Assumptions ## Overview

The Dates step of the Assumptions wizard

If creating new Assumptions manually, you will need to specify a date range for the Assumptions. By default the date range is set to the [**Timings**](/models/home-tab/creating-a-model/timings) of the Model (e.g. one Assumption per period). If the [**Unit**](/units/introduction-to-units) for your Assumptions is `Constant` (i.e. no part of the Unit varies with time), the Dates step will not be shown. {% hint style="info" %} The Dates step will only be shown when creating new Assumptions. If you are editing multiple Assumptions, the time range for the Assumptions will be automatically detected. {% endhint %} ## Entry type Dates can be entered with an **automatically generated** series of dates, or a **manually entered** list of dates. Instructions for each of these options are below. ## Date entry ### Automatically generated #### Start Date / End Date / Number of intervals Enter the Start date, number of intervals, and End date for the series. The format of date entry depends on the period type of the Model (see details [**here**](/models/home-tab/creating-a-model/timings#start-end-date-text-formats)). Editing any two of these three inputs will automatically update the third. #### Intervals between dates By default, assumptions will be generated for each period between the start date and end date. You can opt to change this interval: e.g., to generate an assumption for every fourth period, you would enter 4. ### Manual batch entry If you select **Manual batch entry**, you will be presented with a text box in which you can type/paste a list of dates, which must be in the correct format, as shown in the example screenshot below. You must include a line break in between each date.

Screenshot of the manual batch entry step used to enter multiple dates for a time series in the Assumptions wizards — Manual batch entry of dates in the Assumptions wizard

# Assumption Values Step How to enter values for Assumptions ## Overview

Screenshot showing the Assumptions Values step of the Assumptions dialog. The user is presented with a table in which they should enter values for the assumptions. 5 of the values have been entered correctly, indicated by cell formatting in the table. The last value is yet to be entered and its cell has a pink background indicating that it is not valid. — Values step of the Assumptions wizard

When creating Assumptions, either through the Assumptions wizard or [**from a Variable**](/assumptions/creating-referencing-assumptions#creating-assumptions-from-variables), you will usually enter values through the Values step interface. This presents you with a table in which you can enter a value for each Assumption. Validity of the entered data is indicated by a green/red background. ## Dimension editing

The **Dimension editing** section of the interface allows you to rearrange the order and positioning of items in the value entry table. Drag and drop the table dimensions (Time, Scenarios, Dimensions) between the Horizontal and Vertical sections to change the way in which the table is displayed. You can sort each dimension by pressing the

sort button and selecting a sort direction. In the example below, the interface shown in the [**Overview**](#overview) section above is rearranged with the `Region` dimension horizontal, and the `Membership Tier` sorted alphabetically.

Screenshot of the Assumption Values entry interface. The dimensions of the assumptions have been rearranged so that the table is in a 3x2 format rather than a 6x1 format. The Membership Tier dimension has been sorted alphabetically. — Value entry with rearranged and sorted dimensions

{% hint style="info" %} Much of the time you won't need to rearrange the value entry dimensions, but it can help enormously when you are working with a large number of Assumptions. e.g., if you are entering data across a large number of periods, we recommend moving `Time` to Vertical {% endhint %} ## Copy/Paste The value entry interface includes some functions to make it easier to copy and paste values to and from Excel, or other spreadsheets.

Button	Details
	Pastes contents of clipboard to table if possible. If pasting several values from Excel, will paste from first cell in the table. Pasting will not work if the number and position of copied values do not match the cells in the table.
	Copies just the value cells to the clipboard. If pasted to Excel, will paste in the same layout.
	Copies value cells and row/column headers to the clipboard. If pasted to Excel, will paste in the same layout.

You can also paste in values using the `Ctrl+V` shortcut. If you have copied multiple values (e.g. from Excel), values will start to be pasted from the currently selected cell. {% hint style="info" %} For a large number of assumptions, we sometimes find it easiest to use **Copy all to clipboard** to paste the entry table into Excel, edit values in Excel, and paste back to Models using **Paste Values** or **`Ctrl+V`.** {% endhint %} {% hint style="info" %} If pasting values from Excel, use [**Dimension editing**](#dimension-editing) to make the values entry layout match the layout of your data in Excel before pasting. {% endhint %} # Linking to external Data How to link Assumptions to external Data points ## Overview [**Models**](/models/home-tab) includes an application for managing commonly used [**Data**](/data/introduction-to-data), leveraging the power of [**Units**](/units/introduction-to-units) and [**Tags**](/tags/introduction-to-tags). Model Assumptions can link to this Data, which provides benefits over entering the data manually within the Model: * Values stored in Data are linked to a [**Data Source**](/data/data-sources) (a document or URL), which can be instantly opened from Models to quickly understand where values originate * Values stored in Data can be reused across multiple Models {% hint style="info" %} Read more about how to create and manage Data [**here**](/data/introduction-to-data). {% endhint %} ## External Data Step

Screenshot of the External Data page of the Assumptions wizard. — External Data step of the Assumptions wizard

From the Assumptions wizard, you can select and create new Data from which to take values. The **External Data** page presents you with a list of Data in available [**Namespaces**](/using-taglo-software/namespaces) and an **Item Status** control. In the Item Status control, you can: * **See whether Data is available** **for your Assumptions** - a **green** background indicates that one or more Data points are available * **See when Data is selected** - a

tick indicates whether an item has been selected * **Filter the list of Data to matching Units** - a

filter symbol indicates when an Assumption is an active filter - click on any cell or heading in the table to change the active filters (by default, all cells are active filters) If no matching Data is present, you can create new Data in the Data list, which will bring up a new **Data wizard**. Read more about the [**Data wizard here**](/data/creating-data). The wizard will be configured according to the filters set in the Item Status control. > For instance, in the example screenshot above, if all three cells are set as active filters, creating new Data will open a dialog with the correct Unit and Dimensions pre-populated for the three `Monthly Price per Member` assumptions. On closing the Data wizard, new Data will have been added to the list and selected. {% hint style="warning" %} When creating new Data, it is often faster to enter local values first, then convert them to Data, as described in the section [**below**](#converting-local-values-to-data) {% endhint %} ## Converting Local Values to Data

Screenshot showing a list of assumptions, with some assumptions selected. A context button is highlighted, which allows the conversion of local assumptions to external data. — Converting local values to Data

In the Assumptions list, If you select one or more Assumptions with local values, you will see a button (highlighted in the screenshot above) to convert the selected local values to Data. Pressing the button will open a new wizard in which you can: * Select which Scenarios you would like to convert to Data (only shown if more than one Scenario contains local Data) * Select a [**Data Source**](/data/data-sources) to apply to the Data Completing the wizard will create the new Data and reference it from your Assumptions. ## Converting Data to Local Values

Screenshot showing the assumptions list, with three assumptions selected. These assumptions link to external data, so a button is shown allowing the user to convert the data to local assumptions. — Converting Data to local values

The converse operation is also possible, converting Assumptions that reference external Data to local values. If you select one or more Assumptions that reference external Data (as indicated by the

arrow next to the value **(1)** ), you will see a button **(2)** to convert the Data to local values. Pressing the button will open a new wizard which will prompt you to select whether or not to delete the Data after converting. # Linking to Excel Inserts How to link Assumptions to Excel Inserts ## Overview As described in the [**Excel Inserts**](/excel-inserts-and-outputs/excel-inserts) help sections, you can connect custom Excel sheets to your generated Model, either by creating [**Outputs**](/excel-inserts-and-outputs/excel-outputs) from your Model, or by linking [**Assumptions**](/assumptions/introduction-to-assumptions) to your Inserts - this page deals with the second of these. {% hint style="info" %} Generally, we advise against linking Assumptions to Excel Inserts if it can be avoided. If your inputs are produced by a dynamic Excel model, you will not be able to control this model from within the [**Model Editor**](/models/model-editor), and there's usually a way to produce whatever inputs you need in Models! {% endhint %} ## Linking to Insert inputs Assumptions are linked to Inserts via [**Named Ranges**](https://support.microsoft.com/en-us/office/define-and-use-names-in-formulas-4d0f13ac-53b7-422e-afd2-abd7ff379c64). You will need to create a Named Range in your Insert that represents your input data, and then tell Models how to link to that Named Range. The following example illustrates this process. ### Example link to Excel Insert In this example, we have some input data for the `New members per month` Variable that we want to take from a custom Excel sheet, as shown below. The input data is in a 3x2 table, with one `Membership type` per row, and one `Region` per column. This input sheet is contained in an Excel Insert that we have already created, called `Volume Input`. To make the input data accessible from Models, we must assign a Named Range to it: in this case, we have given it the name `Input_NewMembersPerMonth`.

Section of an Excel spreadsheet, used as an Excel Insert in Models. A range of cells to be used as an input has been assigned as an Excel Named Range — **Excel Insert** with input data

To link our data to this input, we select and Edit the relevant Assumptions, as shown below.

Screenshot of the Assumptions list, with several assumptions selected, highlighting the Edit button in the preview panel — Editing Assumptions

This opens an **Assumptions dialog**. First, we change the source type to `Link to Excel Insert` (1), which results in several additional steps being shown. In the **Link to Insert** step, we choose the `Volume Input` Insert **(2)**, and the `Input_NewMembersPerMonth` Named Range **(3)**. {% hint style="warning" %} Before this point, you should ensure that the linked workbook is not open in Excel, so that Models can successfully access information about its Named Ranges. {% endhint %}

**Assumptions dialog**: Linking to Excel Insert

Once you have selected a Named Range, you then need to give Models information about the shape of the data in that Named Range. You do this by matching the layout of data in the input workbook to the displayed table in Models. In the example below, we drag the `Region` [**Dimension**](/dimensions/introduction-to-dimensions) to the Horizontal section **(4)**, which results in the correct table configuration **(5)**.

Screenshots showing how to manipulate Dimensions to correctly link to Excel Insert data inputs — **Assumptions dialog:** Matching shape of input data

Finally, we need to enter some default values for the data **(6)**, so that Models can calculate its values when it does not have access to the Excel Insert (Models will not extract data from the input workbook when re-calculating the Model). Note that in the example below, we have arranged the table with `Region` on the horizontal axis so that we can copy and paste data directly from the input workbook.

Screenshot showing Default Values page of Assumptions dialog. The user has entered values to use when the Excel Insert input is not available. — **Assumptions dialog:** Entering default values

# Sensitivity Values How to edit Assumption sensitivities ## Overview

Sensitivities step of the Assumptions dialog

Optionally, for any Assumption, you can add [**Sensitivities**](/cases/managing-sensitivities) that will vary the value of the Assumption according to certain rules. {% hint style="info" %} This is an optional step of the Assumptions wizard, and you will be able to exit from the wizard before reaching this point {% endhint %} ## Sensitivity type You can choose from one of 3 sensitivity types:

Sensitivity type	Details	Example
`Percentage change`	Varies from base value by a percentage	Base Value = 10 Sensitivity Value = +20% Used Value = 12
`Delta`	Varies from base value by an absolute amount	Base Value = 10 Sensitivity Value = 2 Used Value = 12
`Absolute`	Replaces base value with an absolute amount	Base Value = 10 Sensitivity Value = 12 Used Value = 12

{% hint style="info" %} Available Sensitivity Types will depend on [**Data Type**](/data-types/data-types) of the Assumption. For instance, `Validation` and `String` Assumptions can only have `Absolute` sensitivities. {% endhint %} ## Sensitivity value entry Add any sensitivity values to the table displayed. You do not have to enter any values, as by default, no sensitivity is applied unless specified. # Introduction to Calculations Key concepts to understand about Models Calculations ## Overview **Calculations** allow you to specify relationships between [**Variables**](/variables/variable-basics). > For instance, `Profits = Revenues - Costs` where `Profits`, `Revenues`, and `Costs` are all Variables With Calculations you can replicate most of the operations you'd perform in an Excel formula, including Date/Time, Logical, Lookup, and Mathematical functions. {% hint style="info" %} For a full list of supported Excel functions, see [**here**](/calculations/calculation-parts/functions#list-of-supported-functions) {% endhint %} ## Calculation Parts Calculations are made up of [**Calculation Parts**](/calculations/calculation-parts). When you create a Calculation, you create a list of Calculation Parts which you can rearrange and edit as in any [**list view**](/using-taglo-software/the-taglo-interface/list-views). > For example, the Calculation `SUM(Cost1, Cost2)` contains six Calculation Parts: > > * `SUM` : A Sum Function > * `(` and `)` : Opening and Closing brackets surrounding the Function content > * `Cost1` and `Cost2`: Variable References > * `,`: Comma between Function arguments You don't usually need to think about Calculation Parts as you can type a formula directly into the [**Formula Entry Bar**](/calculations/the-calculation-page/the-formula-entry-bar), which creates the associated Calculation Parts automatically. However, you can use the Calculation Part list to edit specific items (e.g. [**Variable References**](/calculations/calculation-parts/variable-references)) and quickly rearrange/edit your Calculation. # The Calculation Page Overview of the Calculation page ## The Calculation Page

Screenshot of the Calculations Page of the Variables wizard — The Calculations Page of the Variable wizard

The Calculation page of the Variable wizard has several key features, as shown in the screenshot above: 1. [**Formula Entry Bar**](/calculations/the-calculation-page/the-formula-entry-bar) 2. [**Unit analysis**](/calculations/the-calculation-page/unit-analysis) 3. [**Calculation Part**](/calculations/calculation-parts) list 4. Calculation Part preview These features are covered in the following sections # The Formula Entry Bar How to create Calculations in the Formula Entry Bar ## Overview

GIF showing a user entering a calculation into the Formula Entry bar. As the user types, a dropdown appears with the names of Variables and other items to choose from. — Formula Entry Bar example

The **Formula Entry Bar** in the Calculations step of the [**Variable**](/variables/variable-basics) dialog is the fastest way to create Calculations, by typing in a formula, similarly to how you would in Excel. ## Autocomplete Dropdown On typing any text in the Formula Entry Bar, an autocomplete dropdown will appear, as in the examples below: | Dropdown example | Details | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |

Typed in "Peri"

Brings up options for:

Adding reference to current Period
Adding reference to an existing Variable (Months per period)
Adding a reference to a new Variable named Peri
Adding a new Lambda function named Peri()

| |

Typed in "Month"

Brings up options for:

Adding a reference to two existing Variables
Adding a reference to a new Variable named Month
Adding a Function (either EOMONTH or MONTH)
Adding a new Lambda function named Month()

| Autocomplete options can be selected in any one of three ways: 1. Press **`Tab`** to select the first option in the list 2. Click on an option with the **Mouse** 3. Press **`Down`** (arrow key) to navigate through the list, and then press **`Enter`** to select an item ### Full list of Autocomplete option types

Symbol	Type	Details
	Variable Reference	Creates a reference to an existing Variable
	Reference to New Variable	Opens a wizard to create a new Variable; Adds a reference to the new Variable once created
	Period Reference	Creates a reference to a Period of the Model (a date value)
	Function	Adds a (supported) Function name and opening bracket
	Lambda function	Adds a reference to an existing LAMBDA function
	New Lambda function	Opens a wizard to create a new LAMBDA function, and then creates a reference to it
	New Argument	Applies to LET and LAMBDA functions. Creates a new argument which can be referenced in subsequent sections of the function.
	Argument Reference	Applies to LET and LAMBDA functions. References a previously defined argument.

## Referencing a new Variable The [**Taglo interface**](/using-taglo-software/the-taglo-interface) allows you to create and reference a new Variable from within another Variable's calculation, without having to leave the Variable that you are currently editing. This means you can stay within your current train of thought at all times. To do so, follow these steps: 1. Start typing a name for your new Variable in the Formula Entry Bar 2. Select the new Variable (

) autocomplete item in the dropdown 3. A new dialog will open - edit your new Variable here 4. Click Finish in the new dialog - a reference to your new Variable will be created in the formula ## Entering Text To enter text strings, type your text into the Formula Bar using a **"** character (double quotes) to indicate the start and end of the string. When you enter the second **"**, a Text [**Calculation Part**](/calculations/calculation-parts) will be created. ## Entering Numbers To enter numbers, type the number directly into the Formula Bar. Any numbers typed in will automatically be interpreted as a number. {% hint style="info" %} Generally, it is not advisable to hardcode numbers into Calculations. Try to create Variables for these numbers instead.
There are exceptions to this rule such as the hardcoded `1` in inflation formulas like `Cost = Cost[-1] * (1 + Inflation)` {% endhint %} {% hint style="warning" %} If you have a Variable name which starts as a number, this means you may not find it easy to add from the autocomplete dropdown, in which case you can use the **Add Variable Reference**

button which can be found at the end of the list of Calculation Parts. {% endhint %} # Unit Analysis How to keep track of Units when creating a Calculation ## Overview The Calculation page analyses the Unit of your Calculation as you are creating it. This helps you check your Calculation for logical consistency, and provides clues to the Unit of Variables required to finish your Calculation. The Calculation page shows two or three items:

Unit analysis item	Details
Target Unit	The Unit of the Variable in which we are creating the Calculation. Note: If you haven't defined a Unit for the Variable, this will be guessed based on context
Current Unit	The Unit currently produced by the Calculation. This item will show warning messages if a Unit cannot be determined.
Remaining Unit	The Unit required to finish the Calculation with the Target Unit. The remaining Unit will only be shown if the entered formula is empty ends in an operator (`+`, `-`, `/`, `*`).

## Worked Example In this example, we are creating a Variable called `Gym Revenues`, which is equal to `Gym members * Revenue per member`. `Gym Revenues` has a Unit of `GBP`. ### Step 1

To begin with we have an empty formula. **Target Unit** shows our desired Unit (`GBP`). **Current Unit** shows that the Calculation is not currently valid. **Remaining Unit** shows that if we reference a Variable with Unit `GBP` we will have the correct Unit. ### Step 2

We enter a reference to `Gym Members`. This updates the **Current Unit** to `Member`, and alerts us that `Member` does not match the **Target Unit** of `GBP`. We have not entered an operator, so Models cannot determine the **Remaining Unit**. ### Step 3

We enter a `*` (multiply) operator. Models can now work out that we need to reference a Variable with Unit `GBP / Member` in order to arrive at the Target Unit, as **Current Unit** \* **Remaining Unit** = **Target Unit**. At this point, if we click on the **Add Variable Reference** ![](https://2847533834-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVy65sax6FVoNo2UTlJ0x%2Fuploads%2FQdWH8BhVdevVv4g8aKN5%2Fimage.png?alt=media\&token=f04fcfc6-03dd-46a4-8003-2624e2606c8e) button in the Calculation Part list, we will be shown only Variables that match the Remaining Unit of `GBP / Member`. ### Step 4

We add a reference to the `Revenue per member` Variable, which has Unit `GBP / Member`. The **Current Unit** now matches the **Target Unit**. # Calculation Parts Overview of Calculation Parts ## List of available Calculation Parts

Calculation Part	Details
`Variable Reference`	References the value of a Variable
`Period Reference`	References the date value of a Period of the Model
`Constant`	Any numerical value
`Text`	Any text string
`Operator`	A mathematical operator: `+` `-` `*` `/` `^`
`Comparator`	A comparison operator: `<` `>` `<=` `>=` `=`
`Brackets`	Parentheses `(` `)` to indicate order of calculation or Indicate start and end of a Function
`Function`	Performs a defined Function on a set of arguments
`Comma`	Separates Function arguments
`Lambda Reference`	References a Lambda function
`Lambda Argument`	Defines an argument for use in Let and Lambda functions
`Lambda Argument Reference`	References a Lambda Argument

{% hint style="info" %} Calculations follow standard mathematical order of evaluation: Brackets > Order > Products (Division or Multiplication) > Sums (Addition or Subtraction) {% endhint %} The following sections go into detail on some of these Calculation Parts. # Variable References How to reference a Variable in a Calculation ## Creating a Variable Reference Most references to Variables are created in one of two ways:

Screenshot showing two ways of adding a reference to a Variable in a Calculation. One through the dropdown, and one through the Add Variable Reference button. — Adding a Variable Reference

1. From the [**Formula Entry Bar**](/calculations/the-calculation-page/the-formula-entry-bar), by typing a name and selecting the relevant Variable from the dropdown list **(1)**. 2. Clicking on the **Add Variable Reference** button at the bottom of the list of Calculation Parts **(2)**. The first option is great when you know the name of the Variable you want to reference, and can access it quickly via a simple text search. The second option is useful when you are unsure of the name, and want to browse through the full list of Variables, or for when you want to see a list of Variables that match the [**Remaining Unit**](/calculations/the-calculation-page/unit-analysis). When you enter a Variable using one of these methods, the default behaviour is: * The current period will be referenced * If the referenced Variable has [**Dimensions**](/dimensions/introduction-to-dimensions), Models will make its best evaluation of which item(s) should be referenced, depending on the source Variable If the default behaviour is not desired, you can configure the reference in detail to your requirements. The following sections explain the ways in which you can do this. # Referencing Time How to reference specific Periods of a Variable ## Time Offset By default Calculations reference other Variables' values from the same Period of the Model. > For instance, for a Model in Years, by default a Variable will calculate its value for 2025 by getting the values from its referenced Variables in 2025. To make most Models useful, you will need to reference previous Periods in the Model at multiple points. You can do this using a Time Offset. As shown in the example below, a Time Offset is indicated in a Calculation's formula by a negative number in square brackets (e.g., `[-1]` ) to the right of the referenced Variable name.

Example of a Calculation with a Time Offset

The number in brackets refers to the number of periods relative to the current period from which a Variable should take the referenced value. In the example above, this calculation takes the previous period's value of `Gym members`. {% hint style="info" %} If you reference a Variable from its own Calculation, it will automatically have a `[-1]` offset applied, in order to avoid circular references. {% endhint %} {% hint style="info" %} In Models, Time Offsets **must be 0 or negative**. You cannot refer to future periods. {% endhint %} ## Time Ranges By default Calculations reference a single period of a Variable. You can choose to reference multiple or specific periods of the Model using Time Ranges. As shown in the example below, Time Ranges are indicated in a Calculation's formula by a description in square brackets (e.g. `[Starts at: First period, Ends at: Last period]`).

Example of a Calculation with a Time Range

The above example calculates the cumulative revenues since the beginning of the Model. In this case, the Time Range for the `Revenues` Variable starts at the first period of the model, and ends at the current period. {% hint style="info" %} Time Ranges are particularly useful when creating [**Metrics**](/metrics/metrics), which summarise information about the Model as a whole. When you refer to a Variable from a Metric, by default it will reference the entire Model time range. {% endhint %} {% hint style="warning" %} When you use a Time Range from within a Variable, you should take care not to reference future Periods, as this will lead to Calculation errors. {% endhint %} When creating a Time Range, you can define any two of: 1. Start period 2. Duration 3. End period At least one of these parameters must be set to `Auto`. If all three are set to `Auto`, the reference will refer to the current period. #### Start/End period The Start and End periods can be defined as below:

Period type	Details
`Auto`	Refers to current period
`Fixed period`	Refers to a specific period (e.g. `June 2023`)
`Periods from start`	Refers to a period that is a defined number of periods after the start. First period = `1`
`Periods from end`	Refers to a period that is a defined number of periods before the end. Last period = `1`

#### Duration Duration can be defined as `Fill`, which will be the number of periods between the Start and End periods, or `# of Periods` (a defined number of periods). > For instance, if the Start Period is defined as the First Period, and the End Period is Auto (Current Period), the duration will be the number of periods between the first period and the current period. ## Setting the Offset and Range There are two ways of editing the Time Offset and Range. 1. Shortcut buttons in Calculation Part list 2. Calculation Part editing dialog ### Shortcut buttons

Screenshots showing how to change the time offset of a Variable reference using the shortcut buttons. — Setting an offset to the previous period using shortcuts

As in the example above, each Periods or Variable Reference Calculation Part displays a shortcut button which can be pressed to show a list of actions to change the Time Offset or Time Range. Press the **Reset** button at the bottom of the list to revert to a the default single current period reference. ### Calculation Part wizard Detailed properties of any Calculation Part can be edited through a wizard as in any [**list view**](/using-taglo-software/the-taglo-interface/previewing-and-editing#preview-actions). In the Calculation Part wizard, navigate to the **Reference Range** step, where you can edit the Offset and Range properties manually, as shown in the example below. {% hint style="info" %} The Reference Range step is only available for Variable and Period References {% endhint %}

Creating a Calculation using a Time Range reference

# Referencing Dimensions How to configure references to Dimensions ## Auto Relationships When you create a reference to a Variable that has [**Dimensions**](/dimensions/introduction-to-dimensions), Models needs to know which items within that Variable to reference when performing Calculations. Most of the time, Models can automatically work out which items to reference. For instance, in the example below, `Revenues by region and membership type` has the [**Calculation**](/calculations/introduction-to-calculations) `Gym members [Auto] * Revenue per member [Auto]`. The `[Auto]` suffix to the Variable references indicates that Models will automatically deduce the correct relationships, based on Dimensions. `Revenues by region and membership type` and `Gym members` both have two Dimensions: `Region` and `Membership Tier` - they vary both regionally and by gym package. `Revenue per member` only has one Dimension, `Membership Tier`, as the price of the gym does not vary by region. For each item of `Revenues by region and membership type`, Models will take the matching line from each of the reference Variables.

Example: Automatic Dimensions references. NOTE: Displayed values are rounded and will not produce calculated outputs shown

## Custom relationships We can configure the way that Dimensions are referenced. For example, let's say we want to create a new Variable called `Revenue if everyone is Platinum`. We use the same formula as in the example above (`Gym members * Revenue per member`), but this time we want the `Revenue per member` reference to only use the `Platinum` value. To do this, we open the Calculation Part wizard for the `Revenue per member` Variable Reference, and navigate to the **Reference type** step, as shown below:

Screenshots showing how to create a custom relationships to a Variable using the Calculation Part editor wizard — Setting a Custom Dimension relationship

In the item match dropdown, we select a **Custom** match **(1)**. A new step is displayed which allows us to customise the match for the `Membership Tier` Dimension. Here, we can specify that it should always link to the `Platinum` item **(2)**, rather than varying based on the source Variable's Dimension. This results in the desired calculation, as shown below:

Example: Custom Dimensions references. NOTE: Displayed values are rounded and will not produce calculated outputs shown

# Lookups How to create a lookup reference ## Overview Sometimes you will need to lookup a [**Variable**](/variables/variable-basics)'s value based on another Variable's value. > For instance, let's say we have a Model with four cost categories. For each cost category we want to apply one of two inflation types, RPI or CPI (Retail and Consumer Price Index respectively). We want to be able to dynamically choose between the two options, and for the cost item to use the correct inflation value automatically. This is achieved using a Lookup reference - we explain how you can achieve this below. {% hint style="info" %} This is the kind of operation you typically perform in Excel with an INDEX-MATCH formula, or an [**XLOOKUP**](https://support.microsoft.com/en-us/office/xlookup-function-b7fd680e-6d10-43e6-84f9-88eae8bf5929#:~:text=The%20XLOOKUP%20function%20searches%20a,Argument) {% endhint %} ## Lookup reference example

This above example illustrates the scenario described in the [**Overview**](#overview). `Recurring cost inflation` pulls its values from `Inflation by type` according to the selected value in `Recurring cost inflation types`. ## Creating the Lookup reference To create a Lookup reference, perform the following steps, as illustrated in the screenshots below: 1. In the [**Calculation step**](/calculations/the-calculation-page), add a Variable reference to the target Variable **(1)** (in the above example `Inflation by type`) using [**any method**](/calculations/calculation-parts/variable-references#overview) - by default, the reference will be a Summary of the target Variable, because the target has different [**Dimensions**](/dimensions/introduction-to-dimensions), so an `Auto` reference is not possible. 2. Edit the Variable Reference Calculation Part that has been added **(2)** 3. In the **Reference type** page of the dialog, select a LOOKUP reference **(3)** 4. This will display a new step, in which you can select a Variable with which to perform the LOOKUP **(4)**. This Variable will need to have the same Dimensions as the Variable in which you are performing the Calculation. By default, this list will be filtered to Variables with the correct Dimensions. {% hint style="info" %} Create the Lookup Variable by using the [**Validation data type**](/variables/variable-basics/variable-setup#validation-dimension) - in this case using `Inflation type` as the Validation Dimension. {% endhint %}

Screenshots showing the steps described in this section for creating a Lookup reference — Creating a Lookup reference

# Summarising Variables How to combine lines from Variables with Dimensions ## Overview When referencing a [**Variable**](/variables/variable-basics) with one or more [**Dimensions**](/dimensions/introduction-to-dimensions), from a Variable with different Dimensions, we can summarise the target Variable in several different ways.

Summarise method	Details
Summary Line	If the target Variable has a row summary, the value of the row summary is returned
New Summary	Creates a custom summary - you can choose which lines of the target Variable are summed together
Sum based on third Variable	Sums Variable rows together according to a categorisation made in a third Variable

{% hint style="info" %} By default, if you create a reference to a Variable which has Dimensions that do not match the Calculation Variable, a Summary Line reference will be created. If a Row Summary is not present in the target Variable, a New Summary adding together all lines of the target Variable will be created. {% endhint %} ## Referencing the Summary Line

If the target Variable already has a [**row summary**](/variables/summaries#row-summary) line, your Calculation can simply reference that summary. This is indicated by an `[All]` suffix in the Variable reference. This reference will often be created for you by default. If you need to create the reference yourself, edit the [**Calculation Part**](/calculations/calculation-parts) and select the option `Reference the SUMMARY line of the Variable` in the **Reference type** step, as shown below.

## Creating a New Summary ### Example 1

In the above example, we have created a Variable, `Platinum Revenues`, that sums together the `Platinum` items of the `Revenues by region and membership type` Variable. This is achieved by creating a **New Summary** reference, via the following steps: * Edit the Calculation Part and navigate to the **Reference type** page, as shown in the screenshot below * Select the `Create a NEW SUMMARY` option **(1)** - this displays a new Variable summary step in which you can select the desired summary options **(2)** * In this case, we need to select an option for each of the two target Dimensions, `Region` and `Membership tier`. As we are adding together the `Platinum` lines, we select **Sum** for `Region`, and `Platinum` for `Membership Tier`

### Example 2

In this example, we have created a Variable, `Revenues by region`, which has the `Region` Dimension applied, and we want to sum together all revenues for each region. To do this, we follow the same steps as in Example 1, but this time we have an option **(1)** to link the `Region` Dimension in the target Variable to the `Region` Dimension in the Calculation Variable. {% hint style="info" %} In this situation, Models would automatically generate this summary when the reference is created, as it can see that the `Region` Dimension is present in both Variables. {% endhint %}

## Summarising by a third Variable

In the example above, we have seven cost items, which we want to assign to either `Capex` or `Opex` and then automatically sum up the totals for the two types of cost. We can achieve this in a single Variable reference as follows: * Edit the Calculation Part and navigate to the **Reference type** page, as shown in the screenshot below * Select the `SUM lines together based on a third Variable` option **(1)** - this displays a new Variable selector step in which you can select the assignment Variable **(2)** * In this step, select a Variable with which to perform the assignment. This Variable will need to have the same Dimensions as the referenced Variable. By default, this list will be filtered to Variables with the correct Dimensions. {% hint style="info" %} Create the assignment Variable by using the [**Validation data type**](/variables/variable-basics/variable-setup#validation-dimension) - in this case using `Opex/Capex` as the Validation Dimension. {% endhint %}

Summarising based on a third Variable: Example steps

# Period References How to reference Periods from Calculations ## Overview If you need to use a date from your Model's [**Timings**](/models/home-tab/creating-a-model/timings) in a [**Calculation**](/calculations/introduction-to-calculations), you can do this using a Period Reference [**Calculation Part**](/calculations/calculation-parts). When you reference a period of the Model, the value returned is a representation of the number of days since 1st January 1900 at the end of the period, as explained in the [**Data Types documentation**](/data-types/data-types#datetime-date-treatments), equivalent to the treatment of dates in Excel. > For instance, if you want to calculate the number of days in a period of the Model, you would use the Calculation `Periods - Period [-1]`. This subtracts the date value at the end of the previous period from the date value at the end of the current period. ## Creating Period References There are 3 ways of creating a Period Reference: 1. Use the [**AutoComplete dropdown**](/calculations/the-calculation-page/the-formula-entry-bar#full-list-of-autocomplete-option-types) in the Formula Entry Bar (type "Periods" and select the Periods item as indicated by the clock

symbol) 2. Add a new Calculation Part, and select `Period` from the part type options 3. Use the **Periods**

shortcut button which can be found at the bottom of the Calculation Part list ## Editing Period References Periods References can reference single or multiple time periods, and reference offset periods, similarly to Variable References. See the [**Variable References documentation**](/calculations/calculation-parts/variable-references/referencing-time) for details of how to edit these. # Functions Introduction to Functions in Models ## Overview [**Models**](/models/home-tab) supports many of the Functions that you are used to using in Excel, from logical functions like `IF()` and `AND()`, to financial functions like `XNPV()` and `IRR()`.

In fact, all Models functions are Excel functions, meaning you can always generate working Excel spreadsheets from your Models. You can also create custom functions using the LET/LAMBDA features, which are explained in the [**Advanced Functions section**](/calculations/calculation-parts/functions/advanced-functions). {% hint style="info" %} Not all Excel functions are fully supported in Models. You can still use non-supported functions to generate working Excel spreadsheets, but they will not show up in the AutoComplete dropdown, and Models will not be able to calculate values. See the [**full list of supported functions below**](#list-of-supported-functions). {% endhint %} ## Entering a Function The simplest way to create a Function is to simply type the Function name in the [**Formula Entry Bar**](/calculations/the-calculation-page/the-formula-entry-bar). Typing the name followed by an opening parentheses will create the relevant [**Calculation Parts**](/calculations/calculation-parts), or you can select the Function from the [**AutoComplete dropdown**](/calculations/the-calculation-page/the-formula-entry-bar#autocomplete-dropdown) - functions are indicated by the function

symbol. As in Excel, Function arguments are separated by commas. {% hint style="warning" %} We have not yet implemented an Intellisense equivalent for Function arguments (i.e. where the user interface indicates the name and purpose of each argument). Please refer to [**Excel documentation**](https://support.microsoft.com/en-us/office/excel-functions-by-category-5f91f4e9-7b42-46d2-9bd1-63f26a86c0eb) or test the Function from within Excel to see the required arguments for an unfamiliar Function. {% endhint %} ## List of supported Functions See [**Excel documentation**](https://support.microsoft.com/en-us/office/excel-functions-by-category-5f91f4e9-7b42-46d2-9bd1-63f26a86c0eb) for full list of Excel functions.

Name	Excel Category	Microsoft Documentation
DATE	Date and time	https://support.microsoft.com/en-us/office/date-function-e36c0c8c-4104-49da-ab83-82328b832349
DAY	Date and time	https://support.microsoft.com/en-us/office/day-function-8a7d1cbb-6c7d-4ba1-8aea-25c134d03101
EDATE	Date and time	https://support.microsoft.com/en-us/office/edate-function-3c920eb2-6e66-44e7-a1f5-753ae47ee4f5
EOMONTH	Date and time	https://support.microsoft.com/en-us/office/eomonth-function-7314ffa1-2bc9-4005-9d66-f49db127d628
MONTH	Date and time	https://support.microsoft.com/en-us/office/month-function-579a2881-199b-48b2-ab90-ddba0eba86e8
WEEKDAY	Date and time	https://support.microsoft.com/en-us/office/weekday-function-60e44483-2ed1-439f-8bd0-e404c190949a
YEAR	Date and time	https://support.microsoft.com/en-us/office/year-function-c64f017a-1354-490d-981f-578e8ec8d3b9
YEARFRAC	Date and time	https://support.microsoft.com/en-us/office/yearfrac-function-3844141e-c76d-4143-82b6-208454ddc6a8
IRR	Financial	https://support.microsoft.com/en-us/office/irr-function-64925eaa-9988-495b-b290-3ad0c163c1bc
XNPV	Financial	https://support.microsoft.com/en-us/office/xnpv-function-1b42bbf6-370f-4532-a0eb-d67c16b664b7
AND	Logical	https://support.microsoft.com/en-us/office/and-function-5f19b2e8-e1df-4408-897a-ce285a19e9d9
IF	Logical	https://support.microsoft.com/en-us/office/if-function-69aed7c9-4e8a-4755-a9bc-aa8bbff73be2
IFERROR	Logical	https://support.microsoft.com/en-us/office/iferror-function-c526fd07-caeb-47b8-8bb6-63f3e417f611
NOT	Logical	https://support.microsoft.com/en-us/office/not-function-9cfc6011-a054-40c7-a140-cd4ba2d87d77
OR	Logical	https://support.microsoft.com/en-us/office/or-function-7d17ad14-8700-4281-b308-00b131e22af0
FILTER	Lookup and reference	https://support.microsoft.com/en-us/office/filter-function-f4f7cb66-82eb-4767-8f7c-4877ad80c759
INDEX	Lookup and reference	https://support.microsoft.com/en-us/office/index-function-a5dcf0dd-996d-40a4-a822-b56b061328bd
CEILING	Math and trigonometry	https://support.microsoft.com/en-us/office/ceiling-function-0a5cd7c8-0720-4f0a-bd2c-c943e510899f
CEILING.MATH	Math and trigonometry	https://support.microsoft.com/en-us/office/ceiling-math-function-80f95d2f-b499-4eee-9f16-f795a8e306c8
EXP	Math and trigonometry	https://support.microsoft.com/en-us/office/exp-function-c578f034-2c45-4c37-bc8c-329660a63abe
FLOOR	Math and trigonometry	https://support.microsoft.com/en-us/office/floor-function-14bb497c-24f2-4e04-b327-b0b4de5a8886
FLOOR.MATH	Math and trigonometry	https://support.microsoft.com/en-us/office/floor-math-function-c302b599-fbdb-4177-ba19-2c2b1249a2f5
LN	Math and trigonometry	https://support.microsoft.com/en-us/office/ln-function-81fe1ed7-dac9-4acd-ba1d-07a142c6118f
LOG	Math and trigonometry	https://support.microsoft.com/en-us/office/log-function-4e82f196-1ca9-4747-8fb0-6c4a3abb3280
MOD	Math and trigonometry	https://support.microsoft.com/en-us/office/mod-function-9b6cd169-b6ee-406a-a97b-edf2a9dc24f3
PI	Math and trigonometry	https://support.microsoft.com/en-us/office/pi-function-264199d0-a3ba-46b8-975a-c4a04608989b
POWER	Math and trigonometry	https://support.microsoft.com/en-us/office/power-function-d3f2908b-56f4-4c3f-895a-07fb519c362a
PRODUCT	Math and trigonometry	https://support.microsoft.com/en-us/office/product-function-8e6b5b24-90ee-4650-aeec-80982a0512ce
RAND	Math and trigonometry	https://support.microsoft.com/en-us/office/rand-function-4cbfa695-8869-4788-8d90-021ea9f5be73
ROUND	Math and trigonometry	https://support.microsoft.com/en-us/office/round-function-c018c5d8-40fb-4053-90b1-b3e7f61a213c
ROUNDDOWN	Math and trigonometry	https://support.microsoft.com/en-us/office/rounddown-function-2ec94c73-241f-4b01-8c6f-17e6d7968f53
ROUNDUP	Math and trigonometry	https://support.microsoft.com/en-us/office/roundup-function-f8bc9b23-e795-47db-8703-db171d0c42a7
SQRT	Math and trigonometry	https://support.microsoft.com/en-us/office/sqrt-function-654975c2-05c4-4831-9a24-2c65e4040fdf
SUM	Math and trigonometry	https://support.microsoft.com/en-us/office/sum-function-043e1c7d-7726-4e80-8f32-07b23e057f89
SUMPRODUCT	Math and trigonometry	https://support.microsoft.com/en-us/office/sumproduct-function-16753e75-9f68-4874-94ac-4d2145a2fd2e
AVERAGE	Math and trigonometry	https://support.microsoft.com/en-us/office/average-function-047bac88-d466-426c-a32b-8f33eb960cf6
MAX	Math and trigonometry	https://support.microsoft.com/en-us/office/max-function-e0012414-9ac8-4b34-9a47-73e662c08098
MIN	Math and trigonometry	https://support.microsoft.com/en-us/office/min-function-61635d12-920f-4ce2-a70f-96f202dcc152
LET	Other	https://support.microsoft.com/en-us/office/let-function-34842dd8-b92b-4d3f-b325-b8b8f9908999
LAMBDA	Other	https://support.microsoft.com/en-us/office/lambda-function-bd212d27-1cd1-4321-a34a-ccbf254b8b67

# Advanced Functions How to create custom functions using LET and LAMBDA ## Overview Microsoft has added two powerful features in recent years which effectively allow users to create custom functions. There are many benefits to using these functions, including: * Improved readability of formulas * Minimising the number of references to Calculation inputs * Making complex functions reusable To understand how LET and LAMBDA functions work, we recommend reading the Microsoft documentation. Links are included in the relevant sections below. {% hint style="warning" %} LET and LAMBDA functions are available in Office 365 versions of Excel. If you are using older versions of Excel, you can still use these functions within Models, but they will not produce working Excel spreadsheets. {% endhint %} ## LET functions {% hint style="info" %} If you are new to LET functions, first read the [**Microsoft documentation here**](https://support.microsoft.com/en-us/office/let-function-34842dd8-b92b-4d3f-b325-b8b8f9908999) {% endhint %} To create a LET function, you can type the function into the [**Formula Entry Bar**](/calculations/the-calculation-page/the-formula-entry-bar), as you would for any other function, with two key differences: **Arguments** (called "variables" in the Microsoft documentation) and **References** to those arguments must be entered via the AutoComplete dropdown. This is demonstrated in the example below.

A LET function to find a root of a quadratic equation

Let's say we want to create a LET function to find one of the roots of a quadratic equation, as shown above. This is useful as the arguments `a` and `b` are both used twice in the formula, so using a LET function means we only have to enter the input values for those arguments (which could be references to Variables) once. When we enter each of the arguments (`a`, `b`, and `c`), we type in the name of the argument and then select the Argument Calculation Part with the plus in braces symbol

from the AutoComplete dropdown, as shown below.

To reference these arguments, we type in the name of the argument, and select the Argument Reference Calculation Part with the comma in braces symbol

, as shown below.

## LAMBDA functions {% hint style="info" %} If you are new to LAMBDA functions, first read the [**Microsoft documentation here**](https://support.microsoft.com/en-us/office/lambda-function-bd212d27-1cd1-4321-a34a-ccbf254b8b67) {% endhint %} ### Creating a Lambda To create a LAMBDA function, go to the Lambda applet, which is accessible from the [**Navigation Bar**](/using-taglo-software/the-taglo-interface/navigating-in-models), or create one [**on the fly from the Formula Entry autocomplete menu**](/calculations/the-calculation-page/the-formula-entry-bar#full-list-of-autocomplete-option-types). Lambdas are stored separately from Models so can be used in any Model that has access to the Lambda's [**Namespace**](/using-taglo-software/namespaces). When you create a new Lambda you will need to perform the following steps, as per the screenshots below: * Select a Namespace * Choose a Name **(1)**. The name must obey Excel naming rules for [**Named Ranges**](https://support.microsoft.com/en-us/office/define-and-use-names-in-formulas-4d0f13ac-53b7-422e-afd2-abd7ff379c64), and not include spaces or certain special characters. The full rules are complex so we will not list them here, but the Lambda dialog will not let you proceed if the name does not meet the rules. * Create the Arguments for the function **(2)** * Enter the formula **(3)**

The Calculation entry step for a Lambda uses the same [**Formula Entry Bar**](/calculations/the-calculation-page/the-formula-entry-bar) as Variables, but with reduced capabilities (e.g. as Lambdas exist outside Models, you cannot reference Variables or Periods in a Lambda formula). {% hint style="info" %} Lambdas can reference other Lambdas - use this to greatly simplify complex calculations {% endhint %} ### Using a Lambda function Once you have created a Lambda function, it can be used in Models just like any other Function, as long as the Lambda's Namespace is available in your Model. For instance, to use the `QuadraticRoot` Lambda from the above example, we would simply type the name of the Lambda into the Formula Entry Bar, select the function from the dropdown, and enter arguments as desired, as shown below.

Using a Lambda function in a Calculation

# Introduction to Aggregation How to use Aggregation to improve Model structure ## Overview As described in the Dimensions documentation, [**Dimensions**](/dimensions/introduction-to-dimensions) allow you to improve the quality of your Models while reducing complexity, by removing repetition of Calculations. For instance, you might have several cost items in a business (e.g. Marketing, Salaries, IT, Rent) that you need to perform some common calculations on, such as working capital adjustments. To do this efficiently, it is best to have these cost items in a single [**Variable**](/variables/variable-basics), in this case using a `Cost Type` or similar Dimension. However, the individual cost items are all calculated differently (e.g. Salaries and Rent), so we cannot use the `Cost Type` Dimension for all Calculations - we need to first calculate the individual items separately, and then bring them together under one Variable. This is where we use **Aggregation**. ## Aggregation Example

The screenshot above shows the preview for a Variable using Aggregation. The Variable uses a Dimension, `Cost Type` **(1)**, with seven children (`Central staff`, `Gym staff`, etc...). The Variable has a single [**Time Segment**](/variables/time-segments) **(2)** that uses an Aggregation [**Formula**](/variables/time-segments/time-segment-setup#formula) in which the Cost Item Variables are referenced. {% hint style="success" %} Note that the [**Row Summary**](/variables/summaries#row-summary) is set to `Sum`, providing an automatic sum of the seven Variables. This is a much cleaner method of adding these Variables together than creating a dedicated Calculation: (`Central Staff` + `Gym staff + Marketing cost` + `etc...)` {% endhint %} The next section explains how to create and configure an Aggregation Variable. # Creating Aggregations How to create and configure an Aggregation ## Aggregation in the Variable wizard Aggregations are created in the [**Variable wizard**](/variables/variable-basics/variable-setup).

Screenshots of the Variable wizard, showing how to create an Aggregation — Creating an Aggregation in the Variable dialog

To create an Aggregation you will need to perform the following steps, as per the screenshots above: * Select the `Aggregation` **Variable type** **(1)** * Assign at least one [**Dimension**](/dimensions/introduction-to-dimensions) to the Variable **(2)** * Set the [**Unit**](/units/introduction-to-units) for the Variable, in the **Unit step** * In the **Aggregated Variables step**, select the Variables to be aggregated **(3)**. The **Item Statuses** table **(4)** shows which items have been selected, and can be used to filter the Variable list to matching items. {% hint style="warning" %} Selected Variables must have the correct Unit so that Models can match them correctly to the target items. The below section explains several ways to set up these Variables. {% endhint %} ## Creating Variables with the correct Unit for Aggregation Each aggregated Variable must have a Unit which has been modified to match one of the child items of the Aggregation Variable. For instance, in the above example, the Aggregation Variable (`All costs by cost type`) has a Unit of `GDP` and a Dimension of `Cost type`, which has seven children (`Central staff`, `Gym staff`, etc.). To match a `Central staff` Variable, we need a Variable with a Unit of `GDP` which has had a `Central staff` modifier applied. To match a `Gym staff` Variable, we need a Variable with a Unit of `GDP` which has had a `Gym staff` modifier applied, and so on for each item. The screenshot below shows such Units for the `Central staff` and `Gym staff` items.

Variables with modified Units for Aggregation

### Manual creation These Variables can be created manually. In this case, the Unit should be specified with appropriate modifiers added, in the **Unit step** of the Variable wizard, as demonstrated in the gif below.

GIF showing the user setting a context modifier on a unit part in the Unit page of the Variables wizard — Setting a Unit Modifier

Read [**here**](/units/key-unit-concepts#context) to understand more about Unit Modifiers. ### Automatic creation If you have not already created the Variables to be aggregated, you can automatically create them in the [**Aggregated Variables step**](#aggregation-in-the-variable-dialog) of the Variable dialog. To do so, perform the following steps, shown in the example screenshots below: * Navigate to the **Aggregated Variables step** * Select any items that you want to create in the **Item statuses** **(1)**. By default, all items will be selected. Selected items are indicated by the filter

icon. * Press the **Create selected** button **(2)** * A Variable for each item will be automatically created, each with a correctly modified Unit **(3)** * These new Variables should then be selected and edited as desired

Example of automatic aggregated Variable creation

### Aggregating Variables with Dimensions You can aggregate Variables which themselves have Dimensions, if some or all of the child items of their Dimension are present in the Aggregation Variable. The screenshot below shows an example of this feature. In this case, the `All costs by cost type` Variable references a Variable **(1)** called `Costs: Recurring`, which has the `Simple recurring cost type` Dimension applied. The `Simple recurring cost type` Dimension has four cost items as children: `Marketing cost`, `Rent`, `Equipment`, and `IT & Technology` **(2)**. Each of these four items are also present in the `Cost type` Dimension that is applied to `All costs by cost type`. Hence selecting `Costs: Recurring` means that Models is able to determine values for those four items, as indicated in the **Item statuses control ****(3)**. {% hint style="info" %} In this case, you do not need to apply any Modifiers to the Unit of `Costs: Recurring.` `Costs: Recurring` already has Unit `GBP`, and the relevant Modifiers are applied in the background by the `Simple recurring cost type` Dimension {% endhint %}

Example of an Aggregation referencing a Variable with a Dimension

# Introduction to Rearranging Why you might want to change the direction of your Calculation flows ## Overview Usually, we think about our Models in a certain "direction", based on what's most important to us. Let's say we are building a revenue forecast for our company selling widgets. The first Calculation we might think about is `Revenue = Widgets Sold * Price`, which looks like the below **(1)** in our Model:

The same Calculation might, however, just as easily be expressed as `Widgets Sold = Revenues / Price`, which would look like the below **(2)**.

The way in which we express Calculations usually depends on what we consider to be inputs and outputs of our Model. In **(1)**, we know how many widgets we are selling and what the price is, and we want to calculate the revenues generated. In **(2)**, we know the revenues and price, and want to calculate the number of widgets sold. Often, particularly when we are building Models that are a mix of **actual** and **forecast** data, what we consider to be an input and output will change over time. For instance, in our example above, we want to forecast future Revenues as an output, but we only know historic Revenues and Price, and not the number of Widgets Sold. For historic periods, therefore, we want `Revenues` and `Price` to be inputs, and in future periods, we want `Widgets Sold` and `Price` to be inputs. We can achieve this using **Rearranging**. The next section walks through an example of how to do this in Models. # Rearranging Example Worked example of Rearranging ## Setup For our forecast periods (2023 onwards), we want to calculate `Revenues` **(1)** as an output, so we start with a simple calculation, `Revenues = Widgets Sold * Price` **(2)**.

We set up our `Widgets sold` Variable so that we need to enter [**Assumptions**](/assumptions/introduction-to-assumptions) for 2021 and 2022 **(3)**, and from 2023 onwards `Widgets sold` will be equal to the previous period **(4)**. However, we don't know how many Widgets were sold in 2021 and 2022, so we cannot initially calculate `Revenues`, meaning we have blank values in our output **(5)**.

`Widgets sold` Variable before rearranging

## Entering Actual Revenues We know what our revenues were for 2021 and 2022, so we create a [**new Time Segment**](/variables/time-segments/time-segment-setup#creating-editing-time-segments) in our `Revenues` Variable **(6)**, with an `Assumptions` [**formula type**](/variables/time-segments/time-segment-setup#formula), and add our historical revenues data to this Time Segment.

`Revenues` Variable after entering Assumptions for 2021 and 2022

Models now sees that for 2021 and 2022, it is expecting input data for all three Variables, `Revenues`, `Widgets sold` and `Price`. This is not a valid state, as in any [**Calculation**](/calculations/introduction-to-calculations) there must be exactly one unknown Variable to be calculated, otherwise there is the potential for conflicts (i.e. we could enter values for the three Variables that do not match the Calculation `Revenues = Widgets sold * Price`). To rectify this, Models displays a message on the first Time Segment of `Revenues` **(7)**, warning that a "Child needs to be rearranged for this segment". We can read this as saying that one of the input Variables, `Widgets Sold` or `Price` needs to become the output of the Calculation to maintain logical consistency. ## Rearranging To rearrange the segment, we simply click the **Resolve**

button **(8)**, which opens a new dialog, shown below. We are offered a choice of child Variables to rearrange. We need to select the Variable that we want to be used as the new output of the Time Segment. In this case, we know the price, but we don't know the number of widgets sold, so we select `Widgets sold` as the new output **(9)**.

This results in the below state, where we no longer have warnings in our Variables. The first Time Segment for `Widgets sold` has been rearranged, with a Calculation of `Revenues / Price` **(10)**.

`Widgets sold` Variable after rearranging

`Widgets sold` is now calculated from `Revenues` and `Price` for 2021 and 2022, and is static thereafter. {% hint style="info" %} Note that the **Values** table visually indicates the change in calculation method with a border to the right of the 2022 period **(11)**. {% endhint %} # Rearranging Tips ## Cascading rearranged Variables In the [**previous section's**](/rearranging/rearranging-example) simple walkthrough, we only have three Variables, `Revenues`, `Widgets sold`, and `Price`. Most situations are more complex than this: for instance, take the example below, where `Widgets sold` incorporates an inflation Calculation (`Widgets sold = Widgets sold [-1] * (1 + Widget sales yearly increase)`.

We see the same warning in the `Revenues` as previously **(1)**: we need to rearrange a child. However, this time, when we rearrange `Widgets sold`, we see a similar warning in `Widgets sold`, as shown below **(2)**.

Models is telling us that now we are calculating `Widgets sold` from `Revenues` and `Price`, we cannot also calculate it from the inflation calculation. Therefore we must rearrange `Widget sales yearly increase`, which can be calculated from the actual values of `Widgets sold` in 2021 and 2022. This results in the below output with `Widget sales yearly increase` also rearranged **(3)**.

`Widget sales yearly increase` after rearranging

In this way, rearranged Variables cascade down to the "bottom" of the Model, or the point at which there are no more Calculations to rearrange. ## Reversing relationships Models allows you to quickly change the direction of calculation flows if you change the desired output of a Model. Take the below example, where we have set our Model up with `Revenue` as the output from the two input Variables, `Widgets sold` and `Price`.

If we select both **(1)** the `Revenues` Variable, and one of its child Variables (in the example above, `Widgets sold`), we are offered the option to reverse their relationship, using the **Reverse relationship** button **(2)**. This results in the below:

`Widgets sold` Variable after reversing relationship with `Revenues`

`Revenues` Variable after reversing relationship with `Widgets sold`

`Widgets sold` has been converted to a Calculation Variable with Calculation `Revenues / Price` **(3)**. `Revenues` has been converted to an Assumptions Variable where the second Time Segment is now rearranged **(4)** to its original Calculation of `Price * Widgets sold`. # Introduction to Cases How to use Scenarios and Sensitivities to test your Model ## Overview We often want to test how our [**Model**](/models/home-tab) outputs change for different values of inputs. What would be the impact of raising the price of a product? What would happen if our product launch was delayed by 6 months? To do this, we can use **Scenarios** and **Sensitivities**:

Version component	Details
Scenario	A Scenario usually reflects some kind of "alternative reality" for your Model, perhaps to reflect decisions that need to be made, and may involve significant changes. e.g. turning a revenue item on or off, or switching between insourcing and outsourcing a cost activity
Sensitivity	A Sensitivity is usually used to test how the outputs of a Model are affected by changes to the inputs, reflecting uncertainty in our assumptions. e.g. testing the impact of a range of inflation rates

Version component

Details

Scenario

A Scenario usually reflects some kind of "alternative reality" for your Model, perhaps to reflect decisions that need to be made, and may involve significant changes.

e.g. turning a revenue item on or off, or switching between insourcing and outsourcing a cost activity

Sensitivity

A Sensitivity is usually used to test how the outputs of a Model are affected by changes to the inputs, reflecting uncertainty in our assumptions.

e.g. testing the impact of a range of inflation rates

Models automatically calculates all combinations of Scenarios and Sensitivities and, unlike Excel, can easily display several Scenarios or Sensitivities simultaneously, as in the example screenshot below, enabling efficient analysis of your Model dynamics.

{% hint style="info" %} We call each combination of a Scenario and Sensitivity a **Case**. {% endhint %} ## How Scenarios and Sensitivities work in Models Scenarios and Sensitivities both affect the values of Assumptions in your Model. For each Scenario/Sensitivity in the Model, you can apply a value for each Assumption. In the below example, there are two Scenarios (`Base` and `Lean`), and three Sensitivities (`Base`, `Low`, and `High`). In this case, the `Lean` Scenario is configured to take its value from the `Base` Scenario by default, unless a value is specified for `Lean` **(1)**. This means that a value must be present in the `Base` Scenario for all Assumptions. Sensitivities do not need to have a value specified, in which case the value for the Assumption will be the unchanged Scenario value. In the case that a value is specified **(2)**, the Scenario value will be modified appropriately.

Scenario and Sensitivity values in Assumptions

The next sections explain how to set up Scenarios and Sensitivities, and the various ways in which they can be used. ## How to change active Scenario and Sensitivity [**Variable**](/variables/variable-basics) previews and [**Dashboard**](/dashboards/dashboards-basics) items will by default display values for the currently active Scenario and Sensitivity. You can change this in the Model Settings bar at the top of the [**Model Editor**](/models/model-editor). Just click on one of the Scenario or Sensitivity buttons, as shown in the screenshot below, to activate it.

Controls for changing active Scenario/Sensitivity

# Managing Scenarios How to configure Scenarios ## Scenario Wizard

Screenshots showing the Edit Scenarios button in the Model Settings ribbon, and the Scenarios wizard that opens when it is pressed. — Scenario editor

You can create Scenarios by clicking the **Edit** button **(1)** in the Scenarios section of the **Model Settings** area of the [**Model Editor**](/models/model-editor). This will open a wizard **(2)** in which you can view, edit and create Scenarios. When creating a Scenario, you can select another Scenario on which to base the new one. In the above example, the `Lean` Scenario is based on the `Base` Scenario. This means that if a value isn't specified for an Assumption for the `Lean` Scenario, its value will be taken from the `Base` Scenario. {% hint style="info" %} If you do not specify a "based on" Scenario, you will need to specify a value for every Assumption for the new Scenario {% endhint %} ## Entering Scenario values ### In the Assumptions wizard You can enter values for different Scenarios in the [**Assumptions wizard**](/assumptions/assumptions-wizard). To do so you will need to first select the Scenarios that you want to edit, in the **Setup step** **(1)**. The **Values step** will then include all selected Scenarios in the values input table **(2)**, where you can edit them freely.

Editing Scenario values in the Assumptions wizard

### In the Assumptions list You can edit Scenario values directly in the Assumptions list in the Assumptions tab of the [**Model Editor**](/models/model-editor). Just click in the value you would like to edit **(1)**, enter a new value, and press **Enter** to save. You can delete a Scenario value using the delete button **(2)**, or by deleting the value and pressing **Enter**.

Editing Scenario values in the Assumptions list

# Managing Sensitivities How to configure Sensitivities ## Sensitivity Wizard

Screenshot of the Edit Sensitivities button, and the wizard that it opens — Sensitivity Editor

You can create Sensitivities by clicking the **Edit** button **(1)** in the Sensitivities section of the **Model Settings** area of the [**Model Editor**](/models/model-editor). This will open a wizard **(2)** in which you can view, edit and create Sensitivities. When creating a Sensitivity, you can optionally select another Sensitivity on which to base the new one. In this case, the new Sensitivity would take its values from the Sensitivity on which it is based, unless a value is specified. In the above example, all Sensitivities are independent from one another. ## Editing Sensitivity values ### In the Assumptions Wizard You can edit values for Sensitivities in the [**Assumptions Wizard**](/assumptions/assumptions-wizard). In the **Sensitivities step**, you can change the way in which the Sensitivity is applied **(1)**, and add/edit Sensitivity values in the entry table **(2)**. Note that all Sensitivity values can be left blank. See the [**Sensitivity Values documentation**](/assumptions/assumptions-wizard/sensitivity-values) to understand how the different Sensitivity Types work.

Editing Sensitivity values in the Assumptions dialog

### In the Assumptions list You can edit Sensitivity values directly in the Assumptions list in the Assumptions tab of the [**Model Editor**](/models/model-editor). Just click in the value you would like to edit **(1)**, enter a new value, and press **Enter** to save. You can delete a Sensitivity value using the delete button **(2)**, or by deleting the value and pressing **Enter**.

Editing Sensitivity values in the Assumptions tab

# Generating Excel Introduction to generating Excel with Models ## Overview You can generate an Excel spreadsheet from your Model at the click of a button. These spreadsheets are: * Free of copy/paste formula errors * Neatly and consistently formatted * Fully-working and dynamic, allowing your colleagues and clients to explore your model without needing access to the Models software ## Layouts To generate Excel, you first need to create a **Layout**. The Layout tells Models where you want the various parts of your Model ([**Variables**](/variables/variable-basics), [**Assumptions**](/assumptions/introduction-to-assumptions), [**Dashboards**](/dashboards/dashboards-basics) etc.) to appear in your spreadsheet. Your Model's Layout is independent of the Calculation structure - so unlike in Excel, moving things around in the Layout can't affect any of the Calculations being performed. This means you can quickly edit the layout of your spreadsheet, without needing to worry about breaking a formula. Instead, you can focus on improving the readability of the spreadsheet, or whatever is important for your particular project. That said, you do need to make sure that you have included all components of a Calculation in the Layout for the Calculation to be performed. If your Layout is missing a part of a Calculation tree (any Variables and Assumptions on which the Calculation is dependent), the spreadsheet will still be generated, but you will see warnings where components are missing. {% hint style="info" %} You can add the same Variable to the Layout multiple times. A calculation formula will only be created in the first instance of the Variable; subsequent instances will reference the first instance. {% endhint %} {% hint style="warning" %} Currently, you can only create one Layout per Model. We may add the ability to create multiple Layouts in future updates (e.g. so that you can include/exclude parts of the Model depending on audience) - let us know if you would be interested in this feature. {% endhint %} ## Layout Views Models provides two views for examining your Excel layout, Spreadsheet view (left) and Logical view (right).

Screenshot of the two views for Excel layouts — Excel layout views

### Spreadsheet view (default) This view shows a representation of how your generated Excel will look, including all calculated values, and borders, bold/italic text (note, it does not show how the selected [**Model Theme**](/layout/excel-formatting/excel-themes-and-styles) will look). Values representing assumptions (with a green background) can be edited directly in this view. ### Logical view This view shows simplified [**Line Groups**](/layout/sheets/sheet-content#line-groups) and Variables but does not show any calculated values. This view is helpful when reorganising a sheet and allows quick rearranging of items. ## Creating your Layout Automatically Models provides an easy way of adding multiple items to the Layout in a logical fashion with just a few button clicks. Details are on the [**next page**](/layout/auto-layout). ## Creating your Layout Manually Models provides two main methods of creating and editing your Layout manually: 1. From within the **Sheets tab** of the [**Model Editor**](/models/model-editor). Here you can easily see all of the items in each [**Sheet**](/layout/sheets) and edit them directly.

Screenshot of the Sheets tab with contents of the sheet displayed in a treeview — The **Sheets tab**

2. By adding items directly to the Layout from the [**Variables**](/variables/variable-basics), [**Assumptions**](/assumptions/introduction-to-assumptions) and [**Metrics**](/metrics/metrics) tabs. Here you can add items to the Layout as you create them without needing to leave your workflow.

Screenshot of Variables list view, with "Add to sheet" buttons showing on Variable items that haven't been added to the layout. — **Add to sheet** buttons in the **Variables tab**

The next sections provide more detail of how to build and edit your Layout. # Auto Layout How to automatically add sections of your Model to the Layout ## How to use the Auto Layout feature To automatically add Variables to your Layout, simply select one or more Variables. As shown below **(1)**, you only need to select the top node of any logical tree of Variables - Models will ensure that any Variables that the selected Variable depends upon will also be added to the Layout. With the Variable selected, simply press the "Auto layout" button **(2)**. This brings up a wizard with one page

Steps 1 and 2 of using the Auto Layout feature

### The Auto Layout wizard

The Auto Layout wizard has only one mandatory field, which is the choice of **Calculations Sheet**. This is the sheet which all [**Variables**](/variables/variable-basics) within the selected node will be added to. There are several *optional* fields which can be used to change how the layout is created as follows:

Optional Field	Description
Calculations Line Group	If you want to add new content to an existing Line Group, select a Line Group here. If no Line Group is selected, new content will be added to the top level of the selected Sheet.
Assumptions Sheet	If you want to add Assumptions to a specific sheet, select one here. Otherwise Models will use the first Assumptions sheet it finds, or create one if none exists.
Assumptions Line Group	Select if you want to add new Assumptions content to an existing Line Group. If none selected, new content will be added to the top level of the selected Assumptions sheet.
Add Flags to separate sheet (toggle)	Flags are any Variable using the Boolean Data Type (i.e. with TRUE/FALSE values), often used for settings timings of Variables (e.g. start period, end period). It is often good practice to place Flags on a separate sheet from other calculations - select this option if you want to do so.
Flags Sheet	If the Add Flags to separate sheet toggle is selected, you will be prompted to choose a Sheet to add Flags to.
Flags Line Group	Select if you want to add new Flags content to an existing Line Group. If none selected, new content will be added to the top level of the selected Flags sheet.
Max levels	Sets the maximum level of nesting of groups within a Sheet. We recommend a maximum nesting of 3 for most Models - higher levels of nesting add more "structure", but make worksheets less readable.
Ideal min groups at level / Ideal max groups at level	Controls the way in which nested Line Groups are created. Models will try to ensure that Line Groups contain a number of child groups between the min and max values set here. Increasing the min groups at level setting will result in more Line Groups at higher levels, and fewer groups at lower levels.

# Sheets How to create Sheets in a Layout ## Overview Just like in Excel, Layouts in Models are divided into Sheets. Each Sheet in Models represents a sheet that will be generated in Excel. There are 5 types of Sheet that you can create:

Sheet type	Details
`Assumptions`	Contains Assumptions. All inputs to the Model will be editable from an Assumptions sheet, unless they are linked to a Dashboard or Excel Insert.
`Calculations`	Contains Variables.
`Metrics`	Contains Metrics.
`Dashboard`	Contains a Dashboard. Each Dashboard sheet can only display one Dashboard.
`Excel Insert`	Copy of a pre-built sheet from another spreadsheet (e.g. a cover sheet). Read more about Excel Inserts here.

{% hint style="info" %} You can only have one type of item (Assumptions, Variables, Metrics or Dashboards) on each Sheet in the Layout. {% endhint %} ### Auto-generated Sheets Depending on your Model, some auto-generated Sheets may be added to your Layout. For instance, if any of your Variables use Dimensions, a `Dimensions` Sheet will be added. These Sheets: * **Can** be moved * **Can** be [**hidden**](#hide-sheet-in-excel), or have their [**tab color**](#tab-color) changed * **Cannot** be deleted ## Sheet Setup page Sheets can be created directly in the **Sheets tab** of the [**Model Editor**](/models/model-editor), or from within any Sheet selector (e.g. in an **Add Item wizard**). {% hint style="info" %} Depending on the type of sheet you are creating, and which part of the UI you are creating it from, you will see different pages in the Sheet wizard. For `Dashboard` and `Excel Insert` sheets, for instance, you will see pages allowing you to choose the items to show on the sheet. {% endhint %} All sheet dialogs contain the **Setup page**, which will look similar to the below:

Screenshot of the new Sheet setup step — Sheet **Setup page**

### Sheet name Each sheet must have a name that meets Excel [**sheet name rules**](https://support.microsoft.com/en-us/office/rename-a-worksheet-3f1f7148-ee83-404d-8ef0-9ff99fbad1f9). If you enter a name that has already been used elsewhere in your Layout, Models will automatically change it. ### Sheet description (Optional) Adds a description to the Sheet when generated, shown in the top left of the sheet, as below.

### Time period (Calculation sheets only) Specifies whether the Sheet's time period is the default period of the Model (as defined in [**Timings**](/models/home-tab/creating-a-model/timings)) or an aggregated time period. If you have [**Variables**](/variables/variable-basics) that are [**aggregated**](/variables/variable-basics/variable-setup#time-period) over several time periods (e.g. in a quarterly Model, you may have a Variable that sums up totals for each year), these must be placed on a dedicated Sheet with the appropriate time period. {% hint style="warning" %} Each sheet can only show one type of time period e.g. you cannot have a Sheet that shows both quarterly and annual periods {% endhint %} ### Control sheet One Sheet in the Model must display the dropdown controls for selecting the active Scenario and Sensitivity, as shown below.

Sheet with dropdown controls for Scenario and Sensitivity

Use the toggle to specify whether this Sheet will display these controls. If you select this option on one Sheet, it will be deselected on all other Sheets. ### Group levels You can specify a number of levels to group your [**Line Groups**](/layout/sheets/sheet-content#line-groups-and-lines) by in your generated spreadsheet. By default, the value is `0`, meaning no Excel grouping is performed. {% hint style="info" %} Use grouping on large or complex Sheets to help speed up navigation of the Excel. {% endhint %}

Generated spreadsheet with 2 levels of grouping

### Hide sheet in Excel If this item is selected, the Sheet will be [**hidden**](https://support.microsoft.com/en-us/office/hide-or-unhide-worksheets-69f2701a-21f5-4186-87d7-341a8cf53344) in Excel. ### Tags You can apply [**Tags**](/tags/introduction-to-tags) to your Sheet to help search Sheets in large Layouts. ### Tab color You can select a color for your Sheet, which will be used to change the color of its tab in Excel, as shown below.

# Sheet Content What content do Sheets contain? ## Line Groups and Line Items [**Variables**](/variables/variable-basics), [**Assumptions**](/assumptions/introduction-to-assumptions) and [**Metrics**](/metrics/metrics) are all added to Sheets via [**Line Groups**](#line-groups) and [**Line Items**](#line-items).

Line Groups and Line Items in Models (left) and Excel (right)

### Line Items All Variables, Assumptions and Metrics in your Layout are represented by a Line Item. As shown in the screenshot above, when a Variable or Metric has a [**Dimension**](/dimensions/introduction-to-dimensions) applied (the Variable `Gym members` in the example), you only need to add a single item to the Layout for all child items, and the summary line, to be generated in the Excel. ### Line Groups Each [**Line Item**](#line-items) must be a child of a **Line Group**. Line Groups can be added to other Line Groups in a tree-like structure, and numbering will be automatically added, as in the example screenshots above. ## Dashboards `Dashboard` Sheets contain a reference to a single [**Dashboard**](/dashboards/dashboards-basics). In the [**Sheet wizard**](/layout/sheets#sheet-setup-step), if you select the `Dashboard` Sheet type, you will be shown a step in which you can choose a Dashboard to display. Only one Dashboard can be shown on any single Sheet. # Adding and Editing Content How to edit Sheet content ## Adding Line Items ### Adding from item lists From any [**Variables**](/variables/variable-basics), [**Assumptions**](/assumptions/introduction-to-assumptions) and [**Metrics**](/metrics/metrics) list, you can add items directly to the Layout, as shown below. An **Add to layout** button will appear **(1)** when any items are selected. An **Add to sheet** button is also available on the Variable itself **(2)** - this button will only be shown if the Variable has not been added to the Layout yet.

Screenshots showing Add to Sheet buttons in the Variables view (left) and Metrics view (right) — **Add to sheet** buttons in the **Variables** and **Metrics** tab4

Pressing one of these buttons will open an **Add Item to Layout wizard**, as shown in the screenshots below. Select a [**Sheet**](/layout/sheets) **(1)**, and a [**Line Group**](/layout/sheets/sheet-content#line-groups) to add the items to **(2)**. Line Groups can be added and edited as desired in the **Line Group step**. {% hint style="info" %} The **Sheet step** will only show Sheets of the correct item type. If you add a new Sheet here, it will automatically be of the correct type. {% endhint %}

#### Show/Hide Layout buttons If you do not want to see **Add to sheet** buttons on the Variables themselves, you can hide them from the Menu, by navigating to **View > Show Layout buttons**, as shown below.

### Adding in the Sheet preview From any Sheet preview, as shown in the screenshot below, you can add items to a Line Group by selecting the Line Group and pressing the **Add items** button.

Screenshot of a Sheet preview, with the Add Items to LineGroup button highlighted — Adding items from the Sheet preview

## Adding Line Groups From any Sheet preview, as shown in the screenshot below, you can add Line Groups by pressing the **New** button **(1)** - this will add a new Line Group to the bottom of the Sheet. If you select an existing Line Group, you can add a child Line Group directly, by pressing the **Add child group** button **(2)**.

Screenshot of a Sheet preview highlighted the New LineGroup button and the "Add Child Group" button — Adding Line Groups

### The Line Group wizard

The Line Group wizard, as shown in the screenshot above, allows you to enter a Name and some formatting options, as follows:

Formatting option	Details
Number of lines before/after header	Changes the number of blank lines inserted into the spreadsheet before and after the Line Group heading
Include header?	Specifies whether to include the header in the generated spreadsheet. In this way, you can use Line Groups to create custom spacing between items, without displaying a header.

## Editing in the Sheet preview ### Drag and Drop The Sheet preview supports drag and drop to move single or multiple Items and Line Groups. ### Line Group level controls When you hover over a Line Group, as shown in the screenshot below, buttons will appear that can be used to promote/demote the Line Group between levels.

### Item Previews A full preview for any Sheet item (Variables, Assumptions, Metrics and Dashboards) can be seen by selecting that item in the Sheet preview. Editing the item from the Sheet preview will open a full editing wizard for that item, so you can make changes without needing to navigate away. # Excel Formatting How to change the appearance of your spreadsheets ## Overview Models ensures that all of your generated spreadsheets are consistent in layout and style, and it uses formatting to provide visual indications of how the spreadsheet should be used. ### Cell styles To format cells in Excel, Models uses Excel's built-in [**Cell Styles**](https://support.microsoft.com/en-us/office/apply-create-or-remove-a-cell-style-472213bf-66bd-40c8-815c-594f0f90cd22) feature, as shown in the screenshot below.

Models adds styles to the spreadsheet and then applies these to different types of cells. Editing the style from within Excel changes all cells in the spreadsheet that have the style applied. The main styles that should be understood are listed in the table below.

Style	Details
	The value of these cells can be changed at will. Typically used for Scenario and Sensitivity dropdowns.
	Input values to the Model. These cells should typically only be updated if you have better data than is currently present.
	Cells that are linked to input values. Assumption Variables link to their Assumptions using this type of cell.
	Calculations. Most Variable cells look like this.
	A cell that links to an existing calculation. If you enter a Variable into the Layout multiple times, only the first instance will perform the calculation - subsequent instances of the Variable will link to the first one.
	Cells that should never be changed.
	Indicates a potential problem in generating the spreadsheet (e.g. linking to a Variable which has not been added to the Layout).

### Calculation formatting Models gives users clear indications of how Calculation cells can be interpreted by using separator lines, as shown below. These separator lines show how, if you were building your Model directly in Excel, you could copy/paste a formula vs. where a formula needs to be manually changed. In the example below: 1. **Time separator**: Indicates that a formula cannot be copy/pasted across this line. In this example, the formula references a previous period, so the first period uses a different formula to deal with this case. Time separators are also placed between different [**Time Segments**](/variables/time-segments). 2. **Dimension separator**: Indicates that a formula cannot be copy/pasted across this line. In this example, the `Churned members` Variable has two Dimensions, but references `Churn rate` which has a single Dimension. This means that the formula can only be copied across the first three rows, and then must be manually changed for the fourth row onwards. 3. **Summary separator**: Indicates the summary line of the Variable

{% hint style="info" %} While Models controls most of the layout of your spreadsheet, you can tailor some colors and cell formatting to your requirements - read on to find out more. {% endhint %} # Excel Themes and Styles How to style your Excel outputs ## Themes In Models, you can set a specific theme for any Model, or use a default theme, set in the [**Application Settings**](/models/home-tab/application-settings). You can create as many themes as you like. Each **Theme** comprises: 1. An [**Excel Theme File**](#excel-theme-files)**,** which sets the color scheme for your Model 2. A set of [**Styles**](#styles), which instructs Models how it should format different types of cell in your Excel output You can create and edit **Themes** in the Themes applet, accessible from the [**Navigation Bar**](/using-taglo-software/the-taglo-interface/navigating-in-models), or from any Themes picker. ### Default and Model Themes You can set the Theme for a Model in two ways: 1. Use the Default theme for all Models 2. Set a specific theme for an individual Model Default themes are set by navigating to **Edit > Edit settings**, and selecting/creating a Theme in the **Default Theme** page of the wizard. This Theme will automatically be applied to any new Models. To set a **specific theme** for a Model, in the [**Model Editor**](/models/model-editor), open the Model settings bar, and click **Edit** in the [**Model settings**](/models/model-editor#model-settings-bar) section. This will open a wizard in which you can set the Theme to be used in the Model. ### Excel Theme Files To generate spreadsheets, Models must have access to an Excel color scheme file (.xml extension). Models comes installed with a default Theme File, but you can change to a color scheme of your choosing at any time. When you create a new **Theme File** item, you will be asked to select a .xml color scheme file from your computer, which Models will copy to your data folder locally. #### Creating a .xml color scheme There are several ways of creating one of these files, including from within Excel, Word or PowerPoint. Below are the steps to create a scheme from Excel (modern versions). #### Exporting a color scheme from Excel * Open any spreadsheet in Excel * Navigate to **Page Layout > Colors** ![](https://2847533834-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVy65sax6FVoNo2UTlJ0x%2Fuploads%2FHHTlpXRQJPEbPbYJSnKf%2Fimage.png?alt=media\&token=77a4062d-e89c-42a7-bcf3-119727509b5e) * Click on **Customize Colors...** at bottom of list ![](https://2847533834-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVy65sax6FVoNo2UTlJ0x%2Fuploads%2FVjqv5F6irdxt0H3k1I1N%2Fimage.png?alt=media\&token=377569c2-223d-4082-acbf-6a339096e0a0) * Use the dialog box to edit your color scheme, enter a **Name** for it, and click **Save**

* Your color scheme will be saved as ***\[Name].xml*** in *C:\Users\\**\[Your User Name]**\AppData\Roaming\Microsoft\Templates\Document Themes\Theme Colors* ![](https://2847533834-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVy65sax6FVoNo2UTlJ0x%2Fuploads%2FOMrCglMOED1Ws0hpXCCY%2Fimage.png?alt=media\&token=455ac49c-c8fc-4184-b4e7-123a841ce9b6) ### Styles Styles allow you to select formatting options for certain types of cell in the Excel output that Models produces, such as headings, input cells and calculation cells. The **Themes** wizard shows you how each type of cell is currently formatted, and allows you to choose a color and font style. # Line Formatting How to change line formatting ## Editing line formatting After selecting one or many line items in the sheet preview, you can edit the format of the selected lines in two ways: 1. By clicking on any of the formatting controls as shown in the screenshot below. Available controls are: 1. Bold 2. Italic 3. Border Above / Border Below / Double Border Below 4. Add space above 5. Add space below 2. Clicking on the **Edit line item settings** button.

Screenshot showing the "Edit settings" buttons on the Sheet preview — **Edit line item settings** button

# Data Tables How to create Excel Data Tables ## Overview Unlike Models, Excel will only calculate one [**Case**](/cases/introduction-to-cases) of your Model at a time, and you will need to use the [**Scenario and Sensitivity**](/cases/introduction-to-cases#how-scenarios-and-sensitivities-work-in-models) controls in your spreadsheet to change Case. However, Excel [**Data Tables**](https://support.microsoft.com/en-us/office/calculate-multiple-results-by-using-a-data-table-e95e2487-6ca6-4413-ad12-77542a5ea50b) allow you to calculate results from different sets of inputs simultaneously, and display all results in one place. While this will not show you all outputs, it can be useful for comparing specific metrics over several Scenarios and Sensitivities, as shown in the example below.

A **Data Table** in Excel, generated by Models

{% hint style="info" %} Due to the limitations of Excel Data Tables, which can only respond to a single input cell, when you add a Data Table to your Layout, Scenarios and Sensitivities are combined into a list of Cases that contains all combinations. We also add a **Cases sheet** to the Layout, which contains the list of Cases. This sheet can be [**moved and hidden**](/layout/sheets#hide-sheet-in-excel) as desired. {% endhint %} ## Creating a Data Table To create a Data Table, simply go to the **Tables tab** of the [**Model Editor**](/models/model-editor) and add a new item. You will need to enter a name and choose which combinations of Cases to show. {% hint style="info" %} If you add new Scenarios and Sensitivities to the Model, these will not automatically appear in the Data Table. You will need to edit the selected Cases if you want them to be shown. {% endhint %} As shown in the screenshot below, once you have created the Data Table, you can edit it in the same way you [**edit a Sheet in the sheet preview**](/layout/sheets/adding-and-editing-content#adding-in-the-sheet-preview). In a Data Table, all sheet items are [**Metrics**](/metrics/metrics). Use [**line formatting**](/layout/excel-formatting/line-formatting) and [**group spacing**](/layout/sheets/adding-and-editing-content#the-line-group-dialog) to change the appearance of your Table.

Screenshot of a Data Table in models. — A **Data Table** in Models

## Adding a Data Table to the Layout To add a Data Table to the Layout, you must perform the following steps: 1. Add the Data Table to a [**Dashboard**](/dashboards/dashboards-basics). You must place the Data Table in the main [**Panel**](/dashboards/dashboard-layout) of the Dashboard, and the Data Table should be the only item in the Dashboard. 2. Add a Dashboard [**Sheet**](/layout/sheets) containing the Dashboard to the Layout # Excel Generation Troubleshooting Tips on what to do when Excel generation doesn't go as expected ## Overview If Models or Excel encounters a problem when generating Excel, you will be shown an error or warning message in Models with details of the issue. If this message does not provide you sufficient information to fix the issue yourself, please contact us at . ## Known issues

Issue	Details
Slow Excel generation due to offline printer	In some rare cases, Windows sees an offline printer as being connected. If this printer is the default printer, this will cause a significant delay during Excel generation due to Excel attempting to access printer's available fonts during formatting. Fix: Remove offline printer from list of printers, or set a different printer to default
Failure due to Plug-Ins with duplicate Named Ranges or Lambdas	If a Plug-In has Named Ranges or Lambdas with the same name as in the sheets generated by Models, this can cause a failure. Fix: Remove or rename conflicting Named Ranges and Lambdas

## Tips If the generation process is causing errors, or not working as expected, you can try the following:

Action Details

Refresh Models Press F5 to refresh your Model. This can sometimes solve issues with Excel generation (if this is the case, we'd appreciated it if you emailed us at support@taglo.io with details of any error messages received)

Close all Excel instances Problems can be caused by unclosed background instances of Excel. Models should never leave any instances of Excel open, but it can happen in rare cases, and Excel itself can leave background processes running.

You can manually close background Excel processes in Windows Task Manager, or use Models to do so by navigating to Menu > Excel > Close background Excel. Make sure you close/save any work in Excel before doing so.

Action	Details
Refresh Models	Press `F5` to refresh your Model. This can sometimes solve issues with Excel generation (if this is the case, we'd appreciated it if you emailed us at support@taglo.io with details of any error messages received)
Close all Excel instances	Problems can be caused by unclosed background instances of Excel. Models should never leave any instances of Excel open, but it can happen in rare cases, and Excel itself can leave background processes running. You can manually close background Excel processes in Windows Task Manager, or use Models to do so by navigating to Menu > Excel > Close background Excel. Make sure you close/save any work in Excel before doing so.

# Excel Inserts How to add custom Excel content to your spreadsheets ## Overview There may sometimes be elements of your spreadsheet that cannot be generated by [**Models**](/models/home-tab). If this is the case, you can usually achieve your desired output using Excel Inserts. Excel Inserts are just pre-built workbooks that can contain any kind of content. They may have no links to your generated Model (e.g. a simple cover sheet), or they might interact with your Model, (e.g. complex charts designed to show a specific output, or a separate Excel model that produces some inputs into your main Model). You can connect your Excel Inserts to your main Model in either direction, as shown below.

Connections from Excel Insert sheets to Models-generated sheets

Read more [**here about how to connect Assumption Values to Inserts**](/assumptions/assumptions-wizard/linking-to-excel-inserts), and in the next section about [**how to create Outputs**](/excel-inserts-and-outputs/excel-outputs) from generated sheets to your Inserts. {% hint style="info" %} We will continue to add functionality, so always check latest features before using an Excel Insert to ensure that your desired spreadsheet output cannot be achieved within Models. {% endhint %} ## Creating and managing Excel Inserts Create Inserts from the **XL Inserts tab** of the [**Model Editor**](/models/model-editor), or from any list of Inserts. In the Inserts dialog (shown below), you must select an existing Excel (.xlsx) file from disk, and enter a name.

When you create an Insert, Models creates a copy of the Excel file into your [**Taglo data directory**](/using-taglo-software/data-storage). If you want to make subsequent changes to the Excel, you will need to edit this copy. You can open it by expanding the preview of the Insert, and clicking on the name, as shown below **(1)**.

## Adding Insert sheets to your generated Excel To generate Excel including Insert sheets, you must add sheets to your [**Layout**](/layout/generating-excel). In the **new Sheet wizard**, select the `Excel Insert` sheet type to be presented with the steps as shown below. Here you can select an existing or new Excel Insert **(1)**, and then choose a sheet from the Excel file **(2)**. You can then edit the sheet details in the **Setup step ****(3)**, including sheet name and tab color.

{% hint style="info" %} If your Excel Insert has multiple sheets, you must add each one to the Layout separately. Each sheet can be independently positioned and formatted within your generated Excel. {% endhint %} # Excel Outputs How to link outputs from your generated sheets to an Excel Insert ## Overview Models allows you to link sheets from Excel Inserts to your generated Model through **Excel Outputs**. Excel Outputs work by generating Named Ranges which can be referenced by your custom Excel Inserts. (Read more about Named Ranges in the [**Microsoft documentation here**](https://support.microsoft.com/en-us/office/define-and-use-names-in-formulas-4d0f13ac-53b7-422e-afd2-abd7ff379c64)). There are several types of Output that Models allows you to create:

Output type	Details
`Variable values`	The values of a Variable across all periods of the Model (including Row Summary)
`Variable headings`	The descriptions of dimensions of a Variable (including Row Summary)
`Assumption`	The used value of an Assumption
`Timings`	The periods of the Model

Examples of `Variable values`, `Variable headings`, and `Timings` are shown in the screenshot below.

## Creating and using Excel Outputs In the **Excel Output wizard**, shown below, you must enter a name for your output that conforms to Excel Named Range [**naming rules**](https://support.microsoft.com/en-us/office/define-and-use-names-in-formulas-4d0f13ac-53b7-422e-afd2-abd7ff379c64). Choose the type of output, and the [**Variable**](/variables/variable-basics) or [**Assumption**](/assumptions/introduction-to-assumptions) to link to.

When your [**Excel is generated**](/layout/generating-excel), Models will add a Named Range for each of your Outputs, with the name given. You can set up your Excel Inserts to reference these Named Ranges, which will ensure that these references are correct regardless of where your Variables or Assumptions end up in your [**Layout**](/layout/generating-excel). {% hint style="info" %} To reference Excel Outputs in an Insert, we recommend creating your Outputs first and generating Excel. Then create your custom sheet, referencing the Named Ranges that have been created. Once you have created your custom sheets, delete all other sheets, save the custom sheets into a separate file, and turn this file into an Excel Insert. {% endhint %} # Number Formats How to manage and use Number Formats ## Overview **Number Formats** change how values are displayed to the user within the [**Models**](/models/home-tab) application, and in generated spreadsheets. > For instance, applying the Number Format `£#,##0` to the value `1234.567` would give a displayed value of `£1,235`. Number Formats in Models are closely related to [**custom Number Formats in Excel**](https://support.microsoft.com/en-us/office/number-format-codes-5026bbd6-04bc-48cd-bf33-80f18b4eae68). Any custom Number Format that is valid in Excel will be accepted in Models, though some aspects of the format (e.g. color), may not be displayed within Models. When generating Excel, all aspects of the custom format will be respected. ## Managing Number Formats Number Formats are stored separately from Models, and independent of [**Namespaces**](/using-taglo-software/namespaces), meaning they are available and can be reused across all of your Models. Models is installed with a number of inbuilt Number Formats, but you can add an unlimited number of your own, from any Number Format picker (e.g. in the [**Variable wizard**](/variables/variable-basics/variable-setup#number-format)). ## The Number Format wizard The Number Format wizard has only one step: enter a custom format. An example result of the custom format is displayed, as shown in the screenshot below. {% hint style="info" %} To see all available custom formatting rules, see the Microsoft documentation [**here**](https://support.microsoft.com/en-us/office/number-format-codes-5026bbd6-04bc-48cd-bf33-80f18b4eae68). {% endhint %}

## Default Number Format You can select a default Number Format for new Variables in a Model by navigating to [**Model Settings**](/models/model-editor#model-settings). # Dashboards Basics How to use Dashboards to visualise and test your Model ## Overview

Dashboards provide an easy way for you to visualise your Model and understand the impact of [**Assumptions**](/assumptions/introduction-to-assumptions), [**Scenarios and Sensitivities**](/cases/introduction-to-cases). Dashboards are created using a simple drag and drop interface giving you the power to quickly generate a new view of your Model. {% hint style="info" %} Metrics and Charts will show the [**currently active Case**](/cases/introduction-to-cases#how-to-change-active-scenario-and-sensitivity) by default. Charts can be configured to always show a specific Case (see [**Dashboard Charts**](/dashboards/dashboard-items) for more details). {% endhint %} ## Editing Dashboards Dashboard Items can be created and moved through a drag and drop interface, as demonstrated in the gif below.

Creating, moving, editing and deleting Dashboard items

### Creating an Item To create an Item, drag an icon from the control bar to the desired position in the Dashboard. A dialog will be opened allowing you to configure the item before it is added to the layout. ### Moving an Item To move an Item, simply drag and drop it to a different position. ### Editing and Deleting Items To edit or delete items, you must first enable editing, using the **Editing on/off** toggle on the control bar. When editing is enabled, hovering over an item will show **Edit** and **Delete** buttons. {% hint style="info" %} You can only edit or delete [**Panels**](/dashboards/dashboard-layout) when the **Show panels** toggle is set to **On**. {% endhint %} ## Dashboards in Excel You can add a Dashboard to a [**Sheet**](/layout/sheets/sheet-content#dashboards) in your [**Layout**](/layout/generating-excel), and a representation of the Dashboard will be generated for you in Excel. There are limitations to what can be produced in Excel relative to Models - these are covered in the [**Excel Dashboards**](/dashboards/excel-dashboards) page. # Dashboard Layout How to arrange items in a Dashboard ## The Items Panel All Items in a Dashboard are placed in a **Panel**, which can be oriented either horizontally or vertically. Panels can contain other Panels - in this way, you can quickly create complex and flexible layouts in your Dashboards. To view the current layout of your Panels, clock on the **Show panels** toggle in the Dashboard control bar, as shown in the screenshot below **(1)**. This will reveal outlines of the Panels, and show their directions **(2)**.

{% hint style="info" %} By default, all Dashboards are created with a single `horizontal` Panel. This Panel cannot be deleted, but its orientation can be changed. {% endhint %} ## Adding Items to Panels To add an Item to a Panel, drag a new Item from the Control bar, or an existing Item from anywhere else in the Dashboard. As shown in the screenshots below, the blue insertion indicator will tell you whether the target Panel is oriented vertically **(1)** or horizontally **(2)**.

## Adding Space You can add blank space between Items or Panels using a Spacer. To add a Spacer, drag the Spacer icon

from the control bar, and enter a height/width as desired. # Dashboard Items What Items can you show in a Dashboard? ## Overview

Item	Icon	Details
Panel		Contains other Items in a horizontal or vertical layout (see Dashboard Layout for details)
Chart		Displays a Chart of a Variable's values
Metric		Displays a Metric's name and value(s)
Assumptions		Display a table of Assumptions in which you can edit Scenario and Sensitivity values
Table		Displays a Data Table
Spacer		Adds blank space between Panels or Items

## Charts When you add a Chart to a Dashboard, you will be prompted to choose a [**Variable**](/variables/variable-basics) from which to create a Chart. By default, a Chart will be created similar to the one seen in the preview for that Variable. Just as with preview Charts, you can configure how the Chart is displayed. This is done in the **Chart settings** step of the Chart Item dialog, as shown in the screenshot below **(1)**. {% hint style="info" %} Read about configuring Chart settings [**here**](/charts/chart-customisation) {% endhint %} By default, the Chart's values will reflect the Model's active Scenario and Sensitivity. You can fix values to the Scenario and Sensitivity selected in the Chart settings control by using the **Vary with active Case** toggle **(2)**. The width of the Chart can be edited in the **Size** page of the dialog **(3)**.

## Metrics When you add a [**Metric**](/metrics/metrics) to a Dashboard, you simply need to select a Metric to display - the Metric will be formatted automatically. ## Assumptions When you add an Assumptions Table to a Dashboard, you will be prompted to select any Assumptions to display. Selected Assumptions will be displayed in a table in which values can be edited as you would edit values in the [**Assumptions tab**](/assumptions/introduction-to-assumptions#the-assumptions-tab). Assumptions can can reordered by dragging and dropping them in the table. When adding an Assumptions table, the wizard contains a page of settings (as shown below), allowing you to show or hide various columns in the table. Switching off columns can make the table narrower and allow you to view more dashboard items simultaneously.

Screenshot showing options for showing or hiding columns in a Dashboard assumptions table — Assumptions table settings

{% hint style="warning" %} Columns that are switched off in the dashboard are only hidden within Models, but will be shown in the generated Excel. {% endhint %} ## Data Table When you add a Data Table to a Dashboard, you simply need to select a Data Table to display. {% hint style="info" %} Note, currently Data Tables are not displayed in Models, only when generating in Excel. Read more about Excel Data Tables [**here**](/layout/data-tables). {% endhint %} # Excel Dashboards How to create Excel-compatible Dashboards ## Overview Excel has certain limitations which means that not everything that can be achieved with Models Dashboards can be replicated in Excel. For instance, in Models, you can add the same [**Assumption**](/assumptions/introduction-to-assumptions) to multiple Dashboards and edit the Assumption value in any of the Dashboards with no problems - the Assumption value will be updated everywhere. However, in Excel you can only edit an Assumption value in one place, so multiple Dashboards with the same Assumption cannot be generated correctly. The below section details some of rules that you will need to bear in mind for Dashboards when creating an Excel [**Layout**](/layout/generating-excel). {% hint style="info" %} Models will show you warnings in your Layout when you break these rules. {% endhint %} ## Rules for Excel

Rule	Details
Source Item must be in Layout	For a Dashboard Chart, Metric, or Assumptions Table, all associated Variables, Metrics and Assumptions must be added to a Sheet in the Layout
No repeated Assumptions	No Assumption can appear in the Dashboards of a Layout more than once
One Assumptions Table per Dashboard	Due to potential conflicts with row/column layouts, Excel Dashboard sheets can only contain one Assumptions Table
Data Tables cannot be combined with other Items	To ensure the successful operation of Data Tables in Excel, Data Tables should be in Dashboards with no other items
Charts will not be automatically aggregated over time	If you have a Chart in a Dashboard using Time Aggregation, the Chart in Excel will be shown in the default time periods of the Model. If you want a Chart with aggregated time periods in Excel, you must create a corresponding aggregated Variable first.

# Metrics How to create summary Calculations from your Model ## Overview **Metrics** are Calculations which are independent of the [**Timings**](/models/home-tab/creating-a-model/timings) of a [**Model**](/models/home-tab). Whereas a [**Variable**](/variables/variable-basics) calculates a value for each period of the Model, a Metric calculates a single value. > For instance, a Metric might be NPV (the [**Net Present Value**](https://en.wikipedia.org/wiki/Net_present_value) of all cashflows), or the number of customers at a specific point in time. ## The Metrics wizard Metrics can be created and edited in the Metrics wizard, the steps of which are described below.

Screenshots showing the two pages in the Metrics wizard — The Metrics wizard

### Setup #### Name Choose a name for your Metric. There are no restrictions to the name, as long as it is not blank. #### Dimensions Optionally choose any [**Dimensions**](/dimensions/introduction-to-dimensions) to apply to the Metric. While a Metric will only produce one value across all periods of the Model, it can have values across several child items (in the example above, the Metric produces one value per `Region`). #### Number Format Choose a [**Number Format**](/number-formats/number-formats) for the Metric. #### Data Type Choose a [**Data Type**](/data-types/data-types) for the Metric. Currently the `Validation` Data Type is not supported for Metrics. #### Tags Choose any additional [**Tags**](/tags/introduction-to-tags) to apply to your Metric for search purposes. ### Calculation Create a [**Calculation**](/calculations/introduction-to-calculations) for your Metric using the same [**Formula Entry Bar**](/calculations/the-calculation-page/the-formula-entry-bar) used in the Variable dialog. You must make sure that any Variable or Period references in a Metric Calculation [**reference specific periods**](/calculations/calculation-parts/variable-references/referencing-time) of the Model. By default, they will reference all periods of the Model (from first period to last period). # Introduction to Charts How to visualise your Calculations in Models ## Overview Every [**Variable**](/variables/variable-basics) that you create in Models is automatically visualised for you in a Chart in the [**Variable preview**](/variables/variable-basics#the-variables-preview).

Example of a Chart in a Variable preview

Similarly, if you select multiple related [**Assumptions**](/assumptions/introduction-to-assumptions), the Assumptions preview will display a chart.

Example of a Chart in an Assumptions preview

In both of these examples, the Charts can be manipulated (in terms of type of chart, information shown, time periods etc.), allowing you to dynamically investigate your Model's inputs and outputs, but these changes will be temporary, and will be lost when you select other items. To create permanent visualisations, you can use [**Dashboards**](/dashboards/dashboards-basics), in which you can view multiple charts in one place.

Example of several permanent Charts in a Dashboard

In either case, and anywhere else that you see a Models chart, the full range of chart customisations will be available to you, which you can read about in the next section. # Chart Customisation How to alter the appearance of Charts ## Chart Settings

Screenshot of a chart, showing the expanded chart settings area which contains various controls — The Chart settings area

Each chart has an expandable **Chart settings** area in which four types of changes can be made: 1. Chart type 2. Labels 3. Time 4. Fix Series Axis 5. Data shown Below, we go through each of these in turn ## Chart type

Chart type can be changed by simply selecting a new option from the **Chart Type dropdown**, as shown above. ## Labels

Labels can be added to Charts using the **Labels dropdown**, as shown above. Available Label options depends on the Chart type. ## Time

Charts aggregated over different Time Periods

You can aggregate your charts over different time periods using the **Time dropdown**, as shown above. ## Fix Series Axis If "Fix Series Axis" is selected, the dimensions of the series axis (usually y-axis) will be set such that all scenarios/sensitivities can be shown on the chart without changing the axis. This gives a more visual experience when switching between scenarios. If you want to look at an individual scenario in more detail, unselect "Fix Series Axis" and the series axis will then adjust to the best scale for just the selected scenario. ## Data Shown (Categories, Series and Filters) A Models Chart can only show two dimensions at any given time. Usually one of the dimensions shown is `Time`, typically on the X-axis, meaning that the "series" of the Chart can only vary by one other dimension. This might be a [**Dimension**](/dimensions/introduction-to-dimensions) of the Variable (or Assumptions), but it could also be the [**Scenarios**](/cases/managing-scenarios) or [**Sensitivities**](/cases/managing-sensitivities) of the Model. Any dimensions that are not chosen as Chart categories or series, must be specified as a filter. In the example below, the Variable has two Dimensions: `Region` (North, South), and `Membership tier` (Basic, Premium, Platinum). There are also two Scenarios and three Sensitivities in the Model. Here, `Time` has been chosen as the Chart's categories, and `Region` as the series **(Chart axes)**. This means that only one combination of `Membership tier`, `Sensitivities` and `Scenarios` can be shown at a time **(Chart filters)**. These are set to `Basic`, `Base`, and `Base` respectively **(Filter values),** but can be changed by the filter value dropdowns.

Chart controls for choosing which data to display

In the below example, we want to see information about the same Variable, but across both of its Dimensions, `Region` and `Membership tier`. This means we cannot keep `Time` as a dimension of the Chart; instead we use `Region` for categories, and `Membership tier` for series. This automatically makes `Time` a filter for our Chart, and we need to choose a specific date to show data for: in this case, we choose the last date of the Model, `March 2028`. Now we can see the difference between revenues across both region and membership tier simultaneously, at a given point in time.

# Importing Models How to save time and improve quality by re-using Models ## Overview [**Models**](/models/home-tab) allows you to take an existing Model, and duplicate it inside another one. In this way you can create templates for commonly re-used sections, generating huge time-savings and improving consistency of your Models. ## Importing a Model The process for importing a Model is straightforward: simply navigate through the menu to **Edit > Import Model**. This will open a wizard showing available Models to import. Select the Model you want to import, and it will be duplicated and inserted into your Model, including its Layout and Dashboards. {% hint style="info" %} Only Models within available [**Namespaces**](/using-taglo-software/namespaces) will be shown. Before importing, make sure that your Model's Namespace references the Namespace of the Model you want to import. {% endhint %} ## Replacing Variables When importing a Model, you will often want to connect it to the structure of your current Model. This can be done manually, by editing Calculations in the imported Model, but Models provides a shortcut for this process**,** the **Replace Variable** function. In the example below, we have a Variable, `Revenues` **(2)**, in our current Model, which reflects the specific revenue line of the business that we are modelling. When we import the `Financial Statements` template Model, a second placeholder `Revenues` Variable **(1)** is added. We want to override all instances of this second `Revenues` Variable with our original. To do so, we perform the following: * Select the new `Revenues` Variable * Press the **Replace** button ![](https://2847533834-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVy65sax6FVoNo2UTlJ0x%2Fuploads%2F9LT2hoWTMtyvUQubK75p%2Fimage.png?alt=media\&token=b1e2058b-5da8-4e74-9e28-6567abc8bb05) * Select the original `Revenues` Variable, and press **Finish**

All instances of the new `Revenues` Variable have now been replaced **(3)**, including in [**Dashboards**](/dashboards/dashboards-basics) and the [**Layout**](/layout/generating-excel). We can now remove the new `Revenues` Variable and associated [**Assumptions**](/assumptions/introduction-to-assumptions). {% hint style="info" %} Note that after we replace the new Variable, it appears as a top-level node in the Variable tree-view **(4)**, because it is no longer referenced by any other Variables. This tells us that it is safe to delete. {% endhint %} ## Creating Template Models You can import any Model into any other Model. However, if there are Models you want to use only as Templates, like the Financial Statements Model in the examples above, there are steps you can take to make them easier to import - we list some of these below. ### Make all Assumptions Constant Generally a template Model will have different [**Timings**](/models/home-tab/creating-a-model/timings) from the Model you want to import it into. That means it's a good idea to use a [**Constant Unit**](/units/key-unit-concepts#constants) for any Assumptions in the template Model - this way, when you import the Model, it will be immediately fully-working, regardless of the Timings of the target Model. This can be achieved in two ways: * For any Assumptions Variable that is genuinely Constant (e.g. `Number of months per year`), make sure the Unit is Constant * For any Assumptions Variable that is not Constant, but acts as a placeholder for a Variable in the target Model (e.g. `Revenues`), use a single [**Default Assumption**](/variables/default-assumptions). Default Assumptions are always of Constant Unit. {% hint style="info" %} It is not always possible to make all Assumptions Constant. For instance, if you had a template Model including a country's population over time, the population figures would reflect specific points in time. In this case, you will just need to add or remove Assumptions after importing to update the Variable in question to the Timings of the new Model. Time Segment warnings will help you determine where updates need to be made. {% endhint %} ### Make the Model independent of Interval Type A template Model may have a different [**Interval Type**](/models/home-tab/creating-a-model/timings#interval-type) from the Model you want to import it into (e.g. a template Model in `Years` imported into a Model in `Quarters`). To ensure that a template Model will work across multiple Interval Types, you should use time conversion Variables, as shown in the example below. Here, our template Model is in `Years`, but instead of just using the Variable `Years of depreciation/amortization` directly in our depreciation calculation, we first convert it into a time-generic Variable, `Periods of depreciation/amortization` using a conversion Variable of `Periods per year`. In our template Model, `Periods per year` has a constant value `1`, but if we import it into a Model with Interval Type `Months`, we can simply change the value of the `Periods per year` Assumption to `12` and our Model will work as intended.

Using time conversion Variables to make a template Model compatible with different Interval Types

# Introduction to Data Coming soon... This section will be completed soon. If you have any questions in the meantime, please email [**support@taglo.io**](mailto:support@taglo.io) # Creating Data Coming soon... This section will be completed soon. If you have any questions in the meantime, please email [**support@taglo.io**](mailto:support@taglo.io) # Data Sources Coming soon... This section will be completed soon. If you have any questions in the meantime, please email [**support@taglo.io**](mailto:support@taglo.io)