tadawID on Sun, 29 Oct 2017 15:35:58


I have a model on Azure Analysis Services (compatibility 1400), which utilize some files from Azure Blob Storage being connected as Data Source.

I have several tables now created in VS (enhanced with PowerQuery editor), some measures and relations added and the model deployed to Azure. In Power BI Desktop I have been able to connect to AAS ('Live connection'), add visualization layer and publish to Power BI Service (app workspace).

BTW, I have an On-premises Data Gateway (personal mode) installed and running, but is this case it seems not valid, since here I am not using any on-prem data sources. However, 'settings' section in Power BI Service says that my data gateway is online, but all datasources are offline (!?).

The issue I am experiencing now is that after updating some files on the Blob Storage I can not see them updated on Power BI Service side.

When opening the model (in Visual Studio 2017) I can see in the Grid view that tables actually have the latest data, but after deployment it doesn't refresh when opened in Power BI Desktop (hitting refresh pulls some new measures, but not this new data from Blob Storage). 

Interestingly, when I am opening the table in Design view, there are old records. So it seems that the PowerQuery doesn't refreshes the connection (and does not react to 'Refresh All' command). So, summing up: Azure Blob Storage have new data set > Table edited in PowerQuery Designer (VS) shows old data > Table in Grid view (VS) presents new data set > Power BI Desktop and Power BI Service report shows old data.

Any clues what is happening? How to refresh the connection created by PowerQuery when importing new table (if that is the case)?


BillAnton on Tue, 31 Oct 2017 16:50:38

For changes in the source blob files to be picked up in the Power BI report(s), you will need to "refresh" the corresponding table(s) in the Azure AS model. Hitting "refresh" from the Power BI service will only pick up changes in the Azure AS model (data or metadata)... but nothing has changed (data-wise) because the Azure AS model hasn't been refreshed.