About Data Entry and Advanced Transaction Object (ATO)
  • 30 Apr 2025
  • 1 Minute to read
  • Dark
    Light

About Data Entry and Advanced Transaction Object (ATO)

  • Dark
    Light

Article summary

💡This article contains version changes.
Spot the light bulb icon? That means you’ll find helpful details about what’s changed across versions. Read more about version changes here.

Board provides a rich set of Data Entry features for the creation of analytical applications such as budgeting and planning models, and any simulation model and business application in general. Such models and applications usually require a high degree of interaction from end users, as they need to set assumptions, enter data and commentaries, perform calculations, and possibly review previous assumptions or modify existing values.

The Data View Object and the Flex Grid Object provide features to enter data in Cubes and manage Relationships (read the next paragraphs in this chapter).

💡 Version Changes

In version 14.2.2 and earlier, Data Entry on a Flex Grid Object is not available.

The Data View and the Flex Grid provide features that allow you to:

  • enter data directly on Cubes (numeric data, text, files, and more)

  • define validation rules in order to automatically accept or reject entered values

  • define locking rules in order to block or allow data entry on cells based on another Block values

  • assign or change the relationship between members of two hierarchically related Entities

To provide the end user an even more controlled and guided environment, you can enable the ATO Management option on a Screen or Container. This option is located in the Screen Properties panel on the right side of the Screen editing page in Design mode.

ATO management in particular allows you to:

  • give end users the ability to manually create new Entity members and manage relationships between Entities. ATO is the exact opposite of the Data Reader, which instead makes bulk and centralized changes.
    ATO is activated automatically when the Entity editor Object is added to the Screen and allows end users to execute CRUD (Create, Read, Update, Delete) actions on Entities, Entity members, and Relationships

  • control the write-back to a Cube with a Procedure. This allows you to run a Board procedure before or after saving data to a Cube, for example to calculate other values in different Cubes

You cannot enable ATO when a Screen contains a Pager Object


Was this article helpful?