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.
Hello,
So I am having an issue with refreshing my data in Power BI.
My data is stored in Azure SQL from an Access Web App. I pulled the data and generated a report in the Desktop then published it to a workgroup. When I go to Power BI online and hit refresh to see new data I get an error saying my refresh failed.
Any thoughts? Am I doing ths right?
Thank you
Solved! Go to Solution.
Hi @goaltender36,
Sorry for slow response, I think the issue may related to dataset, you can check its connection state at "Setting" -> "Datasets".
Regards,
Xiaoxin Sheng
Hi @goaltender36,
Can you share us some detail information to help us to reproduce your issue?
For example: Publish steps, screenshots, detail error log, refresh type, dataset connect state...
Regards,
Xiaoxin sheng
Hey @v-shex-msft
I built an Access Web App on a SharePoint and then opened Power BI Desktop and did an Import of the data, created some visuals and published it to a WorkGroup I created in Power BI. (It was when I refreshed the data source online in Power BI I got the error)
I then created a new connecting in Power BI Desktop and this time as DirectQuery and then uploaded to the workgroup. Now I do not get the error.
Is this because of where the data is being queried?
Hi @goaltender36,
Sorry for slow response, I think the issue may related to dataset, you can check its connection state at "Setting" -> "Datasets".
Regards,
Xiaoxin Sheng
What is your error saying?
Thank you for your help on this.
This was the error:
Data source error:
Unable to cast object of type 'ComDataConvert' to type 'ComDataConvert'.. The exception was raised by the IDataReader interface.
Do you think it could because I did an import from the Azure SQL DB instead of DirectQuery?
Hi @goaltender36, it would appear that there is a possible data type change in one of the columns? Where potentially it was a Whole Number, and now that particular column has a text value, causing the Whole Number data type to be invalidated or wrong?
It is a guess but something to look at.
Has the data ever been able to refresh successfully?
Hey @GilbertQ I tried yesterday reconnecting as a Direct Query and I think that worked. I haven't gotten the error since even after entering new data into the Access Web App and then clicking refresh.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
117 | |
107 | |
69 | |
68 | |
43 |
User | Count |
---|---|
148 | |
103 | |
103 | |
88 | |
66 |