Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
9 years ago

Frustrating Bug When Typing Visualization Sizes

Hi All,

 

I am coming across a fairly annoying issue while trying to manually enter the "General" fields on certain visualizations (X Position, Y Position, Height, Width) where if I use the backspace button the clear the field, Power BI automatically reverts back to the previous setting for that field.  There are also times where while typing new field settings, it adds what I am typing to the previous setting so that it creates an absurdly large number.  Has anyone else experienced this issue or found a way to prevent this from happening?  I am currently running on the September Power BI Desktop Update but have noticed this in previous versions as well.

 

Below is a video describing what I am talking about:

 

 

Thanks,

 

Alex

3 Replies

  • Sean's avatar
    Sean
    Community Champion

    Yes that's the way it's been - not really a bug - it seems they just don't want you to delete all numbers and leave the field blank.

     

    Gets a bit annoying when you are in a hurry...

     

    1) Highlight the whole number and then just type the new one without deleting the old one!

    or

    2) Go with backspace until you reach the first number - then type new number - then go back and delete the first digit you left from the old number!

     

    I'll grant you its annoying but I guess I've adapted - looking for other major things that we need

     

    just look at the backlog in the ideas and issues => which is where you could actually bring to their attention!

     

  • v-sihou-msft's avatar
    v-sihou-msft
    Microsoft Employee

    Anonymous

     

    I reproduced same issue as yours. It will change back to old value automatically when we use backspace to clear the field. Please submit an Issue as Sean suggested. We have reported this issue internally.

     

    Regards,

     

  • v-haibl-msft's avatar
    v-haibl-msft
    Microsoft Employee

    Anonymous

     

    The fix should be included in the November release of PBI Desktop. Please check it later.

     

    Best Regards,

    Herbert