-
Notifications
You must be signed in to change notification settings - Fork 115
Shape visibility is not taking effect #867
Comments
The conditional visibility is for the marks used (in the Glyph Editor) to create a glyph, which is a visual representation of a single data row. To create the chart above, I suggest the data table be formatted the following way, which includes the columns (i.e., Xpos and Ypos) to position each glyph: If you use the Charticulator visual with the Slicer and the data in the above format, you don't need to use the conditional visibility. Here is the pbix and csv files created with your data: Safety Cross Test.zip. Please note that the Power BI extension of Charticulator, which is a different codebase, is not actively maintained. Because we are a small team and have limited development resources, we focus on improving the Charticulator visual. If you want to see Charticulator further developed and eventually integrated into Power BI Desktop, please add your vote to this idea, Microsoft Idea · Integrate Charticulator into Power BI Desktop. |
Thank you, I think that is the better way. But I can see your copy above is displaying correctly. Is there a setting that I need to change? |
I would prefer using the Charticulator visual if its the more actively maintained version. However, publishing it is an issue. It is not rendered properly, and need to be manually added by an admin to the "My Organization" page. How can an admin add the Charticulator visual even if I can't export a pbiviz file or template from it? |
@ACVida you need to download *.pbiviz file of Charticulator visual from Appsource page then import into Organizational visual for your tenant |
I’ve created a custom visual called a Safety Cross and I’ve encountered an issue regarding shape visibility.
So this visual is mostly working fine, except that the visibility status of a shape is not taking effect. This is how it looks like in the desktop:
The goal of the custom visual is to display the days of the month in a cross layout. Since some months have 28, 29, 30 or 31 days, days not present in the selected month should be hidden. I configured the custom visual by passing three Boolean fields included in the Safety Cross dataset:
• day_29_visible
• day_30_visible
• day_31_visible
These fields are then used by the custom visual, where the visibility attribute of the shapes referring to days 29, 30, 31 have been assigned with these values. You can open the file “Safety Falls.tmplt” in the zip file to check this configuration.
To replicate the issue, open the pbix file included in the zip file, go to the Safety Cross page, where you can filter either by Feb, Mar or Apr 2021. Choosing February does not hide day 29, 30 and 31 and choosing Apr does not hide day 31 in the custom visual on the left.
There is a matrix on the right to display the values being passed to the Safety Cross custom visual on its left.
I have also attached the PBI file, the template file and the pbiviz file.
Safety Cross.zip
The text was updated successfully, but these errors were encountered: