Expression.Error: We cannot convert the value null to type Number. mysteriously appeared

[Syndicate_Admin]

I'm working in an ERP reporting project and I have relatively complex PBI and PQ set with dozens of tables and processing steps.

Everything were fine until yesterday when I started to get error Expression.Error: We cannot convert the value null to type Number from several different phases of the processing steps. What makes no sense is that the phases where the error occurs is not how it normally is.

So, this is the end result from one of the tables I'm processing

In the middle of the process eveything works fine. Here is the column item list I suspect is the reason for the errors:

No problems there. This is the applied step #16

The next step #17 is about filtering some rows based on completely other column and which does not have anything to do with the salesorderItem column:

"= Table.SelectRows(#"Added invoicingPeriodWorkingDays", each [invoicingPeriodStarts] <= [invoicingPeriodEndDate])"

And now, when I look at the salesorderItem column after the step #17 I get :

There it is. 

Anyone having seen similar behavior? Is this a memory related problem? Is there any way to get better insight what could cause this?

Jani

[Syndicate_Admin]

Right Click on the Column which has errors and Click on "Drill Down" which removes Error.

[Syndicate_Admin]

This happens if there is a step that causes some field in as few as one record to return an error and then a subsequent step does a Grouping that includes the column containing the error result.  For example an AddColumn step.  To find the issue, use Keep Errors to check the steps that might be returning occasional error values.

[Syndicate_Admin]

Hi,

Please validate if you have any measure with null values in your model.  If yes, try to replace the null per 0 or filter it out.

It can be a possible solution to this error.

Regards,

[Syndicate_Admin]

For troubleshooting errors in PBI Power Query Editor, I will extract previous steps (right click on the step where you receive the error) and from there its easier to understand the issue... 

[Syndicate_Admin]

This weird step in fact helped me!

[Syndicate_Admin]

Finding the source of error is the key to solving the issue. 

One of the ways I found helpful for finding the offending row is to use the "Keep Errors" option and understand the nature of the issue. The next step I take is to replace the error with null. This might or might not be of help to you. 

[Syndicate_Admin]

None of this worked for me. Try this:

1. Find the step tranformation step where this error start appearing.

2. go to one step above that (a point where the error does not exist)
3. Select all columns and click "Remove Errors"
4. Go to the next step and the error should be gone.

This seem to work for my transformations.

[Syndicate_Admin]

I am working on a powerBi report and I pulled data from Azure cost management. I tried loading the usage details data into powerquery and I got this.

Expression.Error: We cannot convert the value null to type Record.

Details:

Value= Type=[Type

I have tried modifying the M query from the advanced editor but I am not getting it right.

This is the  M query code

let
    source = AzureCostManagement.Tables("Enrollment Number", "10xxxxx", 12, [startDate=null, endDate=null]),
    usagedetails = Source{[Key="usagedetails"]}[Data]
in
    usagedetails