• 1)

• I don't think that it's this BeastMode that's causing the data to split across columns, since you're summing it. It's probably the TEST column, which I assume is the same one as this discussion:

  Can I sum 2columns one being Aggregation SUM and other (No Aggregation) fixed number?

  IgneP

  Feb 27, 2025

  Good day!

  I am trying to add a column with a count of a TOTAL SUM of different values in Transpose table. (simply: Rename Fee+
  (amFee-Platinum amFee)+
  Platinum amFee+
  VIP No IVA+
  Collector price no IVA) etc

  My columns that needs to be Summed are in format: 123=SUM() Aggregation SUM and one column is a fixed number in format 123=Expenses (No Aggregation). this later column is causing me a lot of trouble haha, as in my Total SUM count at the end it shows up as a huge number (probably a sum of smht) instead of the fixed one.

  This is my 123=Expenses (No Aggregation) CASE

  CASE

  WHEN nmOrganizer= 'Hub Music Factory S.r.l.' AND nmPerformance= 'The Offspring' THEN -2294.62
  WHEN nmOrganizer= 'Hub Music Factory S.r.l.' AND nmPerformance= 'Social Distortion' THEN -964.54
  

  ELSE 0 END

  Here is the

  123=SUM() Aggregation example

  amRenameFee/1.22

  Is this happening because it's not possible to sum Aggregation SUM with (No Aggregation) fixed number? or it's smth else?

  hope it makes sense, if NOT I can give more details.

  Thank you in advance!

To quote myself from that discussion:

"One note of caution is that your current set-up won't work if you have multiple nmPerformers in your data. You either need to insure a single performer is filtered or include the performer as a column in your table."

2)

I've been following your work on this table for a few weeks, and I admire your tenacity, but I want to recommend a different approach. In general, I would recommend using BeastModes to do math on data that you already have in your table. You seem to be using BeastModes to add new data, which is not a sustainable way to store/update/view your data. Create small tables of these expenses and join them to your data before going to the analyzer and BeastModes. Then, if new expenses need to be added, you can add them to your table rather than having to manually add it to the BeastMode every time.

There are the Domo University courses, which will have a lot of examples of how to apply everything in Domo. The only caveat is I feel like most of the Domo courses assume your data is already structured relatively cleanly, maybe coming in from system.

For a theoretical grounding on how to structure your data from the ground up, I recommend this article, which is how to structure your data in a "tidy" format, and is a relatively quick read:

https://vita.had.co.nz/papers/tidy-data.pdf

If you want to get really into the weeds, look for resources on "database normalization", which is the concept of reducing your data into small tables that can be joined together. I don't think your data needs to be truly "normalized" in Domo, but the concepts/thinking behind normalization are useful.