Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hay peeps,
I am just doing chapter 11 in the Gil Raviv as I need to do some text anaylsis and was reviewing his tips.
Step 1 is to duplicate the Message column and the rational for this is to create a lower case version.
Step 2 is to then create a conditional column to extract the key words in the exersize, from lower case to Sentance Case.
However, upon doing this and reviewing the column, the duplicated column is in fact an exact copy and the text is not in lowercase as suggested in the book.
So, has something changed since the book was relased? or is this the expected behaviour - that the column is an exact copy.
Just clarifying as this is going to create problems when following the exerice, but also I need to understand how I will do this with the actual data when I start my analysis.
Any advice greatfully recieved, I have done some searching but many posts and blogs are a fair few years old now.
Solved! Go to Solution.
I solved this issue, as I was rushing ahead and not following step by step and using different ways to get the end result (as I am confident in M and PQ) I missed the step that says to select the column and use the UI to turn all text to lowercase! Doh! (facepalm)
To convert the text in the column to lowercase, you can use the "Text.Lower" function in Power Query Editor. Here's how:
This will create a new column with the text in lowercase.
@MAwwad
Thanks for your reply, I am aware that you can convert text with M functions, I was just puzzled by the exercise in the book.
The book states:
"Because Power Query is case sensitive in searches, in the following steps you will duplicate the Message column and work on the duplicate copy, where all the text is lowercase. You will keep the original messages intact for cases in which you should include the original text in your report to maintain the specific uppercased characters in the messages." Chapter 11 pp 279
So I was a little perplexed, as the case did not change to lowercase, in the duplicated column. Therefore, there is no real need to duplicate the column if you wanted to key word the messages for catogorisation. As you suggest you can duplicate the column and then edit the M code to change the case to lowercase or use the UI to do so on the column.
I solved this issue, as I was rushing ahead and not following step by step and using different ways to get the end result (as I am confident in M and PQ) I missed the step that says to select the column and use the UI to turn all text to lowercase! Doh! (facepalm)
User | Count |
---|---|
9 | |
7 | |
5 | |
5 | |
4 |
User | Count |
---|---|
15 | |
13 | |
8 | |
6 | |
6 |