Tools like these, and there are not so many, can be very valuable. Having a lean & clean model is important in many ways, no discussion on that. When you have control over your datasources making use of RemoveColumns is maybe not so bad but when you don't it is a thing to consider. Any changes to your datasource like columns being removed will result in an error when the model gets refreshed. Nevertheless, the potential value of MeasureKiller is huge.
Yes I would buy that tool if something could help identify unused columns across a live dataset used by multiple reports! When I started watching this I was optimistic that this was the tool. Very Cool tool but bummed it won’t work with thin reports.
Great tool! But to be an awesome tool, I think I would add the information about the folder and subfolders where they're saved, and also, the table and columns names of those measures. Great job guys
It's so clean, great tool. Thanks that the free version actually helps. though I don't think the tool recognizes when a column is used to order an other column ex index columns.
I have a base dataset that has multiple reports using it Would be great if the tool can load multiple related reports and scan all of them together to find unused measures/columns.
If anyone could make something to scan these it would be a GAME CHANGER. However I think it would only work with premium where it can use the SMLA endpoint :\ Otherwise Microsoft would need to do this
Hey pal i am big fan of yours, "POWER BI"☺ i have a question about power query we can undo(means delete) the step, So is there any way we can redu(means to get last deleted step) the step deleted step could be in any line in applied steps. I am asking because sometimes the step is big we write m query so that we just can redu the step instead of to write m query again.
Sadly no undo or control Z in Power Query! My best practice is to duplicate the query and make changes there, saving your original query. When you're done then copy/paste the advanced editor code back into the original one! I wished there was an easier way, but I've also made the mistake of accidentally deleting an applied step!
Super!! How can you identify what to kill in your model if all your reports read from PBI service a central data model which contains all the measures?
@@jazriopk we talk about that limitation towards the mid to end of the video as well. Not really possible to check with multiple reports connected to one model today. :\
If a measure is only used in another measure it should find it without any problems. If you can give me a concrete example I can take a look though, thanks!
Tools like these, and there are not so many, can be very valuable. Having a lean & clean model is important in many ways, no discussion on that.
When you have control over your datasources making use of RemoveColumns is maybe not so bad but when you don't it is a thing to consider. Any changes to your datasource like columns being removed will result in an error when the model gets refreshed.
Nevertheless, the potential value of MeasureKiller is huge.
Yes I would buy that tool if something could help identify unused columns across a live dataset used by multiple reports! When I started watching this I was optimistic that this was the tool. Very Cool tool but bummed it won’t work with thin reports.
we are working on it ;)
@@MeasureKiller Fantastic! Where is the best place to stay up to date so that I can know when this is released. Thanks for the great work!!!!
Great tool! But to be an awesome tool, I think I would add the information about the folder and subfolders where they're saved, and also, the table and columns names of those measures. Great job guys
Same! Hopefully that comes out some day
It's so clean, great tool. Thanks that the free version actually helps.
though I don't think the tool recognizes when a column is used to order an other column ex index columns.
Thanks for your feedback! Do you mean ‚sort by‘ another column? Not sure exactly what you are referring to.
I have a base dataset that has multiple reports using it Would be great if the tool can load multiple related reports and scan all of them together to find unused measures/columns.
If anyone could make something to scan these it would be a GAME CHANGER. However I think it would only work with premium where it can use the SMLA endpoint :\
Otherwise Microsoft would need to do this
Measure Killer can already do this in its current version
@@MeasureKiller I'll have to check it out then!
Hey pal i am big fan of yours, "POWER BI"☺ i have a question about power query we can undo(means delete) the step, So is there any way we can redu(means to get last deleted step) the step deleted step could be in any line in applied steps. I am asking because sometimes the step is big we write m query so that we just can redu the step instead of to write m query again.
Sadly no undo or control Z in Power Query! My best practice is to duplicate the query and make changes there, saving your original query. When you're done then copy/paste the advanced editor code back into the original one! I wished there was an easier way, but I've also made the mistake of accidentally deleting an applied step!
Can we use this on ssas
I don't think so today! Looking at the tool it appears to only connect to local models open on your machine.
Correct!
Super!! How can you identify what to kill in your model if all your reports read from PBI service a central data model which contains all the measures?
Currently we can only analyze single reports!
@@jazriopk we talk about that limitation towards the mid to end of the video as well. Not really possible to check with multiple reports connected to one model today. :\
I'm afraid this has too many false positives, it's not usable.
Can you show me where this is happening? we are always looking to improve our tool!
@@MeasureKiller this seems to occur when there are certain degrees of dependencies between measures.
If a measure is only used in another measure it should find it without any problems.
If you can give me a concrete example I can take a look though, thanks!