Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Report is auto trimming text

Hi,

 

I am new to Power BI and have been trying to get a P&L statement report created.  The data I receive is already grouped in the accounts, I just need to display them in a meaningful way.  In order to distinguish between the header and detail lines in the P&L, I just added the following basic DAX:

 

PL DISPLAY = IF(PL_STRUCTURE[DISPLAY]="Detail", CONCATENATE(" ", PL_STRUCTURE[PL LINE DESC]), PL_STRUCTURE[PL LINE DESC])

The data then looks like the below in the preview window:

 

 

 

When I add it to a table though, the leading white space disappears:

 

 

I have spent a long time looking through settings in Power BI and forum posts, but couldn't find anything on Power BI auto trimming text in the reports.  During my research into creating P&L report structures I did find an example where they managed to do this (The BI Accountant).  I got a copy of their PBIX and added my data in the exact same way as before.

 

 

So it can be done, and looking through document-level settings did not show any reason for why the behaviour was different between the 2 files.  The query part was simple - load from an Excel file and do nothing else to the query.

 

Any suggestions on stopping this apparent "auto-trimming" of text in reports?

  • Hello,

    If you look through comments on the BI accountant's post related to P&L there are other people who mention this issue and the solution provided was: 'Go to the table formatting, select Values, and turn off Word Wrap.'

    Does this solve your issue?

    Regards,
    ElenaN

2 Replies

  • Hello,

    If you look through comments on the BI accountant's post related to P&L there are other people who mention this issue and the solution provided was: 'Go to the table formatting, select Values, and turn off Word Wrap.'

    Does this solve your issue?

    Regards,
    ElenaN
    • Anonymous's avatar
      Anonymous
      Not applicable

      Thank you ElenaN, that resolved the issue.  So simple, yet just not that obvious!  :smileyvery-happy: