Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

Measure is creating duplicate rows in a table

All,
 
I created a measure to return the greater of 0 or the difference Between Baseline - CapEx and Forecast CapEx. The measure is returning the correct value for each Project ID I filter on, but it's also creating additional rows (with the same project ID I filtered on) for every Project Name. My guess is that this behavior is due to how the data model is configured, but I wanted to reach out to see if anyone has seen this before and has a DAX workaround.

Release CapEx = MAX( 0,'Baseline'[Baseline - CapEx] - [Forecast CapEx])
 


 
 

 

Need Help
  • amitchandak's avatar
    amitchandak
    5 years ago

    Anonymous , Couple of reasons I can think of.

    1. These measures are coming from different tables and one of them have a problem with  project join

    2. Both table has project ID, and there is a common project table(Project Dimension) and you took project or project name from a fact, not from Dimension

    3. One of the measures is using all/all selected. even possible when they are from the same table

     

     

6 Replies

  • Ashish_Mathur's avatar
    Ashish_Mathur
    Super User
    5 years ago

    Hi,

    Does this work?

    =if(isblank('Baseline'[Baseline - CapEx]),blank(),MAX( 0,'Baseline'[Baseline - CapEx] - [Forecast CapEx]))

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      Ashish_Mathur  It works in terms of producing the numbers I want, but the solution I found earlier was to bring fields in from a table other than my project fact table. Thank you.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Hi Anonymous 

    Can you please provide more info with screenshots, input and required output in table format for the community so that you ask can be better understood and resolved quickly.

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      Anonymous No, I can't actually, due to confidentiality. I was hoping that someone would recognize the behavior and maybe provide some clues as to what could be causing this behavior. 

       

      If that's not you; thanks anyway for trying.

      • amitchandak's avatar
        amitchandak
        Super User
        5 years ago

        Anonymous , Couple of reasons I can think of.

        1. These measures are coming from different tables and one of them have a problem with  project join

        2. Both table has project ID, and there is a common project table(Project Dimension) and you took project or project name from a fact, not from Dimension

        3. One of the measures is using all/all selected. even possible when they are from the same table