This creates a unique value for every row in your table, e.g.:Ĭlose & Apply the query and this will get added to your table. The puts the data at its lowest level of grain. The tooltip says there's 5 samples, because there are 5 distinct values for Subset, and we actually need 10 because that s what's in your raw data.Īn ideal way to do this is to use something like a primary key in your table to do the sampling on. This indicates that Subset is too high-level to provide all values of Amount to the visual, and we can see the resulting violin plot: We'll look at your data and try and find a suitable candidate field.Īn easy way to check this is by adding a measure that provides a count for the one you want to check. You need to create a unique value for this field so that the visual does not aggregate the measure at a higher level.
In order for the visual to know more about the distribution of your data, we need to give it every row we can and this is where the Sampling field comes in. You will notice that the Amount is aggregated by the Session. If we only pass these in the the visual, then Power BI will aggregate Amount by Session - as you've already indicated in your screenshot - but to illustrate how this looks to the visual: If any of this data is pre-aggregated then it will not work.įrom your example, you are plotting Session as a Category and Amount as the Measure Data. In its simplest terms, you need to be able to provide data at its lowest possible grain for this to be worked out correctly. You are correct that the visual should create all statistical measures, based on the data you feed into it. This is documented here, but I'll walk through using your data. Hi I just came across this post while browsing - I'm the author of the violin plot visual and may be able to help clarify its usage, if you're still experiencing some challenges.
0 kommentar(er)
