-
Field Notes: Moving Data Across Hierarchies
Featuring: Eric Laurin is a Principal Solution Architect and Community Captain
In brief: Aggregate directly when moving data up a hierarchy. For large lift-downs that are slow with Extend, mapping the data off the hierarchy and back onto the detailed Entity can be a much faster option.
A Practical Performance Lesson
In a recent project, I ran into a familiar challenge: moving data down a large Entity hierarchy was taking longer than expected. The direct calculation, moving values one level down, took more than 20 minutes. I tried mapping the data to a standalone Entity that matched the lower level, then mapping it back to the hierarchy. That sequence finished in under a minute. It was a useful reminder that, when Extend becomes a bottleneck on a large dataset, changing the route the data takes can make a dramatic difference.
I wouldn’t use this pattern automatically for every lift-down. If the standard approach performs well, it may be the simplest choice. The key is to recognize when the calculation is the source of a performance bottleneck, then choose a pattern that fits the data volume and the result you need.
Choose the Method Based on Direction and Scale
Moving data up: aggregate directly
When moving values from lower levels to higher levels, use normal aggregation. Aggregation Dataflows can process multiple relevant Entities together, and Board uses the hierarchical relationships when aligning Cubes with different structures.
Moving data down: use Extend, unless scale makes it costly
A standard lift-down uses Extend on the detailed Entity and is generally handled Entity by Entity. For modest volumes, this is often the simplest and clearest solution. If a large lift-down is taking too long, a mapping pattern may avoid the expensive Extend operation.
The “Off the Hierarchy and Back on” Pattern
The pattern moves the values through a standalone or pseudo-replicated Entity that represents the detailed level. In practical terms:
* Copy the aggregated value to a standalone Entity at the target level using a mapping Cube.
* Remove the aggregated Entity from the intermediate result.
* Add the detailed Entity through a second mapping Cube.
* Remove the standalone Entity, leaving the values aligned to the detailed hierarchy.
This replaces the costly lift-down step with simpler JOIN Dataflows that do not use Extend. In the recent case, that change reduced processing time from more than 20 minutes to less than one minute.
A Few Checks Before You Change the Design
* Confirm the calculation is moving data down the hierarchy. Moving data up is an aggregation problem and should generally be handled directly.
* Check whether Extend is actually driving the delay, and whether the data volume is large enough to justify an alternate pattern.
* Validate the mapping at each step, including how the standalone Entity represents the target-level members and how the final result aligns to the hierarchy.
* Compare both runtime and output values before adopting the change.
Takeaway
Use direct aggregation to move data up. For data moving down, start with the standard lift-down when it performs well. When Extend becomes a bottleneck on a large dataset, mapping the values off the hierarchy and back onto it can turn a slow calculation into a much faster sequence of joins.
More in this series:
Field Notes: Why Numeric Calculations Can Produce Unexpected Results
Field Notes: User-Configured Reports
Field Notes: Why Data Readiness Matters More Than Ever
-
Overcoming Common Challenges with Kevin Gough
Featuring: Kevin Gough is a Customer Success Manager and Community Captain at Board.
Kevin is back this month, sharing his insight on one of the common challenges he encounters—thinking about end users last. Involving them early is the key to success.
Listen in as Kevin shares his perspective.
https://player.vimeo.com/1190589800/34c18f157e
More in this series:
Value Realization with Kevin Gough
Long-Term Success with Board with Kristine Young
Customer Self-Sufficiency with Robin Salk
-
Field Notes: Why Numeric Calculations Can Produce Unexpected Results
Author: Community Captain Björn Reuber is a Tech Lead at Board
When working with numeric values, it is important to understand that not every decimal number can be stored exactly in a computer. In my role, I have experienced this challenge on numerous occasions.
Many systems use floating-point numbers to store numeric values. A Single precision number has approximately 6–9 significant digits of precision. This can cause unexpected results when values require more digits, or when calculations rely on an exact comparison.
Dates Stored as Numbers
A date such as 20240131 already contains eight digits.
With Single precision, large integer values cannot always be represented exactly. A value may be rounded internally to the nearest representable number. This makes Single precision unsuitable for storing dates as numeric values when the full eight-digit date representation must be preserved exactly.
Where possible, store dates using a proper Date data type rather than a numeric value.
Using Double Precision
Using Double precision reduces the risk, but it does not remove it.
A Double can store approximately 15–17 significant digits, compared with approximately 6–9 for a Single. This makes it suitable for much larger values and more precise calculations. However, Double precision still uses binary floating-point representation, so decimal values such as 0.1, 0.2, and 0.3 are usually stored as approximations.
Therefore, a calculation may still return a very small difference instead of the mathematically expected result.
Why a Result May Not Be Exactly Zero
Some decimal values, such as 0.1, cannot be represented exactly in binary floating-point format. The stored value is therefore a very close approximation.
This is often invisible in reports because the displayed value is rounded. However, it can become visible in formulas, comparisons, or data validations.
For example, in Excel:
=1-0.1-0.1-0.1-0.1-0.1-0.1-0.1-0.1-0.1-0.1
Mathematically, the result should be 0.
However, Excel may internally return a very small value, such as:
0.00000000000000014
It may be displayed as 0.00, but it is not necessarily equal to zero.
As a result, the following test can return FALSE:
=(1-0.1-0.1-0.1-0.1-0.1-0.1-0.1-0.1-0.1-0.1)=0
The Order of Calculations Can Matter
Floating-point calculations are not always associative. In other words, changing the order in which the calculation is performed can produce a slightly different result.
For example, these Excel formulas should both mathematically return zero:
=0.3-0.2-0.1
=0.3-(0.2+0.1)
However, when shown with sufficient decimal places, the first formula can result in:
-0.0000000000000000278
while the second can result in:
-0.0000000000000000555
Both values are extremely close to zero, but neither is exactly zero. The difference is caused by the internal approximations of 0.1, 0.2, and 0.3, together with the sequence in which the operations are performed.
Recommended Approach
Avoid testing floating-point results for exact equality when calculations include decimal values.
Instead of checking whether a value is exactly zero:
Result = 0
Check whether it is close enough to zero:
ABS(Result) < 0.000001
The tolerance should be selected according to the business requirement and the expected scale of the data.
For financial values, or wherever exact decimal precision is required, use an appropriate decimal or currency data type whenever available.
Floating-point numbers are efficient and suitable for many calculations. The important point is to remember that a displayed value of 0 is not always an internally stored value of exactly 0.
More from this series:
Field Notes: Practical Tips From Professional Services
Field Notes: Why Data Readiness Matters More Than Ever
Field Notes: User-Configured Reports
-
Field Notes: User-Configured Reports
Featuring: Samir Jones is a Developer - Attollo AB and Community Captain
In large-scale Board environments, managing unique reporting requirements for hundreds of users can quickly become a maintenance nightmare. As a developer, you often find yourself caught in a cycle of creating near-identical screens to satisfy slightly different user preferences for KPIs or P&L line items.
The solution? User-Configured Reports. By investing development time upfront into a dynamic framework, you can empower users to define their own reporting views while keeping your maintenance footprint at an absolute minimum.
The Core Concept: Personalization at Scale
The goal is to move away from static screen development. Instead, we provide a single, intelligent report screen where users can switch between various report types, such as Payroll, Full P&L, or Expenses, that are dynamically filtered to show only the items relevant to them.
While an Administrator sets the "Global Default," users have the autonomy to override these settings to meet their specific analytical needs.
Key Benefits
* Minimal Screen Sprawl: Theoretically, you only need one report screen to serve the entire organization, drastically reducing the complexity of your Board capsule.
* End-User Empowerment: Users can toggle the visibility of specific items and sort them in their preferred order, creating a truly bespoke experience.
* Agility for the Business: When the client needs a new report variation, they no longer have to wait for a developer. Admins or users can configure it themselves in real-time.
Technical Architecture
To implement this, you need a robust underlying data model. Here is how to structure the setup:
* Entities* Report: Create a dedicated entity for your report types. You can use a parent group if you need to categorize different types of reports.
* User & UserBoard: The solution relies on a custom selection script on the User entity (in Data Model Security). You will also need the UserBoard entity (a reflection of the User entity) to store user-specific configurations.
* Cubes: You will require two specific "SortFilter" cubes to drive the logic:* Default Cube: Structured with Report and Data Item (e.g., your P&L line items). This holds the "Master" layout.
* User-Configured Cube: Structured with Report, Data Item, and UserBoard. This stores the personalized layouts for every individual user.
* Procedures: To keep the system running smoothly, two primary procedures are necessary:* Apply Default to Users: This should be automated when adding new users. It allows Admins to push the default filter to users who have no filter or to force a global update across the organization.
When Admin is forcing the procedure, you can add an interactive selection for Report and User, to create more flexibility for Admin.
* Get Default: A self-service procedure that allows users to reset their personal view back to the Admin’s default settings.
The Frontend Experience
Admin Settings
The Administrator uses a dedicated screen to define the master layouts.
Pro Tip: When displaying the cubes in a DataView for sorting, always use at least one decimal place (e.g., 1.0, 2.0). This makes it much easier to "insert" a new item between two existing ones (e.g., 1.5) without renumbering the entire list.
Add an Entity Editor, so that the Administrator can add new Report members.
User Report Management
Users can manage their own SortFilter settings on a dedicated management screen.
User Report
The screen uses a DataView driven by these cubes configured in User Report Management.
* Selectors: Use the Report entity as a selector to let users toggle between their custom views.
* Layout Logic: In the Layout Editor, use the SortFilter cube to drive the "Filter and Sort" settings.
* Column Filtering: If you are displaying report items on columns, remember to deactivate "Show all" in the layout, as column filtering works differently than row filtering.
Setup with items on rows
Setup with items on columns
Conclusion
By shifting from "Building Reports" to "Building Reporting Frameworks," you deliver a more flexible, scalable, and professional solution to your clients. You spend less time on manual updates and more time on high-value development.
-
UX Research with Samanta Fink
Featuring: Samanta Fink is a Senior UX Researcher and Community Captain at Board.
Meet Samanta Fink and learn about how the UX Research Team's work provides customers with a unique and impactful opportunity to be part of the present and the future of Board.
Customers interested in participating can:
* Join a research session
* Contribute to the innovation of Board
* Get solutions that serve you best
https://player.vimeo.com/1225295662
More in this series:
Overcoming Common Challenges with Kristine Young
Value Realization with Kevin Gough
Customer Self-Sufficiency with Robin Salk
-
Field Notes: Why Data Readiness Matters More Than Ever
Featuring: Rob Mole is a Board Team Lead - Retail and Community Captain
Having been involved in many software implementations and Board deliveries there is one lesson that is becoming increasingly important with the ongoing interest and growing focus on AI as an asset to a business.
The foundation of a successful Board project and trusted AI adoption in the business starts with the data.
As Solution Architects, we spend a lot of time discussing models, cubes, workflows, user experiences, and now increasingly AI. Yet the most successful projects are where the organisation has invested in making its data accessible, governed, trusted, and understood before it reaches Board.
Board sits at the point where data becomes insight, planning, and decision-making. Executives consume it. Planners act on it. AI agents analyze it. But if the data arriving in Board is incomplete, inconsistent, or poorly governed, the platform simply exposes those issues faster.
There is a saying which we all know; Garbage in, garbage out. And in the era of AI adoption, the consequences of this saying are amplified. Board V15 introduces exciting opportunities with AI-powered capabilities and agents. However, AI is only as effective as the data it can access and understand.
Before an AI agent can answer a question, generate an insight, or recommend an action, it needs confidence in the underlying data. One of the most common objectives I hear at the start of a project is:
“We want a single version of the truth.”
It’s a great goal, but it doesn’t happen automatically because Board is implemented.
A single source of truth requires:
* Consistent business definitions
* Reliable source systems
* Robust integration processes
* Clear ownership
* Data governance practices
* Controlled master data
Board can become the trusted consumption layer, but the foundation must already exist or be established as part of the wider transformation program. Without this foundation, users inevitably spend more time debating the numbers than acting on them.
A guideline that can be utilized to understand data readiness as a foundation is to understand the data maturity of the organization.
Questions such as:
* Which source is authoritative?
* Is the data complete?
* Has it been validated?
* Who owns it?
* Can users trust the result?
These are data maturity questions, not technology questions.
A useful way to assess readiness is to understand where the organization sits on a data maturity spectrum.
Organizations do not need to reach the final stage before implementing Board. However, understanding the current maturity level helps identify the risks, workstreams, and investments required to maximize value from both Board and AI initiatives.
Before discussing dashboards, planning models, or AI use cases, questions to consider at project kick off for project teams to ask:
* Who owns each critical dataset?
* Which source system is authoritative?
* How is data quality measured today?
* Are business definitions agreed across departments?
* How easily can data be accessed and integrated?
* What governance processes exist?
* Can users explain where key metrics originate?
If these questions are difficult to answer, that isn’t a problem. It’s simply an indication that data readiness should become a key consideration and not ignored as a project priority, to enable a solid foundation for a successful and trusted Board delivery.
The organizations that are gaining the most value from Board, AI, and modern analytics platforms share a common characteristic: they treat data as a strategic asset, not a technical by-product.
Board can help organizations visualize, plan, analyze, and act with confidence. AI agents in v15 can accelerate decision-making and uncover new opportunities.
But both depend on trust. And trust starts with data readiness.
Successful Board implementations should begin with the question:
“How ready is our data?”
If you’re starting a Board implementation or planning your AI roadmap, and need some help or advice, take a look at Board’s Data Management and Integration best practices available on the Board Community and Board Help Portal.
Understanding data ownership, governance, integration architecture, and quality processes early in your project can significantly reduce delivery risk and accelerate value realization.
You might also like:
Field Notes: Practical Tips From Professional Services
Value Realization with Kristine Young
New Process for Accessing Board Software Installers
Like this content? Follow Rob for more from the author!
-
Value Realization with Kristine Young
Featuring: Kristine Young is a Customer Success Manager and Community Captain at Board.
Kristine returns this month to talk about value realization. Listen and learn as she talks about common behaviors that help customers continually realize and expand the value of Board over time:
* Board as a strategic platform
* Internal ownership and governance
* User engagement and enablement
* Active partnership with Customer Success team
https://player.vimeo.com/1176359478
Share your thoughts below!
More from the author
Overcoming Common Challenges with Kristine Young
Long-Term Success with Board with Kristine Young
-
Customer Self-Sufficiency with Robin Salk
Featuring: Robin Salk is a Customer Success Manager and Community Captain at Board.
Self-sufficiency helps customers move faster and make more informed decisions. When you can build reports, update models, and analyze data independently, you can respond to changing business conditions and priorities without waiting for support.
Join Robin Salk as she explores the broader benefits of self-sufficiency, including long-term scalability, greater value from your investment, and faster skill development.
https://player.vimeo.com/1209584165/2346ad5e1b?ts=15715
More in this series:
Overcoming Common Challenges
Long-Term Success with Board
Value Realization