All Data Sources unknown

[EasyChreasi]

Hi there,

I got a direct query model with a couple of complex relationships, many dynamic m-parameters and some unconnected filter tables. Everything was working as expected and it still works but all of a sudden power bi shows unknown data source for all tables in model view. The only downside as i see it now is that i am not able to do inner joins anymore (assume referential integrity) with new connections. The ones that are already established still work. 

We work with a premium capacity and a redshift DB. 

Any ideas how to solve this are very much appreciated. 

Thanks in advance!

Christian 

[EasyChreasi]

Hi there, thanks for your answers. Unfortunately not was i am looking for. The model worked perfectly before the August Update. Now I am looking forward to install the october one. Will get back here then. 

[v-nmadadi-msft]

Hi @EasyChreasi ,
Thanks for the update. That makes sense. Once you’ve installed the October update, feel free to come back here, and we’ll be happy to help you further with the issue.

Thank You

[v-nmadadi-msft]

Hi @EasyChreasi 

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.

Thank you.

[v-nmadadi-msft]

Hi @EasyChreasi  ,
Thanks for reaching out to the Microsoft fabric community forum.

Go to File -> Options -> Data source settings. Check if the Redshift DB has all the required permissions, if you find any issues there you may have to reconnect to your data source.
Start by verifying that the data source path or URL is correct and hasn’t changed. Then, reconnect to the source in Power Query and carefully remap the required tables to ensure they align with your model. Also, double-check that the files or databases are stored in a location accessible to Power BI, since inaccessible, relocated, or permission-restricted sources can cause them to show up as “unknown” in the model view.

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[Ritaf1983]

Hi @EasyChreasi 

This is hard to diagnose without opening the PBIX, but the symptom “All Data Sources = Unknown” in Model view means Power BI can’t verify that your DirectQuery tables are from one consistent source. In DirectQuery that prevents new relationships and the “Assume referential integrity” option, which is why inner joins stop being allowed for new connections.

Common causes

• Dynamic M parameters in the connection path (server/database/schema) or text-built connection strings.

• Slightly different connection details across queries (different server aliases, database names, authentication modes, or drivers).

• Privacy levels set inconsistently.

• Recent version or driver changes.

• Infrastructure issues: Redshift or network/Gateway changes, permission updates, or security patches that alter metadata access.

Quick checks

1. In Data source settings confirm every DirectQuery table uses the exact same Redshift connection (same server, database, auth, driver).

2. Open Advanced Editor and make sure your sources are literal, e.g.
   Source = Redshift.Database("my-server", "my-db", [CreateNavigationProperties=false])
   Avoid Text.Combine, parameterized server/database names, or functions in the Redshift.Database(...) call.

3. If you use Dynamic M Query Parameters, keep them only in filters (WHERE) that fold, not in the connection path.

4. Set Privacy level for the Redshift source uniformly (Organizational), then Clear Permissions and re-sign in.

5. Update to the latest Desktop or roll back to the last known good build; also update the Redshift driver.

6. If you use an on-premises data gateway, verify the gateway data source maps to the same server/database and credentials.

Stabilize the model

• Create one base Redshift source query and make all tables reference it.

• Push complex logic and joins into Redshift views so Power BI sees one clean source.

• Keep unconnected parameter tables in Import if needed; avoid mixing multiple DirectQuery sources.

If after normalizing the connection the model still shows “Unknown,” collect a small repro PBIX and open a Microsoft support ticket. Include diagnostics and the exact Desktop build, driver version, and Redshift details.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly