We are having loads of problems with uploaded pbix files to powerbi.com, data can be updated whilst on powerbi desktop, but after uploading to powerbi.com it can now longer be refreshed due to various different errors that are hard to troubleshoot due to lack of documentation and support.
We have several clients where we have created data sets in powerbi desktop and that we now need to create dashboards for sales teams etc, this doesn't work because we cannot update them in powerbi.com. This means that we cannot really use dashboard which is what the clients are looking for.
Whilst Microsoft are hard at work ironing out bugs and documentation for this great product, we are trying to find a workaround. Scheduled refresh are nice however we could live without them for now if the we would be able to somehow refresh the dataset from power bi desktop without breaking the dashboard linkage, does anyone know if there is any way achieve that?
I/E upload a pbix file that is updated, create tailored dashboard based on that(hours of work) and then update the dataset by refreshing from the powerbi desktop app and upload the same dataset again, updating the dashboards in the process. If there is no way then we are pretty much stuck as updates from powerbi.com just won't work.
Thanks for your reply. Yes, for some of the data sets there is a personal gateway configured, with all credentials updated and seemingly working.
This happens though for in total 4 datasets.
Dataset 1: Dynamics crm Online and Azure Sql no gateway required, fails in refresh only in powerbi.com works in desktop
Dataset 2: Dynamics crm, two different Azure SQL, two Excel files on Onedrive- Requires gateway, configured and tested in on total 4 different machins windows 2012 R2, Windows 10, Windows 8.1, fails in refresh only in powerbi.com works in desktop
Dataset 3: Only Excelfiles stored in Onedrive, gateway setup and working, fails in refresh only in powerbi.com works in desktop
Dataset 4: Dynamics crm, two Azure SQL, Excel in Onedrive, fails in refresh only in powerbi.com work in desktop.
Different errors on the different datasets for example(I haven't found anything to explain these so that they can be solved and support and documentation is hard to get at this point, therefore I am thinking of getting a "refresh workaround" so dashboards can be updated from a powerbi desktop update.
|Processing Error:||The operation is canceled by user.|
|Processing Error:||The following system error occurred: Type mismatch.|
|Processing Error:||Cannot decrypt the credential for data source NewPbiDataSource_d3da28bf-75dc-4e1c-9c0c-acea9b9b7887. The credential is missing or the certificate is changed. Please make sure the certificate has not been changed since it is configured in gateway management console.|
Are the failures for all of the data sources in the data sets or just specific ones? I have had excellent success with CRM Online data refreshes although I am using the content pack for it.
I have also had good success with Excel files stored locally, not so much on network drives and haven't tried OneDrive specifically.
Proud to be a Datanaut!
Thats just it, the error message just reads as attached and doesn't point to any data set so very hard to figure out if it one or all or even a specific part in one data set which I guess would be needed in order to troubleshoot. All data set and credentials looks ok before refreshing.
We are also using the built in CRM online data and it works fine also with refresh, also using Google analytics with success. Also the same data sources works when using other much less complex pbix files, by complex I mean renamed colums, calculations etc
I feel you on the data refresh error when there are multiple data sources. I have had to create "test" data sets that consist of one data source each and test these to determine which one is causing the problem. Another indicator that sometimes helps is that if you go to the Schedule Refresh page and look in the Credentials, sometimes the "bad" data source will have the yellow i and that's an indicator of the bad data source.
Proud to be a Datanaut!