Feedback

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.

Please add the feature to enable single selection for checkmarks. Currently only multi-selection is available. Functionality should work not in the display-state of the visual but on the table-level, in the sense that when a new category is assigned as active, all other categories are set as non-active. If the functionality is added as a display-feature, when filtering away the active category, and selecting a new category, the visual itself will have no knowledge that there is already an active category somewhere else in the underlying table. For added UX - please use the dotted-circle as UI for displaying the chechmark as a single-select option.

When defining condtion in AccoMASTERDATA / Settings / Conditions / Condition field, I can enter whatever combination I want [Field] == "T-M" [Field]== "T*M" [Field] == "T#M" ... but as soon as i try to write or copy&paste [Field] == "T&M", borders of condition field turns red and don't allow me to use "&" character.

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 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.

I have an accoMASTERDATA table with 500 rows. When I filter my accoMASTERDATA and then create a new row, the ID is taken as the max of the filtered list, but not the max of the complete list. This results in an error, since the ID that accoMASTERDATA attempts to create already exists.

When creating a new row in accoMASTERDATA with a transaction key, the transaction key is not transfered to DB. However, when updating an exsisting row, the transaction key is transfered.

Please add an option to "expand all" as default when you have grouping ( Hierarki) for columns.

When trying to create a new row, I'm faced with an error if I'm not inserting a date, despite the column being nullable in the DB. This is only an issue in the Preview version.