Bug Reports

I have a AccoPLANNING Visual where I input text. If I write a text that consists of either Period, Comma, Dash or Slash and I leve the cell without saving and comes back a few secconds late to edit the text, AccoPLANNING randomly deletes Period, Comma, Dash and Slash from my text. IF i would write the following string: "This is a test. Pleas don't delete my Period." Leve the cell, and the reenter the cell to edit, the text would change to: "This is a test Pleas don't delete my Period." This is frustrating for the Power BI users.

When using the key parring value function on drop down, the dropdown correctly shows the value instead of the key. however when you select the value from the drop down the key is inserted into the writeback field. it would be more userfreindly if the value equally was shown in the field after beeing selected and the key was send to the database.

test

Sometimes, after entering a number in a cell and pressing return, the whole page jumps to the bottom. This doesn’t happen consistently, and I can’t figure out what triggers it.

If you set "auto size width off" in the settings and you manually drag a column width larger or smaller then the cell selection will be off - >Not fitting the right cell size.

After the update occuring at 16/17th of October 2024 to accoPLANNING v 1.0.71.2. we were unable to use the totals as input and had to do it at the cell level. Meaning that we could not type anything in the green areas in the screenshot submitted. Changing the visual to the enterprise version fixed it.

I am copying values from one column to another. However, I found that a value that was close to 0 after copying became -12 and -7. This resulted in differences between the original column and the new column. See Screanshot for details.

Hiding columns seems not working in the "Stepped Matrix", while it works correctly in the "Matrix" Layout

We are using the accoplanning power bi visual. Whenever we use the 'columns' setting we see the measure get repeated multiple times (see screenshot). This behaviour disappears when we remove the field from the 'columns' setting. However, we want to use this setting. Is this expected behaviour or a bug?