Simple Calculation Blows Up Table Visualization

[Anonymous]

I created a simple table visualization with 57 rows of data. I'm trying to perform a simple calculation with a new measure, calculate(100-sum(price)) but when I do, the table explodes into 1000s of records, majority of this new measure being 100. I'm assuming the calculation is performing on the blank rows.  How do I prevent it from calculating on the blank rows and to just perform the calculation on the original 57 rows of data?

[gdarakji]

It can also be that the fields in the table and the ones used in the measure are not related properly in the model. This will result in a cross join between all used tables and thus the thousands of rows you are getting.

[Jihwan_Kim · Accepted solution]

Hi, @Anonymous 

I am not sure how you created your measure for 57 rows in table visualization, but please try something like the below.

New measure =
IF (
[your measure that created 57 rows] <> BLANK (),
100 - [your measure that created 57 rows]
)

Hi, My name is Jihwan Kim.

If this post helps, then please consider accept it as the solution to help other members find it faster, and give a big thumbs up.

Linkedin: linkedin.com/in/jihwankim1975/

Twitter: twitter.com/Jihwan_JHKIM