[BUG] Aug 2025: DirectQuery treats same Sql.Database connections as separate sources, error refresh

[annelebel]

Not just an annoyance but a regression. Please investigate.

UPDATE: Opened ticket with MS. The new behavior with the Potential Security Risk warning and the different colors for each table using the same Sql.Database connection is intentional and expected in the Aug 2025 Power BI update. I've posted an Idea to have MS change back the coloring as I believe it to be a beneficial visual cue that all your DQ connections are the same (and different when you explicitly need to use a different connection). Idea link at bottom of post/comment - please give a thumbs up to it. 

There is a bug though, and that is the Non-null assertion error and the inability to refresh the tables in Model View. Workaround at this time is to use July 2025 release.

Using Value.NativeQuery for the same server and database (each value stored in a parameter - example posted below) with calls to views and tables. Opening a Direct Query model will now give a warning about separate sources (shown below) - again, this is now expected behavior and should only happen an inital time once model is saved. Going into Advanced Editor and refreshing tables there works without issue, including adding new columns.

Once in Model View, trying to refresh will throw a Non-null assertion error (output pasted below for two DeptDim tables). Table datasource info shows message 'we could not detect the source' - shown below. There is only one datasource used in the model. 

Model Setup:

section Section1; (parameters)

shared ReportingServer = "ServerName" meta [IsParameterQuery=true, Type="Any", IsParameterQueryRequired=true];

shared ReportingDatabase = "Database" meta [IsParameterQuery=true, Type="Any", IsParameterQueryRequired=true];

shared Dept1 = let
Source = Sql.Database(ReportingServer, ReportingDatabase),
Query = Value.NativeQuery(Source, "SELECT * FROM dbo.DepartmentDim dep")
in
Query;

shared Dept2 = let
Source = Sql.Database(ReportingServer, ReportingDatabase),
Query = Value.NativeQuery(Source, "SELECT * FROM dbo.DepartmentDim dep")
in
Query;

Idea post to get DQ same source tables back to using single color scheme in Model view: 
August 2025 bug with Direct Query - each table now... - Microsoft Fabric Community

[annelebel · Accepted solution]

After lots of documenting, testing and confirming with MS support, this bug was fixed in the Sept 15 2025 release,  version 2.147.931.0. Turns out is the the Value.NativeQuery causing the error.

[v-lgarikapat]

Hi @annelebel ,

Thanks for the confirmation

Best Regards.

Lakshmi.

[annelebel]

Yes, the first link you suggest is mine. I added it at the bottom of the post as well. Wasn't quite sure where to post this in all the different forums. I've since changed that to be an actual Idea (per MS suggestion) and I will edit above to reflect what I learned from my MS support ticket on this matter.

[v-lgarikapat]

Hi @annelebel , 

Thanks for reaching out to the Microsoft fabric community forum.

@amitchandak Thanks for your prompt response.

@annelebel  Thanks for confirming. I just wanted to follow up to check if you’ve had a chance to update the post to reflect the learnings from your MS support ticket,

We appreciate your engagement and thank you for being an active part of the community.

Best regards,
Lakshmi

[amitchandak]

@annelebel , There are issues reported, please check and update those or log a new one 

https://community.fabric.microsoft.com/t5/Issues/August-2025-bug-with-Direct-Query-each-table-now-a-...
https://community.fabric.microsoft.com/t5/Issues/Direct-Query-Mode-Missing/idi-p/4799096