Forum Discussion
We cannot convert the value null to type Logical in Service
- 8 years ago
When you use the Azure Data Lake connector Power BI creates your query for you. The resulting query, running through DataLake.Contents is then supplied with default parameters that (at the time of writing) break the evaluation once uploaded to the Power BI service. The problem is the second param, the empty record []. Exchange it for a null, or simply delete it.
Bad:
DataLake.Contents("adl://adlstest01.azuredatalakestore.net/data/examples/entries.csv", [])
Good:
DataLake.Contents("adl://adlstest01.azuredatalakestore.net/data/examples/entries.csv", null)
At least this worked for me.
HI helgerg,
I think it might be a issue with azure data lake service, I'd like to suggest you open a support ticket for this scenario to get more support from power bi team.
submit a support ticket
Regards,
Xiaoxin Sheng
When you use the Azure Data Lake connector Power BI creates your query for you. The resulting query, running through DataLake.Contents is then supplied with default parameters that (at the time of writing) break the evaluation once uploaded to the Power BI service. The problem is the second param, the empty record []. Exchange it for a null, or simply delete it.
Bad:
DataLake.Contents("adl://adlstest01.azuredatalakestore.net/data/examples/entries.csv", [])
Good:
DataLake.Contents("adl://adlstest01.azuredatalakestore.net/data/examples/entries.csv", null)
At least this worked for me.
- helgerg8 years agoFrequent Visitor
thanks, it did the trick :)
- JulianPayne_i47 years agoFrequent Visitor
When trying to connect to AZDL with SSAS Azure in Visual Studio, I keep getting this error:
Details: "We cannot convert the value null to type Logical."
I do not get this error in Power BI using the same connection string.
connection string: adl://<mydata>.azuredatalakestore.net
Any thoughts?
In VS, I am not able to open a blank query to write this correct version of the connection string, as far as I am aware.