Forum Discussion

dswinden's avatar
dswinden
Helper II
1 year ago

How to fix Text Formatting Issue after PBI Version Update (2.139.1678 64 bit)

Hello

 

Long story short, i have a semantic model that uses power query to merge dozens of external csv files into a single table.  This report has been working just fine until suddenly about Thursday last week (Coincidentally MS pushed an update on Jan 16).  Today when the scheduled refresh was set to run, i didn't get a model failure notice, however a field relationship that is used to join to tables suddenly is not working.  I can not share the pbix for confidentiality reasons, however will explain below;

 

The CSV File has an account name and address file and looks like this screenshot below.  As you can see, the csv file shows the store address on three rows. 

 

Until last week, when I would pull this CSV into PBI the address would show up as;

123 Home Road Toronto, ON T2T2T2 CAN

 

I was using that field for store address in a relationship to an internal CRM table with the same formatting.

 

Suddenly, since Thursday this address in PBI is now showing up as;

123 Home RoadToronto, ON T2T2T2CAN (Missing space before Toronto, and before CAN where the line breaks would be in the csv)

 

I have changed NOTHING in the semantic model in well over a month and yet this issue only popped up in the last 4 days which leads me to believe this is something that is included in the new version.

 

Any ideas on how to fix short of my altering source data files?

Need Help

2 Replies

  • dswinden's avatar
    dswinden
    Helper II
    1 year ago

    I suspect this is the issue, but trying to prove it currently.

     

    The csv file in my example has wrap text on.  Previous version of PBI was intepretting that line break as a space, and now it is interpretting as a Line Break (line feed or #(lf))

     

    I did a replace text step in my PQ today and was able to revert the file back to working.  But as mentioned in my post, i have changed NOTHING in the power query steps before trying to troubleshoot this issue.

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    Hi, dswinden 

    This may be a format conversion issue with the new version, and I see other users complaining that the keys don't match the table. Workaround as you said, you can add spaces in PowerQuery to get the report working again.
    Trust the team to find the problem and fix it

     

    Best Regards

    Yongkang Hua