Forum Discussion
Custom Visual stops working
Hi all,
I've edited and repackaged an existing custom visual (https://github.com/microsoft/PowerBI-visuals-TextFilter) to produce an exact match filter rather than a "contains" filter. When applying the filter in PowerBI Desktop it works as expected, but then if I publish the file to the online service, or save the file and re-open, it no longer functions at all. You can still SEE the visual, but it no longer functions as a filter.
If I remove the visual and put it back on the report again, it begins working as expected until I save or publish as discussed above.
Any help or tips as to why this may be occuring would be appreciated.
Cheers
Hi Jayleny,
I have resolved the problem with a suboptimal solution. I had to upload the report with no filter active (not ideal but no major issue), and remove the ability for the user to save filters by ticking the "Don't allow end user to save filters on this report" setting.
The filter now works as expected, just with a few compromises.
5 Replies
- AnkitKukrejaSuper User
Hi! JackL91
There could be a issue in the visual, did you try this in any other report? In case it has same behavior then you should raise a ticket to Microsoft support.
- JackL91New Member
Hi Ankit,
Thanks for the reply. Based on your suggestion I created a dummy workbook with a simple excel csv table, followed the same steps and ran into the same issue where after I'd saved the workbook - the filter function stopped working.
- AnkitKukrejaSuper User
Hi! JackL91
Also, I hope this visual is Microsoft certified? If yes then you should maybe create a support request.
- AnonymousNot applicable
Hi JackL91
Has your problem been resolved? If so, could you share your solution so that others with similar issues can benefit from it?
Best Regards,Jayleny
- JackL91New Member
Hi Jayleny,
I have resolved the problem with a suboptimal solution. I had to upload the report with no filter active (not ideal but no major issue), and remove the ability for the user to save filters by ticking the "Don't allow end user to save filters on this report" setting.
The filter now works as expected, just with a few compromises.