Best Practice - Columns to Rows?

Data_Devon

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)

ColemenWilson

You can use the Dynamic Unpivot tile in Magic ETL:

Results:

GrantSmith

@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.

ColemenWilson

You can use the Dynamic Unpivot tile in Magic ETL:

Results:

GrantSmith

@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.

Data_Devon

Thank you both for the theory and the practicality in this.