Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi folks
I need to split some filtered/selected values into two different tables (visual) just to avoid scroll bar and have clean visualization. I want to define limit of rows per table but must be the same raw data, no repeat any.
How can I do that?
Current scenario: single table with filtered values by slicers
Requested behavior: same filtered values but distributed into different tables
Solved! Go to Solution.
You could assign ranks to config IDs (or entity IDs) and then filter your table visuals by rank range.
But your requirement raises a few design red flags. Make sure it truly serves a purpose for your customers.
@lbendlin Thank you! Actually, I did create this suggested rank but based on different fields. Worked fine.
You could assign ranks to config IDs (or entity IDs) and then filter your table visuals by rank range.
But your requirement raises a few design red flags. Make sure it truly serves a purpose for your customers.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.