The March 2018 update introduced visual header control at the report level. Since this is currently an 'all-or-nothing' feature, please evolve this so we can control visual headers on a per visual b...
eric_beacom
6 years agoNew Member
The headers must be controlled on a per-visual basis. They create a significant usabiity issue when visually obscuring information below (on mouseover). They are more problematic when an visualization or visual element is selected and the header becomes a static layer that sits in the foreground, until unselected. In usability tests both behaviors created problems for some test subjects.
Recent ideas
Pipeline: Activity-level Run Conditions (No IF Container Required)
We need the ability to add a "Run if" condition directly to every pipeline activity. Like, in each acticity's settings. One of the biggest readability issues in Fabric Pipelines is that conditional ...frithjof_v16 hours agoCommunity ChampionNew22Views2likes1CommentPipeline: New Routing activity as an improvement to IF and Switch
The current If Condition and Switch activities create large nested containers that own all activities inside their branches. These containers make the canvas much harder to read. Instead, add a lig...frithjof_v16 hours agoCommunity ChampionNew9Views0likes1CommentEnhance Workspace Throttling to Allow Targeted Limits on Individual Workspaces
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } The current workspace throttling design should be enhanced to allow Fabr...kyleleonard1 day agoNew MemberNew28Views5likes0Comments