Forum Discussion

eneri's avatar
eneri
Helper I
1 year ago
Solved

ErrorCode = 10277, cannot convert null to logical - Dataflow Gen 2 - Lakehouse

Repeated error message when refreshing a data flow The data flow loads a fact table from the Lakehouse, aggregates the values by user_id in 2 different ways, joins these tables together and sh...
Dataflow
Need Help
  • eneri's avatar
    eneri
    1 year ago

    In the end, I had to replace all null and 0 values in all columns (not just logical) and remove a date column that had null values that couldn't be replaced or filtered. 

eneri's avatar
eneri
Helper I
1 year ago

Thanks v-kpoloju-msft for the feedback. 
But all these steps I have already done - as listed above: 

  • changed the logical columns to text

  • deleted and re-created the table in the Lakehouse

  • renamed the table to write it into a new table

  • tested manual and automatic schema settings (see screenshots)

Today I tried additionally: 

  • use "publish later" and run the flow through the pipeline
  • use "publish later" and refresh the flow through the button in the workspace list
  • created an alternative output that doesn't have the has_fji_only, fj_started_tf columns
  • re-created the dataflow without any calculated logical columns (just 0/1 as type any, which I then convert to type text and replace the values with texts)

But the new flow shows the same error in the in-between-step (does not even attempt to write the data into the Lakehouse)

I submitted a support ticket now ... 


 



 

 

v-kpoloju-msft's avatar
v-kpoloju-msft
Community Support
1 year ago

Hi eneri,

Thank you for the detailed follow up and for sharing all the steps you've already tried. Given that the failure is occurring before writing to the Lakehouse and even simplified flows are encountering the same mid-step error, it is likely that this issue goes beyond configuration and may relate to an underlying problem with the dataflow engine or schema inference.

 

Since you have already submitted a support ticket, I recommend continuing with that route so the support team can check the backend logs and telemetry for deeper insights.

 

In the meantime, if you have not already, consider enabling detailed logging or checking the Diagnostics tab (if available in your workspace) for any additional error context.

Please consider raising a Microsoft support ticket. You can create a Microsoft support ticket using the link below: https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

Please let us know if you receive any resolution or workaround from the support team, as it would be valuable for others who might encounter similar issues.


If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.