Hi @DW868990,
This is hard to solve without knowing anything about your specification or your data, so I can take a stab at it, but if I'm not right, you may need to provide more details about your situation so that we can see if anything else sticks out.
The initial thing that comes to mind is the potential number of rows in your dataset. For performance reasons, Deneb limits queries to 10,000 rows, so if some categories turn up when filtering and then don't for other situations, this might be worth exploring. You can set a property to turn this limit off, and recursively load more data from the model, but please bear in mind that it is (a) dependent on how many rows Power BI decides to give the visual, and (b) the performance of the specification, particularly if you're looking to display a high-number of marks.
Power BI and DAX is generally not great with high-cardinality datasets, so the combination of a + b may be limiting for you. If your visual takes a long time to load the data before its visualised, this is certainly a limitation of the query that Power BI produces, and not something we can change from within a custom visual due to that fact that they cannot specify the DAX to execute (as they are not permitted to know about the data model).
If this does turn out to be your issue, it's not recommended that you have this setting enabled while developing your visual and switch it on when you're ready to do more thorough testing or make available for your end users.
Regards,
Daniel
