top of page

Measure Killer Feedback

Updated: Feb 11

If you have downloaded and tried out our tool, we are happy to hear your feedback in the comments at the bottom of this page.


Please make sure to read what measure killer can and what it cannot do before commenting.

Version 2.9.2 is out, try the new model- and report similarity features.

 
 
 

520 Comments


Aviv
Feb 24

Hi,


I am trying to run Measure Killer (version 2.9.2) on my report, which is saved as a PBIX file, and I am receiving the following error:

“zipfile.BadZipFile: File is not a zip file”

“Failed to open …pbix as a ZIP archive.”

Could you please clarify why Measure Killer is attempting to open the PBIX file as a ZIP archive?

I would also appreciate your guidance on how to resolve this issue. The file opens normally in Power BI Desktop, and no sensitivity label appears to be applied.

Thanks

Aviv


[Error Message]

Version 2.9.2

Traceback (most recent call last):

File "measurekiller\definition_misc\definition_classifier.py", line 60, in classify_layout_type

File "zipfile.py", line 1304, in __init__

File "zipfile.py", line 1371, in _RealGetContents

zipfile.BadZipFile: File is…


Like
Replying to

Is the file maybe read-only or something strange is happening with it? I do not know why it would throw this error if you have no sensitivity label etc. applied

Somehow the tool cannot access the file

Like

Guest
Feb 23

do nit have kill table slect all dax object by defulat, i unslected one thinking ti would only kill that and it killed everyhting else just fyi~thanks

Like
Replying to

There is a restore button on top to bring back to life any DAX artifacts you removed with Measure Killer.


But we will take a look, thanks for your feedback

Like

Alex
Feb 13

Enhancement Request: Allow ignoring not supported dataset types. I'm using "Shared model online" to analyze one dataset and all its dependencies. One dependecy seems to be a live semantic model connected to my dataset and I get the error "this type of dataset is not supported. This occurs if the dataset is a scorecard, lakehouse, report usage metrics model or a live semantic model connected to Azure Analysis Services." This is okay, but unfortunately, this error causes the loading process to abort completely, making it impossible to analyse my dataset and all other dependencies.

Like
Replying to

Is your semantic model in a Pro workspace? If yes we know what the issue is, so please contact us to have this fixed (unfortunately it is due to a Microsoft bug).

Like

roberts17
Feb 05

Enhancement request: Allow ignoring of a Metrics/Measures table from the warning of 'Unused tables with no used columns was detected' Perhaps a user configuration option to allow exclusion of tables by a developer's custom name. For example, many developers put all their DAX measures in a clean table (M script or DAX table without columns). Developers often use the same custom name for this measures table across all models (e.g. of names I've used for this table: Measures, Metrics, _Metrics).

Like
Replying to

Hi, thanks for your feedback. We only show this warning though if you have at least one column in your table so that’s how we try to exclude proper measure tables.


Does your measure table still have a column? You can remove it and then the warning should go away.

Like

Ondřej Barták
Jan 29

I have import model (large storage format) with 27 reports downstream for which I tried to run Shared Model Online analysis (Developer), but I am not able to complete it and get (un)used columns, measures etc.


There are 2 composite models connected to it downstream, but the error is the same even if I uncheck them before running Analyze. Is that what the error message is referring to?


How can I complete my analysis?


I get this error message:


[Error Message]

Version 2.9.1

Traceback (most recent call last):

File "measurekiller\tenant_semantic_model\mixins\semantic_base.py", line 449, in execute_query

File "measurekiller\tenant\tenant_api.py", line 911, in make_api_post_request

File "measurekiller\tenant\tenant_api.py", line 509, in _handle_response

measurekiller.tenant_misc.tenant_custom_exceptions_api.BadRequestError: Bad request 400: {"error":{"code":"DatasetExecuteQueriesError","pbi.error":{"code":"DatasetExecuteQueriesError","parameters":{},"details":[{"code":"DetailsMessage","detail":{"type":1,"value":"Failed to execute the DAX query."}},{"code":"AnalysisServicesErrorCode","detail":{"type":1,"value":"3239575574"}}]}}}


During handling of the…


Like
Replying to

Is any of the models in a Pro workspace? If yes please send us your Tenant ID by email to fix this.

Like
bottom of page