Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
If you want to replace all blank values in power query ie either "" or null i usually create a custom column i.e
if field = null then "not specified"
else if field = "" then "not specified"
else field
as you can see below this created a custom column
now when i go into edit it the format has changed to a conditional column
fine no problem but the issue is always with the "" ie blank field which works fine in the custom column, . **bleep** then fails because it wants you to put a value in there?
anyone else had that?
see example below, assoon as you click ok
it fails and if you put "" in it, it just creates around 6 of them which you must delete out of the advanced editor.
Proud to be a Super User!
Solved! Go to Solution.
There is some logic behind it: if you create an if ... then ... else statement in the formula, then Power Query doesn't know if the resulting code was created by adding a custom column or by adding a conditional column, however....
Edit: in your case, you can adjust your code like:
if [Field] = "" or [Field] = null then "Not specified" else [Field]
I have another example, which is even stranger:
= Table.AddColumn(PrevousStep, "Custom", each if Date.IsInNextYear([Date]) then "Next year" else null)
Gives you:
In this case, it is quite obvious that the code couldn't have been created with Add Conditional Column.
As a workaround, you can try and create something neutral that forces the Add Custom Column popup to appear.
In this example: concatenate "" to "Next Year":
= Table.AddColumn(PrevousStep, "Custom", each if Date.IsInNextYear([Date]) then "Next year"&"" else null)
Hi @vanessafvg
I know that it can be fustrating, and what I have done in the past is to go into the Advanced Editor and make my changes there when it tries to use the GUI for the Conditional Column.
sure, thats what i do now, however i hope they fix it soon 🙂
Proud to be a Super User!
I agree, would be easier that way.
There is some logic behind it: if you create an if ... then ... else statement in the formula, then Power Query doesn't know if the resulting code was created by adding a custom column or by adding a conditional column, however....
Edit: in your case, you can adjust your code like:
if [Field] = "" or [Field] = null then "Not specified" else [Field]
I have another example, which is even stranger:
= Table.AddColumn(PrevousStep, "Custom", each if Date.IsInNextYear([Date]) then "Next year" else null)
Gives you:
In this case, it is quite obvious that the code couldn't have been created with Add Conditional Column.
As a workaround, you can try and create something neutral that forces the Add Custom Column popup to appear.
In this example: concatenate "" to "Next Year":
= Table.AddColumn(PrevousStep, "Custom", each if Date.IsInNextYear([Date]) then "Next year"&"" else null)
interesting, thanks @MarcelBeug
Proud to be a Super User!
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 48 | |
| 46 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 70 | |
| 69 | |
| 32 | |
| 27 | |
| 26 |