powered Desktop August update crashes quite often

[konstantinos]

Hi All,

Did anyone else noticed that PBI Desktop August update crashes quite often when writing a measure and click enter to apply changes? 

This is happening too often for me..specially when changing an existing one or copy DAX from i.e. another file or Daxformatter

Can we have the option for autorecover sort of office docs..?

[AlexGorev]

We do not see this type of crashes in our environment. Can you help us to reproduce and fix this!? Can you share the details of the error message you are getting and what are the steps to get there? Also please specify the OS of your machine.

Thanks,

Alex.

[konstantinos]

@AlexGorev sorry I forgot to mention it..

I run windows 10 & PBI Desktop v 2.26.4128.403..I will try to reproduse the steps..Usually this happens when a formula has some errors & instead of getting warnings it crashes..( i.e calculate scalar value when the column is text ) But can happen with working formulas..If try to change a formula already created most of the times it crashes..If I delete it and create a new one with the same formula it works..

I don't have a specific example with working formula now..but

I made on purpose error in a measure to crash it..There are the steps:

I have already the measure in the data model ( doens't matter the complexity, it happens with one line also)

Period Average Lead (hours) =
VAR periodaverage =
    CALCULATE (
        AVERAGE ( Issues[Solving Time Customer] );
        Issues[Solving Time Customer] > 0
    )
RETURN
    SWITCH (
        [Period Selector];
        1; CALCULATE (
            periodaverage;
            FILTER (
                ALL ( 'Calendar' );
                'Calendar'[MonthOfYear] = MONTH ( TODAY () )
                    && 'Calendar'[Year] = YEAR ( TODAY () )
            )
        );
        2; CALCULATE (
            periodaverage;
            FILTER (
                ALL ( 'Calendar' );
                'Calendar'[Year] = YEAR ( TODAY () )
            )
        );
        3; CALCULATE (
            periodaverage;
            FILTER (
                ALL ( 'Calendar' );
                'Calendar'[MonthOfYear]
                    = MONTH ( TODAY () ) - 1
                    && 'Calendar'[Year] = YEAR ( TODAY () )
            )
        );
        4; CALCULATE (
            periodaverage;
            FILTER (
                ALL ( 'Calendar' );
                'Calendar'[Year]
                    = YEAR ( TODAY () ) - 1
            )
        );
        5; CALCULATE ( periodaverage; ALL ( 'Calendar' ) )
    )

Now I detele the VAR (only the word not the variable ) so the formula don't work cause the structure is wrong )..Hit enter and 

Then 

If I choose close the program of course it quits PBI...Debug opens 

Hope this helps..Let me know if you anything else can help...

[AlexGorev]

Thanks @konstantinos! I opened a tracking bug in our system #5634531. First we'll try reproducing this following your steps. I'll keep you updated on the progress...

Thanks again,

Alex.

[Sean]

I'm on Win 10 Pro and PBI Version: 2.26.4128.403 => my PBI Desktop does Not crash

I just finished recreating a Data Model with so far 32 Measures and 12 Calculated Columns - no crashes - I could only imagine how frustrating it would be!

But my Excel crashes - I keep an Excel file open when working on my Data Model where I enter all my Measures and Calculated Columns just to have a record of ALL formulas in one place - I wish they would have one place where you can go and see ALL Measures for the Data Model for ALL tables.

Sometimes that Excel file won't let me Save the changes - asks me to rename the file - but won't let me save the renamed version either. I have to open a new file and move the Sheets to the new file to be able to keep the changes - very frustrating and started happening after the Win 10 update in July.

[Greg_Deckler]

I have not noticed this at all. I spent some time trying to crash it and could not. I am at version 2.26.4128.403. I am on Windows 10.

[ashishrj]

Even I have noticed this. Also renaming measure or calculated column if already used in report crashes the report. We cannot even undo this. I agree with konstantinos auto recovery could be a better option to avoid rework.