Using values from multiple cards (same dataset) as a calculated field

lee0789
lee0789 Member
in Magic ETL

Hi all,

First time posting here, and I'm just looking for some guidance on if this is even possible. Any help is greatly appreciated!

We have created a report in Domo that is using 3 separate cards, all from the same dataset. Each card has a different "Total" because in Analyzer, there are various factors filtered out.

In a perfect world, I would like to know if there is a way to save & use a "Total" value from each card and use it as a dynamic field (whether through a calculated field, an ETL, etc.). If not, I assume I'll probably need to create CASE statements to replicate the filters of each card.

Also, as a bonus question, I am really catching on to calculated fields, but the one thing that I cannot figure out is the correlation between FIXED BY within calculated fields. If I have to use it for one component of a calculated field, do I have to use it for every other component within the calculated field? Why do I get the option to choose an aggregation type sometimes and other times I don't?

Best Answers

  • ArborRose
    ArborRose Coach
    edited September 3 Answer ✓

    There's no way to save from the card. As you mention…you can create calculated fields…setup an ETL transformation that can replicate the logic of the card.

    The FIXED BY clause in Domo is part of the window function capabilities. It allows you to calculate metrics within specific partitions or groups in your dataset, effectively overriding the card-level aggregation settings.

    Use FIXED BY when you need to calculate a value that is fixed or constant within a certain group, regardless of the other dimensions or filters applied in the card. For example, calculating a total sum of sales for each region while ignoring any other dimensions.

    Oh, and glad to see you posting. We love to have the new faces and participation.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **

  • ArborRose
    ArborRose Coach
    Answer ✓

    I guess you could say they don't talk well together. I would say FIXED BY isolates the situation for each so they don't "see" each other well.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **

Answers

  • ArborRose
    ArborRose Coach
    edited September 3 Answer ✓

    There's no way to save from the card. As you mention…you can create calculated fields…setup an ETL transformation that can replicate the logic of the card.

    The FIXED BY clause in Domo is part of the window function capabilities. It allows you to calculate metrics within specific partitions or groups in your dataset, effectively overriding the card-level aggregation settings.

    Use FIXED BY when you need to calculate a value that is fixed or constant within a certain group, regardless of the other dimensions or filters applied in the card. For example, calculating a total sum of sales for each region while ignoring any other dimensions.

    Oh, and glad to see you posting. We love to have the new faces and participation.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **

  • lee0789
    lee0789 Member

    @ArborRose thank you for the help! This is super helpful.

    I think that an ETL is the way that we'll need to go. Another skillset that I'm going to learn!

    FIXED BY is something I still struggle with. If I have 2 calculated fields, one of which is FIXED (BY 'job_id') and the other is FIXED (BY 'change_order_id'), then those 2 fields don't talk to each other well, right?

  • ArborRose
    ArborRose Coach
    Answer ✓

    I guess you could say they don't talk well together. I would say FIXED BY isolates the situation for each so they don't "see" each other well.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **

Categories