Forum Discussion
No error Refresh in Power Bi Desktop, but have DataSource error in Power Bi Service
I check all my power query in Power Bi desktop, Zero error and refresh without problem. After published to Power Bi Service, Data Source error occured as below.
[ValidateMarkupTags][ccon]Expression.Error: We cannot convert the value [ccon]"[Binary]"[/ccon] to type [ccon]Binary[/ccon].. [/ccon]. The exception was raised by the IDbCommand interface. Table: Daily Overdue.
So, I was finally able to solve this problem.
The issue was with my data source credentials. Because my report used different data sources, it expected that each source would have the same credential as the other.
To solve the issue, I went to the semantic models of my report and changed each credential to be the same as the other. For example, I used the OAuth2 authentication method and privacy level was set to Organizational for each of the data sources.This solved the problem for me. I hope it does for you as well.
Best of luck.
PS: If this solves the issue, please accept it as a solution to help others as well
6 Replies
The error message you are encountering in the Power BI Service, specifically the "We cannot convert the value [Binary] to type Binary" error, indicates a problem with the data type conversion in your Power Query transformations. This error suggests that there is a data type mismatch between what Power Query expects and what it's encountering during the refresh in the Power BI Service.
To address this issue, follow these steps:
Review the Query in Power BI Desktop:
- Double-check your Power Query transformations in Power BI Desktop. Pay close attention to any steps that involve data type conversion, especially those that involve binary data.
Check Data Types:
- Ensure that the data types of columns in your data source match the expected data types in Power BI. You may need to explicitly convert columns to the correct data types in Power Query.
Check for External Data Sources:
- If you are connecting to external data sources (e.g., databases), verify that the data types in the source match the data types expected by Power BI. In some cases, data source changes can cause this type of issue.
Check for Privacy Levels:
- Ensure that privacy levels are correctly configured for your data sources in Power Query. If there is a privacy level mismatch between data sources, it can cause errors during refresh.
Review Query Dependencies:
- Examine the dependencies between your queries in Power Query. Ensure that the query dependencies are correctly defined, and there are no circular dependencies.
Test the Refresh Locally:
- Try refreshing your data in Power BI Desktop to ensure that there are no errors in your local environment. This can help identify if the issue is specific to the Power BI Service or if it's present in your original data or Power Query transformations.
Data Source Credentials:
- Make sure that the credentials used to access the data source are correctly configured both in Power BI Desktop and in the Power BI Service.
If you find this insightful, please provide a Kudo and accept this as a solution.
This ChatGPT response does not solve the problem as I am having the exact issue.
FrankFan As you kudoed this reply, can you also accept it as a solution so that other users can find it more easily.
already checked all and no error in power bi desktop but still have the same error msg in Power Bi Service
In my case, I had 2 column headers that changed name (source is excel) - I had to remove lines above and then apply headers. So whenever the header text changed, I got this error.
Had to update the step with the error with the new/updated column names (which is a bit of a pain if the title has a line feeder in it).
So, I was finally able to solve this problem.
The issue was with my data source credentials. Because my report used different data sources, it expected that each source would have the same credential as the other.
To solve the issue, I went to the semantic models of my report and changed each credential to be the same as the other. For example, I used the OAuth2 authentication method and privacy level was set to Organizational for each of the data sources.This solved the problem for me. I hope it does for you as well.
Best of luck.
PS: If this solves the issue, please accept it as a solution to help others as well
