Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi, when I copy a string containing line breaks from Power Query in Power BI Desktop to Power Query in Power BI Service, I get all line breaks replaced with (#CR) and/or (#LF). Why does this happen, is there a different line break encoding between desktop and service version of Power Query? Is there a work around? It si quite annoying, as we find doing coding in the desktop version to be much more efficient than in the service version of Power Query, so copying code from desktop to the service is the natural way to go.
Eirik
Hi. That's weird. I didn't have any issues in the past. You can copy the whole table to avoid issues there like the video of guy in a cube:
https://www.youtube.com/watch?v=YWp4FKzIBxM
Hope that helps,
Happy to help!
Hi, I should have added a screen shot of the issue to explain it better. This is what I get when I press Ok in Advanced Editor with a SELECT statment containing line breaks in Power Query in a dataflow in Power BI Service:
It seems not to support regular linebreaks, but encodes them into #CR and #LF! So my question is: Is there any way to preserve normal line breaks in such a string in a dataflow in Power BI Service?
I had this same problem just now. Unsure if you managed to solve this but for myself, I've saved a dynamic date calendar table as code to paste into a Blank Query when starting a new project. This same error kept showing up until I added a "=" at the beginning of the code.
This might sound crazy but I think I have seen this issue when you are writing the blank query, the whole script is not correct (it has a syntax error or something like that) and you click the Ok or accept button. Then the engine breaks the line break with the hidden code for that like (#cf).
Be sure to copy, paste and finish the blank query with the Let and the In completely before closing the advanced editor. If it fails, it breaks.
Hope that make sense. It's not the best approach I know 😞
Happy to help!
This issue seems to alway happen, blank query, syntax error or not:
It looks like a new expected behavior 😞
I'm sorry but I don't think you can get rid of that addition in dataflows. You can suggest an idea about this:
https://ideas.powerbi.com/
You can also try opening a ticket but I think they won't say that there is an error there.
Regards,
Happy to help!
User | Count |
---|---|
47 | |
32 | |
30 | |
27 | |
25 |
User | Count |
---|---|
56 | |
55 | |
36 | |
33 | |
28 |