Cannot refresh dataset for Azure SQL Server

[randomconjectur]

I have a SQL Server dataset that was automatically refreshing just fine for months. After updating the dataset, I am now getting the following error:  

Nothing is listed after the colon. The only data source is SQL Server. 

Here's the view of the data source in Power BI desktop per this article https://docs.microsoft.com/en-us/power-bi/connect-data/service-admin-troubleshoot-unsupported-data-s...:

There are a number of different tables, but they are all from the same database and this source information is structured identically for each of them. 

Many thanks!

[randomconjectur]

Nevermind.  The data set based on the dataflow seems to have decided to permit me to schedule a refresh now and stopped giving me the "the following data sources currently don't support refresh" message.  Thanks!

[v-yetao1-msft]

Hi @randomconjectur 

You mentioned you update your dataset , how did you update ? After you updating your dataset , did you update your gateway in Manage gateways ? Can you refresh normally in Desktop ?

Best Regards,
Community Support Team _ Ailsa Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[randomconjectur]

I am able to update the dataset in Desktop and in the web app -- but as shown in my screenshot, I cannot *schedule* a refresh.  I do not have a gateway installed as this is an Azure managed instance that, as far as I understand, does not require one (and never did before).  As I mentioned, this worked just fine for months.

I have used @otravers' suggestion of using a dataflow instead of refreshing the data set.  I did that and set up a refresh schedule; it works perfectly. However, the dataset that is based on the dataflow still has exactly the same error (no option to refresh it, exactly as shown in the screenshot I posted initially). 

So . . . now I have a dataflow that updates, but still no way to update my dataset. 

Any further help would be appreciated!

[otravers]

Several of us have seen this bug lately, seems to happen with SQL sources in particular. Refresh your browser or try a bit later and it should go away.

[randomconjectur]

Unfortunately, I have been getting the error for many days.  I even tried republishing it under a different name.  No dice. 😞 

[otravers · Accepted solution]

If you're really stuck, copy one of your queries in a dataflow to see if it refreshes successfully, and if it does, migrate the rest of your queries to dataflows then source your dataset from them.