Sure, I can help you with any questions you have about Microsoft Power BI and DAX. Please feel free to ask me any questions you have about modeling, data visualization, or performance optimization.

This measure appears to be a financial measure that is switching between two different calculations based on the value of the ID_Measure column in the Measures_Financials table. The first calculation is the sum of the Actual Sekm column from the Fact_Financials table, filtered to only include rows where the Category column is "Net Revenue". The second calculation is the sum of the Actual Sekm column from the Fact_Financials table, filtered to only include rows where the Category column is "Ebita".

The measure is using the IF and SWITCH functions to determine which calculation to perform based on the value of the ID_Measure column. The HASONEVALUE function is used to ensure that only one value is selected for ID_Measure, and the VALUES function is used to retrieve the value of ID_Measure. If there is no value selected, the measure returns 0.

It is a bit difficult to give specific advice without more information about the data and how this measure is used in the report but some of the things that could be looked at are:

• Check the cardinality of the ID_Measure column in the Measures_Financials table, to ensure that it has a one-to-one relationship with the Fact_Financials table.
• Confirm that the measure is returning the expected results.
• Confirm that the measure is performing well in terms of performance, as the use of multiple filters and calculations in the measure can cause performance issues.
• Check the data model for any unnecessary relationships and columns that might be affecting performance negatively.
• Consider using a simpler approach if the requirement allows it.

Please let me know if you have any more information or questions.

Yes, there are several ways to make the measure less compute-intensive:

1. Instead of using the SWITCH function to switch between two different calculations, you could use the IF function to check for the value of ID_Measure and then perform the appropriate calculation. This would eliminate the need for the SWITCH function and potentially improve performance.

2. Instead of using the HASONEVALUE function to check for a single value, you can use the COUNTD(Measures_Financials[ID_Measure]) = 1, this way you don't need to use the HASONEVALUE function.

3. You could consider to use a variable to store the selected ID_Measure value, and then use that variable in the calculations, this way you can avoid the use of the VALUES function.

Here is an example of how the modified code could look like:

Copy code
Financials_AC_Switch = 
VAR ID_Measure = SELECTEDVALUE(Measures_Financials[ID_Measure])
RETURN 
    IF(COUNTD(Measures_Financials[ID_Measure]) = 1,
        IF(ID_Measure = 1,
            CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Net Revenue"),
            IF(ID_Measure = 2,
                CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Ebita"),
                BLANK()
            )
        ),
        BLANK()
    )

Regarding the comments:

Copy code
Financials_AC_Switch = 
    --check if only one measure is selected
    VAR ID_Measure = SELECTEDVALUE(Measures_Financials[ID_Measure])
    -- Return the appropriate calculation based on ID_Measure value
    RETURN 
        IF(COUNTD(Measures_Financials[ID_Measure]) = 1,
            -- check if ID_Measure is 1
            IF(ID_Measure = 1,
                -- Sum of actual Sekm for category 'Net Revenue'
                CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Net Revenue"),
                -- check if ID_Measure is 2
                IF(ID_Measure = 2,
                    -- Sum of actual Sekm for category 'Ebita'
                    CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Ebita"),
                    -- If none of the conditions met return BLANK
                    BLANK()
                )
            ),
            -- If none of the conditions met return BLANK
            BLANK()
        )

This way you can have a better understanding of what the measure is doing. Please let me know if this helps or if you have any other questions.

Yes, you're correct that some comments may not be necessary if the code is self-explanatory. The main goal of comments is to provide information that is not immediately obvious from the code itself. In this case, comments could be added to explain the purpose of the measure, the logic behind certain decisions, or any other information that may not be clear from the code alone.

Regarding the use of docstring-style comments, it's not a common practice in DAX, however, you can use comments in that way if it makes sense for your use case and team. A docstring comment can be added at the top of the measure, providing a brief overview of the measure, its inputs, and expected outputs.

Here's an example of how the code might look with more relevant comments:

Copy code
Financials_AC_Switch = 
    --Use a variable to store the selected ID_Measure value
    VAR ID_Measure = SELECTEDVALUE(Measures_Financials[ID_Measure])
    -- Return the appropriate calculation based on ID_Measure value
    RETURN 
        IF(COUNTD(Measures_Financials[ID_Measure]) = 1,
            -- check if ID_Measure is 1
            IF(ID_Measure = 1,
                -- Sum of actual Sekm for category 'Net Revenue'
                CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Net Revenue"),
                -- check if ID_Measure is 2
                IF(ID_Measure = 2,
                    -- Sum of actual Sekm for category 'Ebita'
                    CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Ebita"),
                    -- If none of the conditions met return BLANK
                    BLANK()
                )
            ),
            -- If none of the conditions met return BLANK
            BLANK()
        )

or

Copy code
"""
Financials_AC_Switch measure:
    Purpose: 
        - Return the sum of actual Sekm based on the selected ID_Measure value
    Input: 
        - ID_Measure: ID_Measure column from Measures_Financials table
    Output:
        - Sum of actual Sekm based on the selected ID_Measure value
"""
Financials_AC_Switch = 
    VAR ID_Measure = SELECTEDVALUE(Measures_Financials[ID_Measure])
    RETURN 
        IF(COUNTD(Measures_Financials[ID_Measure]) = 1,
            IF(ID_Measure = 1,
                CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Net Revenue"),
                IF(ID_Measure = 2,
                    CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Ebita"),
                    BLANK()
                )
            ),
            BLANK()
        )

Please let me know if this helps or if you have any other questions.

Initial DAX-measure:

Copy code
Financials_AC_Switch = 
IF(
    HASONEVALUE(Measures_Financials[ID_Measure]),
    SWITCH(
        VALUES(Measures_Financials[ID_Measure]),
        1, CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Net Revenue"),
        2, CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Ebita")
    ),
    0
)

Modified DAX-measure with docstring-styled-comment:

Copy code
"""
Financials_AC_Switch measure:
    Purpose: 
        - Return the sum of actual Sekm based on the selected ID_Measure value
    Input: 
        - ID_Measure: ID_Measure column from Measures_Financials table
    Output:
        - Sum of actual Sekm based on the selected ID_Measure value
"""
Financials_AC_Switch = 
    --Use a variable to store the selected ID_Measure value
    VAR ID_Measure = SELECTEDVALUE(Measures_Financials[ID_Measure])
    -- Return the appropriate calculation based on ID_Measure value
    RETURN 
        -- check if only one measure is selected
        IF(COUNTD(Measures_Financials[ID_Measure]) = 1,
            -- check if ID_Measure is 1
            IF(ID_Measure = 1,
                -- Sum of actual Sekm for category 'Net Revenue'
                CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Net Revenue"),
                -- check if ID_Measure is 2
                IF(ID_Measure = 2,
                    -- Sum of actual Sekm for category 'Ebita'
                    CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Ebita"),
                    -- If none of the conditions met return BLANK
                    BLANK()
                )
            ),
            -- If none of the conditions met return BLANK
            BLANK()
        )

Please note that the modified DAX-measure should be tested with the actual data to ensure it's returning the expected results and that it's performant. Let me know if you have any more questions or if there's anything else I can help you with.

I apologize for the confusion, you are correct that COUNTD is not a function in DAX. To check if there is only one value of ID_Measure selected, you can use the following function :

Copy code
COUNTROWS(FILTER(VALUES(Measures_Financials[ID_Measure]), TRUE())) = 1

Here is the revised modified DAX-measure:

Copy code
Financials_AC_Switch = 
    --Use a variable to store the selected ID_Measure value
    VAR ID_Measure = SELECTEDVALUE(Measures_Financials[ID_Measure])
    -- Return the appropriate calculation based on ID_Measure value
    RETURN 
        -- check if only one measure is selected
        IF(COUNTROWS(FILTER(VALUES(Measures_Financials[ID_Measure]), TRUE())) = 1,
            -- check if ID_Measure is 1
            IF(ID_Measure = 1,
                -- Sum of actual Sekm for category 'Net Revenue'
                CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Net Revenue"),
                -- check if ID_Measure is 2
                IF(ID_Measure = 2,
                    -- Sum of actual Sekm for category 'Ebita'
                    CALCULATE(SUM(Fact_Financials[Actual Sekm]), Fact_Financials[Category] = "Ebita"),
                    BLANK()
                )
            ),
            BLANK()
        )

The modified DAX-measure should be more performant than the initial one as the use of variable to store the selected value of ID_Measure and the use of IF function instead of SWITCH function to check for the value of ID_Measure and perform the appropriate calculation can reduce the number of calculations needed. Please let me know if you have any further questions or concerns.

In general, using IF-functions is less compute-intensive than using switch-statements in DAX because when using a switch-statement, DAX will check all the conditions in the switch statement, one by one, until it finds a match. Whereas using an IF-function, DAX will check the first condition and if it's true, it will return the result, and if it's false, it will check the next condition and so on. This means that if the first condition is true, DAX will not need to check the other conditions, which can save some computation time.

It's difficult to give an exact estimate of how much time you can save by using IF-functions instead of switch-statements because it can depend on several factors such as the size of your data, the complexity of the calculations, and the specific use case. However, in general, you can expect that using IF-functions instead of switch-statements can help improve performance in cases where you have a lot of conditions to check and/or a large amount of data.

In addition, using a variable to store the selected value of ID_Measure and then using it in the calculations can also improve performance, as it eliminates the need to use the VALUES function multiple times, which can be computationally expensive.

It's always best practice to test the performance of the modified code with your actual data and to monitor it to ensure that it's performant. Please let me know if you have any other questions or concerns.