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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Refresh failing for reports using Azure Cost Management tables

 

 

For the past week now, all my reports that are using the Azure Cost Management data tables are failing with the error:

 

Data source error: Expression.Error: <pii>We cannot convert a value of type Binary to type Function.</pii>. ;We cannot convert a value of type Binary to type Function.. The exception was raised by the IDbCommand interface. Table: RI recommendations (single).
Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net
Activity ID: fd876af9-ceba-4a4c-b3d9-fa79bcdad1e9
Request ID: 603eb53f-9af9-448f-8998-a54602d4c0b0
Time: 2021-09-11 07:10:08Z

 

Is there a fix for this?

 

Status: Accepted
Comments
Anonymous
Not applicable

Same issue here, too:

 

Last refresh failed: Thu Sep 16 2021 11:20:22 GMT-0400 (Eastern Daylight Time)
There was an error when processing the data in the dataset.

 

Processing error:We cannot convert a value of type Binary to type Function.
Cluster URI:WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net
Activity ID:88367309-a9f6-42be-ae9d-1dce3ee3cce6
Request ID:e540bf0b-a92b-9a0f-62d0-c45b954f8a0a
Time:

2021-09-16 15:20:22Z

 

Desktop refresh works just fine, just the Power BI Service gives this error.

Anonymous
Not applicable

We've been having the same problem since 9/8/21

 

Data source error: Expression.Error: <pii>We cannot convert a value of type Binary to type Function.</pii>. ;We cannot convert a value of type Binary to type Function.. The exception was raised by the IDbCommand interface. Table: Usage details.
Cluster URI: WABI-WEST-US-redirect.analysis.windows.net
Activity ID: e131c30d-1dac-4d8c-93cb-0bfaebcc7c09
Request ID: af52f36a-9d72-6582-bd79-91069a7bb3af
Time: 2021-09-15 20:14:05Z

v-robertq-msft
Community Support

Hi,

I’ve got this message from pg:

The fix is deployed to MSIT 9.3 (Both shared and MWC) - Validated

Canary1 9.1 QFE is in progress for Australia east- MWC

Canary1 (Australia East) Canary2 (NCUS) - Shared we are waiting for builds due to CST failures)

ROW 9.1 (Expected to complete by 9/18 Noon/Evening)

 

I will update here once I get any information.

 

Best Regards,

Community Support Team _Robert Qin

kerry6a
Regular Visitor

New error with updates:

 

Processing error: We cannot convert the value "Required Field: 'Enr..." to type List.
Cluster URI: WABI-US-EAST2-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 7bde9c80-e342-4747-b6c4-d4a5a1851327
Request ID: d5ffb472-31ca-8553-e6a8-202f8fdb58df
Time: 2021-09-17 14:39:06Z

 

FbrAbreu
Regular Visitor

I am have the same problem here, any ideia for solucion.
Erro de processamento: We cannot convert a value of type Binary to type Function.
Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
ID da atividade: 21b43a6e-0e47-43d0-8317-2bf34db9296b
Solicitar ID: 250057ab-b484-e752-cb4b-63e3c2e3b288
Hora: 2021-09-17 22:18:39Z
Desktop refresh works just fine, just the Power BI Service gives this error.

Steven_VM
Regular Visitor

Same issue applies for me when using Power BI services online. I don't have the issue when using the desktop version and refreshing on my laptop.

I notice that when injecting credentials in the power bi services references, I already have a similar error there, which I don't have on the desktop version:

Steven_VM_1-1631865662006.png

 

I hope this gets resolved soon as our business users need this data for their billing.

kerry6a
Regular Visitor

agreed.  this is becoming urgent

 

dwarnerbn
Regular Visitor

After updating the app this morning I'm getting a different error on refresh:

 

We cannot convert the value null to type Record.

 

kerry6a
Regular Visitor

Processing error: We cannot convert the value "Required Field: 'Enr..." to type List.
Cluster URI: WABI-US-EAST2-B-PRIMARY-redirect.analysis.windows.net
Activity ID: a5b67def-8514-4e05-a273-9182a8e7e751
Request ID: fa2c6f07-eea1-ab3f-50fb-7afb6f76e65f
Time: 2021-09-20 17:05:37Z

Anonymous
Not applicable

The error cleared up for us today. No changes on our end.