Data Science

How to create a calculated field to sum two columns in Tableau?

EL Asked by Elena Rodriguez · 06-04-2025
0 upvotes 12,573 views 0 comments
The question

I'm working with a sales dataset and I need to combine "Shipping Cost" and "Product Base Price" into a single "Total Cost" metric. I tried simply dragging both onto the shelf, but that just creates two separate axes. How do I write a calculation that adds these two measures together at the row level? Also, how should I handle the calculation if some rows have null values in one of the columns, as my current attempts are returning blank results?

3 answers

0
SA
Answered on 07-04-2025

To sum two columns in Tableau, you need to create a Calculated Field. Right-click in the Data pane and select "Create Calculated Field." In the editor, simply write your formula: [Column A] + [Column B].

However, a common trap is the "Null" issue. In Tableau, Value + Null = Null. To prevent this, wrap your fields in the ZN() (Zero Null) function, which converts nulls into zeros. Your final formula should look like this: ZN([Shipping Cost]) + ZN([Product Base Price]). Once created, you can drag this new measure into your view just like any other field.

0
DA
Answered on 08-04-2025

Is there a difference between doing this calculation in the "Data Source" tab versus doing it inside a "Worksheet"? I noticed that when I do it in the worksheet, the aggregation changes depending on what dimensions I add to the rows.

PA 09-04-2025

David, that’s a great observation. If you create the calculation as [A] + [B], Tableau adds the values for every single row first, and then sums them up based on your view (Row-Level Calculation). If you write it as SUM([A]) + SUM([B]), Tableau sums all of A and all of B separately based on your filters and then adds the two totals together (Aggregate Calculation). For "Total Cost," you generally want the row-level version to ensure accuracy across different levels of detail.

0
BR
Answered on 11-04-2025

If you have multiple columns to sum, you can also use the IFNULL() function as an alternative to ZN(), allowing you to specify a different default value if zero doesn't make sense for your specific data model.

EL 12-04-2025

I agree with Brenda. ZN() is the fastest way for math, but IFNULL() is great for flexibility. I recently used it to sum several tax columns where I needed the fallback to be a baseline rate rather than just zero. It keeps the data much cleaner for complex financial reporting.

Share your thoughts

Your email address will not be published. Required fields are marked (*)

Professional Counselling Session

Still have questions?
Schedule a free counselling session

Our experts are ready to help you with any questions about courses, admissions, or career paths. Get personalized guidance from industry professionals.

Request a Call Back

Search Online

We Accept

We Accept

Follow Us

"PMI®", "PMBOK®", "PMP®", "CAPM®" and "PMI-ACP®" are registered marks of the Project Management Institute, Inc. | "CSM", "CST" are Registered Trade Marks of The Scrum Alliance, USA. | COBIT® is a trademark of ISACA® registered in the United States and other countries.

Book Free Session