Why Is the Pivot Tile not Working as I Expected

I am trying to use the Pivot tile to accomplish the following (in my attached dataset), but am getting no results under the column I am creating (Weekend_Date_Pivot).
Weekend Date should now be columns with Demand_Qty as the metric under each Weekend Date
Best Answers
-
@Roman_K In the Pivot tile, you will need to specify a value of WEEK_END_DATE in step 4 for every column you want displayed in the final dataset.
I don't recommend pivoting by date in Magic ETL for a few reasons:
- It is cumbersome to add every possible date column when creating the dataflow
- It requires constant upkeep as your data updates, you will need to manually add new date columns to the ETL as new data populates
- The output dataset no longer contains a usable date field, so you lose the ability to filter the dataset by date
- Similar to #2, as the ETL continues to add columns, any cards you build with the output dataset will need constant upkeep to display the new columns
Instead, I recommend skipping the Pivot tile in the ETL and displaying the output data in a Pivot Table card. This will preserve the native filter functionality of the WEEK_END_DATE field and require minimal maintenance.
0 -
There isn't, but you could reduce the available data on the pivot table card using filters or pre-aggregate the data in an ETL.
If I solved your problem, please select "yes" above
2
Answers
-
Could you share screenshots of your ETL? The pivot tile details.
If I solved your problem, please select "yes" above
0 -
Hi. Thank you for providing direction, it is much appreciated. Here are the details of my pivot tile, but the column I'm creating (Demand_Qty by Week_End_Date) is still empty for all rows.
0 -
Is it not working properly perhaps because an ItemNumber can have multiple SKUs?
0 -
@Roman_K In the Pivot tile, you will need to specify a value of WEEK_END_DATE in step 4 for every column you want displayed in the final dataset.
I don't recommend pivoting by date in Magic ETL for a few reasons:
- It is cumbersome to add every possible date column when creating the dataflow
- It requires constant upkeep as your data updates, you will need to manually add new date columns to the ETL as new data populates
- The output dataset no longer contains a usable date field, so you lose the ability to filter the dataset by date
- Similar to #2, as the ETL continues to add columns, any cards you build with the output dataset will need constant upkeep to display the new columns
Instead, I recommend skipping the Pivot tile in the ETL and displaying the output data in a Pivot Table card. This will preserve the native filter functionality of the WEEK_END_DATE field and require minimal maintenance.
0 -
Thank you for your suggestion, I tried it, but am getting the message that it's too much data (over 100k rows). Is there a way to accommodate larger data sets in a Pivot Table card?
0 -
There isn't, but you could reduce the available data on the pivot table card using filters or pre-aggregate the data in an ETL.
If I solved your problem, please select "yes" above
2
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 311 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3.8K Transform
- 657 Datasets
- 115 SQL DataFlows
- 2.2K Magic ETL
- 815 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 81 App Studio
- 45 Variables
- 775 Automate
- 190 Apps
- 481 APIs & Domo Developer
- 81 Workflows
- 23 Code Engine
- 40 AI and Machine Learning
- 20 AI Chat
- 1 AI Playground
- 1 AI Projects and Models
- 18 Jupyter Workspaces
- 410 Distribute
- 120 Domo Everywhere
- 280 Scheduled Reports
- 10 Software Integrations
- 144 Manage
- 140 Governance & Security
- 8 Domo Community Gallery
- 48 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive