rsDataShapeQueryTranslationError

[kothapsi]

I'm reaching out because I'm currently facing an issue with a report that works perfectly on both the Local and Dev environments. However, the same copy of the report is not functioning correctly on the UAT and PROD environments, despite the data being identical across all three.

The error message I am receiving is as follows: "Error fetching data for this visual. Couldn't retrieve the data for this visual. Please try again later. Please check the technical details for more information. If you contact support, please provide these details. Underlying Error: rsDataShapeQueryTranslationError."

To give you some context, I have a measure that connects an import table composite key with a direct table key. If both keys match, I take values from the direct table and display them in the table view. The table has almost 120 columns and numerous rows.

Interestingly, when I keep 10 import table columns and 2 direct table columns in the table view, it works fine. However, when I add all the columns, this error occurs.

Additionally, I have a button in the report that Action passes a URL (e.g., https:xxx.net/key1, key2, key3, etc.). If the user clicks on the first record from the table, the URL becomes https:xxx.net/key1. Then, if they Ctrl+click on the second record, the URL becomes https:xxx.net/key1, key2, and so on. This works perfectly fine in the Local and Dev servers, but when it comes to UAT and PROD, I immediately get the rsDataShapeQueryTranslationError.

Could you please help me understand why this might be happening and how I can resolve this issue? I appreciate any insights or suggestions you may have.

Thank you in advance for your assistance.
@PowerQueryFTW @PBI Convert DAX to M Code DAX Measure Query 

[v-sgandrathi]

Hi @kothapsi,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

[v-sgandrathi]

Hi @kothapsi,

Thanks for testing further and providing details. Since you need to use DirectQuery for live PostgreSQL data, the best workaround is to reduce the number of columns in each visual rather than changing the storage mode. Typically, this means splitting a large table into multiple visuals, such as a “main info” table and a “details” table, or using a drillthrough page. You could also move some fields to a separate report or drillthrough page, instead of displaying everything in one visual. Alternatively, if possible, you might create a database view in PostgreSQL that only includes the necessary columns to keep the model and visuals simpler.

This appears to be a product limitation rather than a configuration issue. If these workarounds don’t solve the problem, you may want to open a support ticket with Microsoft to have them review your model and check for any internal settings that could be adjusted for your environment.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

Thank you.

[v-sgandrathi]

Hi @kothapsi,

Just wanted to follow up and confirm that everything has been going well on this. Please let me know if there’s anything from our end.
Please feel free to reach out Microsoft fabric community forum.

Thank you.

[kothapsi]

I encountered an issue when adding more than 63 columns to the table in DirectQuery mode, which seems to be related to a column overload limitation in Power BI. Since I am required to use DirectQuery to fetch live data from a PostgreSQL table, switching to Import mode is not an option for me-so not tried. All the environment reports and versions are consistent, but I haven't found an alternative solution to resolve this issue yet.

[v-sgandrathi]

Hi @kothapsi,

The rsDataShapeQueryTranslationError usually occurs when Report Server can't translate the query behind your visual. Based on your description, this seems to be due to combining an Import table and a DirectQuery table with a composite key. Power BI Report Server has limited support for composite models, so if your visual is large (over 120 columns), the query may be too complex for the DataShape engine in UAT/PROD, even if it works in Desktop or Dev. To check this, try copying the report, temporarily set the DirectQuery table to Import, and redeploy—if it works, this confirms a storage mode limitation. Make sure all environments (Local, Dev, UAT, Prod) use the same Report Server version and the report was saved with the matching Desktop for Report Server. Another approach is to add your columns back in small batches to see which one causes the error, as complex DAX across Import and DirectQuery tables can lead to translation issues. For the URL action, use a simpler version since long key strings can exceed limits in UAT/Prod. If you can, check the RSPowerBI log for details on the failed DAX element. For a long-term solution, consider using a single storage mode or moving the join logic to the database with a view to avoid unsupported composite models on Report Server.

Thank you.