You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Visuals display the following error message sporadically when applying slicer selections:
To Reproduce
Steps to reproduce the behavior:
Connect using the Clickhouse Power BI connector in DirectQuery mode
Set up one fact table and 1-2 dimensions tables with many-to-many relationships
Add one visual and some slicers, make selections and witness the visuals return errors sporadically
Sometimes, refreshing and selecting something else resolves this issue. These actions also produce the error. There is no logic at all.
Expected behavior
No errors returned when interacting with slicers
Screenshots
Configuration
Environment
PowerBI version: 2.137.952.0 64-bit
power-bi-clickhouse version: 0.1.5
ClickHouse ODBC driver version: 1.3.0.20241018
Operating system: Windows 11 Enterprise
Additional context
For a few minutes (1-2) it can work perfectly, then the errors occur. Leaving the app for a few minutes then refreshing resolves the errors. Altering the semantic model almost always produces more errors. Restarting Power BI temporarily resolves the issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
Visuals display the following error message sporadically when applying slicer selections:
To Reproduce
Steps to reproduce the behavior:
Sometimes, refreshing and selecting something else resolves this issue. These actions also produce the error. There is no logic at all.
Expected behavior
No errors returned when interacting with slicers
Screenshots
Configuration
Environment
Additional context
For a few minutes (1-2) it can work perfectly, then the errors occur. Leaving the app for a few minutes then refreshing resolves the errors. Altering the semantic model almost always produces more errors. Restarting Power BI temporarily resolves the issue.
The text was updated successfully, but these errors were encountered: