Best Of

Many other tools (e.g. Anaplan in the example below) offer the possibility to right-click on any cell of any report and "drill-through" on a table containing the history of changes for that specific record.

The MVP of this is feature:

Would be extremely valuable to increase transparency and explainability for both end-users and administrators of the system.

Currently, in Board this information is fragmented in different logs (Data Entry, Smart import, ect…) which:

• Are incomplete (there is no log reporting Dataflow and Datareader changes at the atomic level: specific coordinates, username/system admin, timestamp, Old Value/New Value, type of action (Data Entry, Data Read, Smart Import, Data Flow, …), Action identifier
• Create a dependency on the system admin or support team who are the only ones able to access and navigate these often far from clear logs

The result is that:

• End users: often perceive Board as a "Black Box" and keep excel backups as a safety measure
• Developers: With increased application complexity, it is extremely challenging to conduct root cause analysis and identify the source of bugs

The full Version of this feature:

Would allow the possibility to quickly restore previous values with one click to rectify incorrect changes at different level of granularity and perimeters

Give the possibility to Expande or Collapse all the aggregation groups with the same function present in Dataview.

Make the rows height proportional to the information you are currently viewing on the screen and if you scroll slowly between columns make the screen update accordingly.

At the moment the rows height is not changed when the user scroll slowly dataview.

The request is to allow users to choose the orientation of each page during printing (between portrait and landscape)

It would be great if there would be a button in the rows & columns function where the user can start the execution/update of his changes —> currently BOARD is loading every step you make in there - if you made a mistake (choose wrong dimension or pull it into the wrong area) the execution in the backend/running tasks is not disappearing. —> this leads sometimes in performance issues and slowly running updates or not ending tasks

If there would be a button, the user can do all his changes and when he's sure, he can run the update with clicking on this button.

Current Limitation:
When reviewing a new Data Model Package in the Transporter, there is currently no functionality to export the full list of detected changes to Excel, Notepad, or any other external format. This limitation becomes particularly problematic when dealing with a large number of changes that need to be reviewed, validated, or shared across multiple team members.

The existing review interface does not allow exporting the complete change list. Additionally, manual copying from the browser is cumbersome and unreliable, the HTML interface often resets the view or causes inconsistencies when pasting into a target file (e.g., some rows are misaligned or shifted by one column).

Proposed Enhancement:
Introduce an “Export List” feature within the Data Model Package Review screen that allows users to export the entire list of changes with a single click. The exported file could be in Excel (.xlsx) or CSV format to ensure compatibility with standard export views.

Key Benefits:

1)Enables teams to easily share change logs for review, especially when multiple stakeholders are involved.

2) Eliminates time consuming manual copying and formatting, saving effort during large transport reviews. Particularly beneficial for large updates e.g., scenarios involving hundreds of changes (such as my case with 578 modifications).

3) Reduces human error introduced during manual extraction or inconsistent copy-paste actions.

Suggested Improvement Details:

-Add an “Export to Excel/CSV” button to the Data Model Package screen.

-Ensure the export includes all change details (object type, name, action, description, etc.) exactly as displayed in the UI.

-Optional enhancement: Include filtering options prior to export (e.g., by object type or action).

Hello,

As a developer, it really time consuming to extract all the database and to reload it, all of that just for improving a max item number (for example)

There is workarround of course, clear specifically cubes concern and reload them through datareader but the work is really time consumming when the entity is used many time in cubes.

Since we can analyse which cube is link to which entity (with the analisys impact tools), I'm wondering if, by database procedure, we can not just clear cube linked to a specific entity and realod them using the clear cube step and specify 'linked to [entity]' for both (extract and reload).

It's an idea that could save a lot of time for developer.

Tell me what you think and if everything clear.

Thank you

The ability to only refresh data in procedures and on screens is great however it is a small pet peeve of mine that if you have a drill down window open you have to close the drill > refresh data > re-drill.

It would be a great feature if you could refresh the data within the drill down windown.

Use case:

Quite often I will have several tabs open, quite often one of those tabs will contain the output of a process lets say a P&L and then I have drilled down on one of the lines to say a country.

I then go and amend the numbers on a different screen in a different tab.

I then cannot view these new numbers without first closing the drill down window(s) refreshing the data and then reopening everything. It may be trivial for one drill but when you have drilled multiple times in can be even more annoying.

Currently, entities can be selected and extracted in bulk, which is a great time-saver. However, this functionality is not available for Cubes. It would be extremely helpful if Cubes also supported multi-selection extraction via the top toolbar, similar to entities.

Here’s the challenge: when an entity needs to be modified, all Cubes that include this entity must be extracted first to allow re-integration after the update. If multiple Cubes are involved, this becomes a time-consuming task, as each Cube must be extracted individually.

Introducing bulk extraction for Cubes would significantly streamline this process. The more Cubes are affected, the more time is required and this small enhancement could save users a lot of time, making workflows more efficient and productive.

We formally request the implementation of automatic text wrapping for column content in the Flexgrid object.
This feature is currently supported in the Dataview control via the column property → wrap text.