Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Fix rendering of wrapped text in table visual, some text gets cut off

I have a problem trying to display text from user inputs that already contains line breaks in Power BI table visuals.

 

I have the Values -> Text wrap setting set to On. Most of the text values I need to display aren't super long, they just contain line breaks and empty lines for readability/structure. Usually it's just first line with main information, then a second blank line, and a thirs line with more detailed info.

 

I have created a dummy table with different versions of multi-line text, the column "Line Count" indicates the number of lines that I have put in based on line breaks. I set the horizontal gridlines to white and the max width of 10, to better show what exactly is happening.

 

This is how I would like the text to display:

jmf3_0-1749118283723.png

 

However there are other columns that I want to show, specifically a datetime column, that would show users when the different inputs were submitted. Because I didn't want to waste too much width on the timestamp, I narrowed that column so date and time would be wrapped and display on two separate lines. This causes the following issue:

jmf3_1-1749119397281.png

The third line of text on one of the rows with three lines is pushed out of the cell and you can just about see the top of it in the gridline. This behaviour seems to be related to a blank line being present in the text.

 

If I narrow the datetime column even more, so it is forced to spread over three rows, something similar happens to the five line text value instead.

jmf3_2-1749119559206.png

The exact text wrap rendering mode that is chosec/prioritised seems to also be affected by column order, because if I move the datetime column to the right of the text, all text is displayed without problems.

jmf3_3-1749119629422.png

While this last option constitutes a workaround, I do think this is a bug that should be addressed, as column order is often critical for context and for the overall table to make sense to the user.

Status: New