Scheduled refresh unavailable in the service due to error in non-existent Query

[troyhimes]

I have had a scheduled refresh setup using gateway connected sources for over a year.  I recently made some minor changes to report formatting and query setup.  Now when published to the service I get the following error:

'You can't schedule refresh for this semantic model because the following data sources currently don't support refresh:

• Data source for Query1

The problem: there is not a query in the data model named 'Query1'.  It must be a relic of something that is hung up in the system(??)

I have tried renaming it, publishing it to another workspace, but get the same result.

Anyone have any other suggestions?

[v-venuppu · Accepted solution]

Hi @troyhimes ,

Thank you for the Response.

Here are some steps to find Query Order:

1.Enable PBIR (Enhanced Metadata Format):

In Power BI Desktop, go to File > Options and settings > Options > Preview features.

Check the box for “Store reports using enhanced metadata format (PBIR)”.

Click OK and restart Power BI Desktop.

2.Save your file as a PBIP project:

Go to File > Save As and choose PBIP format.

This will save your report as a folder with subfolders like SemanticModel, Report, etc.

3.Inspect the SemanticModel folder:

Open the SemanticModel folder.

Look for the file named DataModelSchema.

Open it with a code/text editor (e.g., Visual Studio Code or Notepad++).

4.Find refresh/query order:

In the DataModelSchema, search for the "tables" or "partitions" section.

Each entry includes metadata like query names and sources.

The appearance order may give clues about how Power BI interprets the refresh sequence.

You might also discover ghost or orphan queries (like "Query1") that no longer show in Power BI UI but are still referenced internally.

If you find a rogue Query1 reference there, try removing it manually from the PBIP project or start from a clean .pbix and copy only the required queries into it.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

 Thank you.

[v-venuppu]

Hi @troyhimes ,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please accept it as a solution and give it a 'Kudos' so other community members with similar problems can find a solution faster.

Thank you.

[v-venuppu]

Hi @troyhimes ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

Regards,

Rama U.

[v-venuppu]

Hi @troyhimes ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

Regards,

Rama U.

[GilbertQ]

Hi @troyhimes 

Can you confirm that the previous version of your report was still refresh successfully? And what I mean by that is, if you had to upload the previous version before you made any changes and that uploads and refresher successfully, the issue then would lie with the query setup changes that you have made. I would recommend going through that to see what the changes are to identify the issue.

[troyhimes]

Hi @GilbertQ,

Thanks for the respons.  Yes, original report will refresh successfully.  New report in question refreshes successfully in desktop, connecting to all sources.  Agreed, issue in the service must have something to do with the query changes. The only clue as to what is causing an error is the 'Query1' verbiage and without any of the queries named 'Query1' I'm at a loss at how to find the issue causing the error.

One approach would be to back out the 'minor changes' one by one.  I'm looking for an alternative solution first, as this approach would be difficult to execute due to the interdependency of all the changes made.

[GilbertQ]

Hi @troyhimes 

For sure, sometimes the query one can be a bit misleading because there's not really the first query. What you could do is, if you open up or save your PBIX as a PBIR format. Right at the bottom, it will give you the query order of your tables that are going to be refreshed. And that might harlot which table it is referring to that is causing the issue.

[troyhimes]

Hey @GilbertQ ,

Sounds like this may be the ticket.  I'm not familiar with the PBIR format, is the query sequence contained in the 'Semantic Model' folder somewhere?

[v-venuppu]

Hi @troyhimes ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @GilbertQ for the prompt response.

The PBIR (Power BI Enhanced Report) format is a new Preview feature in Power BI that aims to improve the development and management of Power BI reports. 

• To use the PBIR format, you need to enable it in Power BI Desktop. Go to File > Options and settings > Options > Preview features and check the box next to Store reports using enhanced metadata format (PBIR)

You can find the below screenshot for reference :

Also find the Microsoft Documentation to understand better on PBIR Format :

Power BI Desktop project report folder - Power BI | Microsoft Learn

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Regards,

Rama U.

[troyhimes]

Hi Rama U. ( @v-venuppu ),

I'm familiar with generation of pbir format, but I don't know where to find  "the query order of your tables that are going to be refreshed" that @GilbertQ  mentions.