Reply
mep
Frequent Visitor
Partially syndicated - Outbound

directquery for Redshift throws error after directquery for opensearch is set

Setting a directquery to my Redshift cluster works perfectly until I set a query to my opensearch instance on the same powerbi dashboard, then the directquery to Redshift cluster stops working and throws the following error:

 

Error Message:
DirectQuery error: DirectQuery may not be used with this data source - please consider moving to a supported data source or upgrading the SQL Server data source to the latest available version.
 
The strange part is that both connections seem to be working in the PowerQuery editor, however, in the Report page, visualizations connected to opensearch DQ work fine but visualizations connected to redshift DQ stops workin and throws above error message once opensearch is setup.
 
Anyone have any idea why could this be?
1 ACCEPTED SOLUTION
v-stephen-msft
Community Support
Community Support

Syndicated - Outbound

Hi @mep ,

 

One possible solution is that you may check if you have mixed datasource options, which is not allowed in DirectQuery. This error is caused by the Mashup static analysis identifying 2 data sources for a DirectQuery query, which is not allowed. Usually this is due to the DQ query referring to another query that utilizes different connection options.

                                                                                                                                                         

Best Regards,

Stephen Tao

 

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

View solution in original post

1 REPLY 1
v-stephen-msft
Community Support
Community Support

Syndicated - Outbound

Hi @mep ,

 

One possible solution is that you may check if you have mixed datasource options, which is not allowed in DirectQuery. This error is caused by the Mashup static analysis identifying 2 data sources for a DirectQuery query, which is not allowed. Usually this is due to the DQ query referring to another query that utilizes different connection options.

                                                                                                                                                         

Best Regards,

Stephen Tao

 

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

avatar user

Helpful resources

Announcements
March PBI video - carousel

Power BI Monthly Update - March 2025

Check out the March 2025 Power BI update to learn about new features.

March2025 Carousel

Fabric Community Update - March 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors (Last Month)
Top Kudoed Authors (Last Month)