Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

Reply
Urs
Frequent Visitor

Dataverse - Currency Fields - Error converting data type nvarchar to numeric - Bug?

Hi there

since some days (I think since the February 2023 release) I experience an Error when multiplying a Dataverse Currency Field with a numeric value. This happens in both Power BI Desktop and Power BI Service.

 

This is source shows the error by simply multiplying the estimated revenue field from the dataverse opportunity table by 1.1:

 

let
    Source = CommonDataService.Database("url.to.dataverse"),
    dbo_opportunity = Source{[Schema="dbo",Item="opportunity"]}[Data],
    #"Removed Other Columns" = Table.SelectColumns(dbo_opportunity,{"opportunityid", "estimatedvalue"}),
    #"Added Custom" = Table.AddColumn(#"Removed Other Columns", "TestMultiplyCurrencyColumn", each [estimatedvalue] * 1.1)
in
    #"Added Custom"

 

 

This is the test-data used:

currencyConvertBug_Data.png

 

This is the error message I receive:

currencyConvertBug_Error_Message.png

 

I think it might could be a bug.

Who is experiencing the same issue?

 

Have a nice day

Urs

1 ACCEPTED SOLUTION
Urs
Frequent Visitor

Just had a call with Microsoft Support. They fixed the issue in the backend and it works now.

View solution in original post

6 REPLIES 6
Urs
Frequent Visitor

Just had a call with Microsoft Support. They fixed the issue in the backend and it works now.

Urs
Frequent Visitor

Since the Problem still exists (in Power BI Desktop and Power BI Dataflow) after the March Release, I opened a Ticket at Microsoft.

 

I will post an update as soon as I have more Information from Microsoft.

Steph999
Frequent Visitor

I am also having this exact issue, it just cropped up over the weekend within a pbx file that was running fine before Saturday. 

Anonymous
Not applicable

I'm running into the same issue...were you able to find a solution?

Urs
Frequent Visitor

Unfortunately, the problem still exists.

 

A possible, but in my opinion bad workaround, is not to do the calculation in Power Query, but to do it in a Calculated Column in the dataset.

Steph999
Frequent Visitor

I tried this, and the problem presists outside of power query. Very odd... 

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

Top Kudoed Authors