Forum Discussion
Column width in matrix
- 10 years ago
Can you just turn off auto-sizing and manually set the width?
Can you just turn off auto-sizing and manually set the width?
- Tsanka10 years agoKudo Collector
Thanks a lot, smoupre!
Switching the auto-size option to off worked. I cannot see where one can define the width of the measure columns but for the moment it doesn't matter as the visual calculates the width correctly (in my case auto-sizing works correctly with auto-size = off :-))
I feel a bit silly as I am almost sure I have tried this before and it didn't work.
Thanks once again!
- Greg_Deckler10 years agoCommunity Champion
If you slide your mouse slowly across the column headings, you should see it change to <- ->, you should then be able to click left-mouse button and drag the column to the desired width.
With weekly updates to the service, it is difficult if not impossible to keep track of what used to be a bug and didn't work versus you just having missed that particular feature. Trust me, I find new stuff all the time and can't tell if it has been there all along or just recently added!!
- JenM10 years agoAdvocate II
Tsanka, you and I are experiencing the same two issues, which puts us in a catch-22 situation.
If you want column totals (and I've even had the problem in columns that were not totals as, just big values) to be displayed in full (not have 3 elipses...), then you need to turn off auto-sizing and adjust the widths accordingly. But if auto-sizing is off, then the matrix often doesn't respond to filtering by a slicer. Ouch! (For now, we're opting to suffer with the clipped text, as the lesser of two evils.)
Post for the other issue, for other readers:
Addendum: My font size when experiencing the problem is 10 pt or higher. When I set it to 9 pt, the auto-sizing is ok (but now my font size is smaller than I'd like.)
- Tsanka10 years agoKudo Collector
JenM, you are so right - it is a catch-22 situation. At least now thanks to Tishchenko we have a work around for the first issue.
Let's be optmistic that the powerBI team will solve the issues soon (or at least one of them). Cheers :smileyhappy: