Forum Discussion

nitinrungta's avatar
nitinrungta
Frequent Visitor
4 years ago

Field Parameters in Measures

Is there a way to use the Field Parameters in Measures for different calculations?

13 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    It depends on what you want to do.

     

    Field Parameters create a Custom table, and you can reference the columns from this table in your measures and work with their values.

     

    Can you provide a more specific example you want to achive?

     

    Kind regards,
    José
    Please mark this answer as the solution if it resolves your issue.
    Appreciate your kudos! 🙂

    • nitinrungta's avatar
      nitinrungta
      Frequent Visitor

      Anonymous I understand what you are trying to say, but I really don't think that really helps in any way. Thanks, anyway.

      I will really consider you a Guru if you can tackle this for me.

       

      I have a field parameter table of three measures:
      vs PY
      vs PM
      vs PW

       

      I also have a separate Color Measure

      ColorMeasure PM = 

      VAR myEventResult =
      [vs PM]

      RETURN
      SWITCH (
      TRUE (),

      myEventResult > 0.05, "#73B761",
      myEventResult > 0 && myEventResult <= 0.05  , "#f7db03",
      myEventResult <= 0, "#CD4C46"
      )

      Now, this is what I want to achieve. Very short and simple -

       

      When I select vs PY then I want the color measure to change from [vs PM] to [vs PY]

       

      How do I do this? Greg_Deckler amitchandak  please could you provide your valuable insight.

      • data-wrangler's avatar
        data-wrangler
        New Member

        Hi,

         

        As per your original questions; "Is there a way to use the Field Parameters in Measures for different calculations?"... I'm not sure if this is totally necessary to achieve the dynamic colour of bars in your graph you've refered to as your actual challenge, based on your selected measure in your field parameter slicer. With that said, I could be interpreting the challenge incorrectly.

        You may be able to refer to the measure itself?

        Try this calculation:

        ColourMeasure =

        VAR _SelectedValue = // This Variable is a workaround for using selectedvalue() with the new field parameters functionality
        CONCATENATEX (
            SELECTCOLUMNS (
                SUMMARIZE ( 'Measure Selector', 'Measure Selector'[Measure], 'Measure Selector'[Parameter Fields]),
                'Measure Selector'[Measure]
            ),
            'Measure Selector'[Measure], ", " )


        VAR _ColorPY =

        SWITCH (

        TRUE (),

        [vs PY] > 0.05, "#73B761", -- Change to whatever desired value threshold and color
        [vs PY] > 0 && [vs PY] <= 0.05  , "#f7db03",
        [vs PY] <= 0, "#CD4C46"

        )

        VAR _ColorPM =

        SWITCH (
           
        TRUE (),

        [vs PM] > 0.05, "#73B761",
        [vs PM] > 0 && [vs PM] <= 0.05  , "#f7db03",
        [vs PM] <= 0, "#CD4C46"

        )

        VAR _ColorPW =

        SWITCH (
           
        TRUE (),

        [vs PW] > 0.05, "#73B761",
        [vs PW] > 0 && [vs PW] <= 0.05  , "#f7db03",
        [vs PW] <= 0, "#CD4C46"

        )

        RETURN

        SWITCH(
            TRUE()
            ,_SelectedValue = "vs PY", _ColorPY
            ,_SelectedValue = "vs PM", _ColorPM
            ,_SelectedValue = "vs PW", _ColorPW
        )

        The calculation may seem verbose, but seeing as you only have 3 measures in your field parameter, its relatively straight forward and gets the job done.

        Let me know if this solves your issue?






    • Anonymous's avatar
      Anonymous
      Not applicable

      Anonymous , Let's consider that I create a field parameter with 2 measures A and B. Now could you please tell me what syntax is apt to reference the measure A in another new measure calculation?

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hello Anonymous ,my requirement is similar to nitinrungta . I need to create a field parameter called 'Month Year'  (Eg: May 2022) and need to use this parameter in my YTD calc. This parameter needs to act as a slicer and every new selection should be reflecting in the YTD. If I select June 2022, then YTD calc will take upto June 2022. By default it should show YTD till current month.

    • nitinrungta's avatar
      nitinrungta
      Frequent Visitor

      Hi,

      You don't need a field parameter for this. Just a clever Measure should take care of this.

      • Anonymous's avatar
        Anonymous
        Not applicable

        Okay, so this is the base calc :

        Measure_to_get_total = CALCULATE ( SUM ( sales_table[Revenue] ), FILTER(sales_table, YEAR( sales_table[date])=2022 and month <= selected month))

         

        Slicer selected : May 2022  (I need to get sum of sales from Jan 2022 to May 2022)

        No slicer selected : Current Month (I need to get sum of sales from Jan 2022 to current month)

         

        How can we achieve this with measure? The highlighted red part is what needs to be dynamic.

        I tried by using 'selectedvalue' but it does not seem to be working 

  • PaulDBrown's avatar
    PaulDBrown
    Community Champion

    Can you please share non-confidential data or a link to a sanitized PBIX file?

  • deviln's avatar
    deviln
    Frequent Visitor

    Hi nitinrungta ,

     

    Were you able to proceed further with this?

    We need to read the field measure dynamically and its value dynamically, based on the field paramter selected in the slicer. I am also stuck with reading the measure and its value dynamically.

    Would like to connect and discuss this further.

     

    TIA

  • Hi nitinrungta , deviln ,

     

    did either of you ever manage to actually solve this issue?

     

    I think in almost all cases you can solve this issue in different ways too (for instance by using calculationgroups), but there is actually one specific scenario where you really cannot do without (afaik).

     

    I need to "interpret" the Field Parameter (rather than retreiving its name), because I'm using this to model OLS into the report, which actually deletes (hides) the normal measures from the report, breaking visuals. Refering to an actual measure, will only result in deleting the referring measure too. However, I've come to the point where I believe this simply is not possible.

     

    I've seen the information from Alberto Ferrari, where he's describing the technical implementation of Field Parameters (basically leveraging extended properties and grouped columns). The takeaway from this is that Field Parameters seem to depend on the client application to handle this, effectively making it impossible to retreive the actual value in another measure.

     

    I wanted to vote for this suggestion, but that link seems to fail?

     

    Cheers