I downloaded the visualisation and the sample Power BI pbix file showed this visualisation working beautifully. This Power BI file is using the In Memory Model.
However I am doing some work for a key customer at the moment and their architecture is to point a Power BI connection to an SSAS Multidimensional 2014 SP 2 cube.
When I got an error I tried the same with the AdventureWorks 2014 Multi dimensional model cube and the same error was returned. I also tried performing a SQL Server Profiler trace and I did not find anything meaningful within this trace log.
So as soon as I select any value within this custom visual timeline slicer the display of any visual within the same reporting pane changes to "Can't display the visual"
Please find attached screen shots.
Note the non custom visual date slicer appears to work perfectly.
I understand why some recommend not using custom visuals, but this is not really a viable option if Power BI is going to succeed.
Although it is constantly being updated and improved, Power BI is still missing a log of required functionality; this is mitigated by having custom visuals available. If we remove custom visuals then the product as a whole is significantly compromised and far less suitable for a lot of projects.
So the only viable answer is not to put our heads in the sand and not use them, but for the awesome custom visual devs (like Jan Pieter) to keep enhancing them further, and critically for Microsoft to find a way of not breaking visuals when Power BI is updated.
Whilst using Power BI InMemory (Import) model I have found the performance of both the Timeslice and Hiearchy custom visual to be fit for purpose.
I was careful though to make sure I only exposed dimensional records as the data source of these custom filters where these dimensional records had at least one associated fact record.
The fact table contains 60,000 rows, the Product dimension (data source for the Hierarchy custom visual contained 158 rows), the Date dimension (data source for the Timeslice custom visual contained 1461 rows).