Forum Discussion
Issue with Filter by List by Devscope Visual
- 2 years ago
I found a solution that is currently working for me (I'm on PBIRS January 2023 version). This youtube video got me pointed in the right direction:
https://www.youtube.com/watch?v=mqDDgPDhSE4
If you have a PBIX file with a previously working version of the FilterByList visual, you can
- export a template of your dashboard (PBIT).
- Then you open the PBIT template file in 7zip or Winzip and find the 'FilterByList507A2DBEC31244C8AAABDE9BA541F723' folder within Reports>Custom Visuals.
- Extract the files within and repackage/zip them up as a new file ending in pbiviz (e.g. CustomVisual.pbiviz)
- Back in your PBIX file, in the Visualizations pane, select ... and then 'Import a visual from a file'
- Select your newly packaged pbiviz file and you should get a messaage 'Import successful'
Between steps 3 and 4, I did something that I'm not sure is necessary. I read in this thread about the need to modify all references of a 'guid' variable throughout the files in the FilterByList folder. I might've done overkill on this, but I'll try to explain.
- The folder inside the PBIT file was named 'FilterByList507A2DBEC31244C8AAABDE9BA541F723' so I appended that name with 'XX' to become 'FilterByList507A2DBEC31244C8AAABDE9BA541F723XX.'
- Within the folder is a file 'package.json' - it contained a 'guid' variable and also another reference to FilterByList507A2DBEC31244C8AAABDE9BA541F723. In both cases I appended the values with 'XX'
- Within the folder there is another folder 'resources' and a json file called 'FilterByList507A2DBEC31244C8AAABDE9BA541F723' I appended the 'XX' to that filename as well.
- I opened that file and did a find/replace on all references to '507A2DBEC31244C8AAABDE9BA541F723' in order to append them with 'XX' - there were probably 5-10 of them.
- I saved all those changes to the files before extracting/zipping them.
Anyway, good luck and you can PM me if you need any help.
I think we need AS MANY PEOPLE AS POSSIBLE to email [email protected]
as them to
1) revert back to old version until they fix the bugs in the new version
2) release the old version as a free stand alone slicer
3) expand the number of values you can filter to in the free version. even just from 20 to 100 would be such a huge impact
- Anonymous2 years agoNot applicable
The problem there is the developer is only going to see such a campaign as an indication of greater demand, and is more likely to increase the price than it is to back down.
What I'm blown away by is that v1 was actually released under GNUv3, so is legally free software. Microsoft forcing an upgrade from a version under GNU to a newer version under private copyright is a defacto theft of the commons, as there is no longer any way for anyone to use v1 legitimately despite it still existing.
I'm completely behind building a marketplace for good ideas to incentivise the improvement of the Power BI ecosystem. But doing so via ensh1tification of preexisting GNU-released solutions to retroactively make a buck, that's not on.