Forum Discussion

eddd83's avatar
eddd83
Icon for Resolver I rankResolver I
2 years ago

How find the most computation expensive calculated columns

So in the data model that I inherited, there are a number of calculated columns in the main table. By chance, I noticed if I delete this particular "end customer" column, it would cut the time to ope...
Need Help
lbendlin's avatar
lbendlin
Icon for Super User rankSuper User
2 years ago

var checkSource = VALUES(Fact_Table[Source])

eddd83's avatar
eddd83
Icon for Resolver I rankResolver I
2 years ago

same error. I've only included a portion of the actual logic. 

  • lbendlin's avatar
    lbendlin
    Icon for Super User rankSuper User
    2 years ago

    you are attempting to return a table inside a row. 

     

    remove lines 2,3 and 12

  • eddd83's avatar
    eddd83
    Icon for Resolver I rankResolver I
    2 years ago

    So when i add back in the related variables, i get this message. FYI this is only 1 of many related variables in this logic)

     

  • lbendlin's avatar
    lbendlin
    Icon for Super User rankSuper User
    2 years ago

    remember that EVALUATE must return a table.  RELATED will always return a scalar value for a single column. You are mixing too many concepts at once.

     

    Check your data model, then formulate the right DAX. You can also let the "DAX Query View"  do the heavy lifting for you when you ask it to create the code for a calculated column or a measure etc.

  • eddd83's avatar
    eddd83
    Icon for Resolver I rankResolver I
    2 years ago

    the whole point of this exercise was to compare different columns and why some columns have a greater effect on the model efficiency/speed. The above logic is the correct DAX for my business case.