accoMASTERDATA

Please make Databricks a supported database tool for AccoPlanning connection

Currently accoMasterData does not support Hierachies - atleast in a visual context. Would be great to display row values in a traditional hierarchy. With the option to expand/collapse. Row Creation: Most often than not, masterdata is related to other dimensions in a hierachy setting. Example Organisation -> Employee. Currently, when creating a new Employee the employee has no relationship to the organization and the organisation must be manually entered into a measure. Idea for improvement is to enable row-creation directly within the context of the hierarchy. The idea is, if you highlight the organisation department "Sales" and click on create row (new employee), the row will be created within the Sales department. In turn, this feature could be combined with a transaction key to correctly assign the organisationKey to the newly created row.

Please add an option to paste several rows at once without having to add empty rows first.

Please add support for DAX-based validation rules. Use case: In accoMASTERDATA you can create/edit rows with dates. We would like to allow end users to only be able to add dates that are withing a specified range of dates based on the planning version start/end definition.

When loading accoMASTERDATA, it currently shows a default picture explaining how to get started with configuration of the visual. Please add support for replacing this picture with either a blank image or a custom picture to allow for better white labeling and corporate alignment.

Currently you can only create 1 row at a time. Having 25 rows that needs to be created becomes cumbersome. Please add the feature to specify how many rows to create. UX Idea is to create a dropdown when hovering the "Create Row" button. In the dropdown an option to select "Create Multiple Rows". After selection you get the option to specify number of rows. if the "Create Row" button is clicked, it should not trigger the dropdown but just create the row. This is my idea for UX - maybe there are better ideas :-)

When creating a new row in the dimension, it should be possbile to define the Unique Identifier for that row. For example a SKU-ID is often bound by characters and numbers in a composite string; "AZ105". Currently MasterData creates the row ID as "Row #44" and cannot be changed. Please make it, so we can specify the exact row ID that needs to be stored at the database. Once created, the ID should NOT be editable.

If I have multiple visuals on the same report page I would like to be able to filter by clicking on rows in multiple visuals. Like the native ctrl-click behaviour you have when using Power BI standard table visual. Also, is there any way to highlight the entire row that is selected instead of only the cell? As well as being able to edit that color.