Best Practice - Columns to Rows?

Data_Devon
Data_Devon Contributor
in Magic ETL

Community,

My data is formatted per my example screenshot below.

Is it best to pivot each location into rows, or is there a benefit to maintaining columns for rows?

I will need a total number, and then drill down numbers (I.e. Total Net Profit = 30 > Drill Down > Omaha Net Profit = 10)

image.png

✅Did this solve your problem? Accept it as a solution!

❤️Did you love this answer? Mark it as "Awesome"!

👍Do you agree with this process? Click "Agree"!

Tagged:

Answers

  • ColemenWilson
    ColemenWilson Coach

    You can use the Dynamic Unpivot tile in Magic ETL:

    Screenshot 2024-12-23 at 3.40.37 PM.png


    Results:

    Screenshot 2024-12-23 at 3.41.00 PM.png

    If I solved your problem, please select "yes" above

  • GrantSmith
    GrantSmith Coach

    @Data_Devon It depends on your use case. Having your columns wide will allow you to consume fewer rows overall, potentially reducing your costs. On the other hand, Domo likes things as rows to deal with filtering. If you want to filter your records based on the City, then you'd need to pivot your locations stomore easily filter the records.

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

Categories