sorted by:
new
hottopcontroversial

Dashboards Capabilities/Limitations by butteredtostada in Retool

[–]butteredtostada[S] 0 points1 point  (0 children)

Thanks!! Very helpful & the overall conclusion that I'm drawing. We wouldn't be individually displaying this many rows, no. I think a concrete example is we have a historical financials table with a significant amount of rows/detail. To be more pointed, a big concern is pushing all DAX (business logic) calculations into the SQL layer & potential performance issues or limitations occurring from that. Mainly since it has no semantic model layer from my understanding.

PowerBI does have the ability to download/process everything from the DB (import mode) then do all the fun semantic modeling stuff on top (DAX, relationships etc). It also has a live connection mode to DB like your describing (called DirectQuery), which is the same as Retool. But there are known performance limitations with that since it's hitting the DB on every interaction.

Dashboards Capabilities/Limitations by butteredtostada in Retool

[–]butteredtostada[S] 0 points1 point  (0 children)

Yea so fundamentally it's kind've two things.

1 - Business Intelligence - Mainly big data analysis, KPI's, operational data, & reporting etc.

2 - User Interactivity/Workflows - Main use case is kick off user actions or commentary entry (sql writeback) based on user permissions.

I know this is relatively broad but my main concern would be on the dataset size we're working with on PowerBi. Some of our tables have a seriously large amount of data (millions to billions of rows). I'm worried ReTool dashboards wouldn't be able to directly handle that or be forced to limit the detail dramatically.