Just started getting a PBI dataset refreshe error today, after 2 successful syncs early in the morning. This is the error code I get from the service. Getting a similar error in PBI desktop when I try to refresh the dataset. This is happening to multiple tables.
Underlying error code-2147467259 Underlying error messageMicrosoft SQL: Conversion failed when converting the nvarchar value '36, 37' to data type int. Microsoft.Data.Mashup.ValueError.MessageConversion failed when converting the nvarchar value '36, 37' to data type int.
Welcome to the world of bad data. What is your expectation - should Power BI use the first number, the second one, or should it reject the row (as it did) but maybe more gracefully?
Helpful resources
Announcements
FabCon Atlanta 2026
Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
