Best Of
Re: Joining and getting all dates between start and end date
Using magic ETL, take the date dimension dataset (Domo Dimensions connector) and feed it into a Add Constant tile to create a new field called "join column" with a value of 1. Do the same for your input dataset. Feed both of those into the join based on the join column. Then you feed that into a filter field with your BETWEEN clause. The joining on the join column will do a cartesian join and add all dates for every record then you're filtering out the rows where the dates from the dimension dataset aren't within your range.
Re: How do we hide/merge duplicate cells in a column in HTML table
Currently this isn't an option with the HTML table, I'd recommend adding this as an idea to the idea exchange.
Re: Shows in Analyzer but not in dashboard
I see in the bottom corner of the chart when you are in the dashboard that the filter icon is showing. This means there is a dashboard filter applied to all cards on the dashboard. Likely, that filter is causing the previous to not be able to show.
Re: Trying to use Unpivot
I follow. Currently, your columns are something like:
- Order Number
- Schedule Date 1
- Completed Date 1
- Status 1
- Schedule Date 2
- Completed Date 2
- Status 2
- ….
- Schedule Date 10
- Completed Date 10
- Status 10
You want to unpivot so your columns are:
- Order Number
- Stage Number
- Schedule Date
- Completed Date
- Status
If un-pivot is giving you trouble, it wouldn't be that hard to do this manually (and maybe more computationally efficient? Not sure):
- Select columns: Order Number, Schedule Date 1, Completed Date 1, Status 1; rename without 1 (if that's part of the column name)
- Add a constant with the stage number
- Do these two steps for each of the 10 groups of columns. You could select the two blocks and copy-paste, changing just which columns and stage.
- Append the 10 stages
Alternatively, you could do the dynamic unpivot once, selecting the Order ID as not pivoted, and something like "Metric" to store the column names and "Value" to store the values, so your three columns are:
- Order ID
- Metric (Schedule Date 1/Completed Date 1/Status 1…Schedule Date 10/Complete Date 10/Status 10)
- Value
Then you could use a formula tile or split tile, to split the Metric name and stage, so your four columns are:
- Order ID
- Stage (1, 2, …10)
- Metric (Schedule Date, Completed Date, Status)
- Value
Then you could split that into three datasets using filter blocks: filter for metric=Schedule Date, metric=Completed Date, metric=Status)
Then you could join those three filter tiles together using Order ID and Stage as keys, renaming the "Value" column to the metric (Schedule Date, Completed Date, Status)
I had a similar ETL for a dataset with dozens of columns in pairs like "Question 1 TEXT", "Question 2 VALUE", "Question 3 TEXT", "Question 3 VALUE". I used a dynamic unpivot, then filtered for just the rows with TEXT and the rows with VALUE, then rejoined them, so I basically three columns; ID, TEXT, VALUE. It didn't take very long to run on a pretty big dataset.
EDIT: Marcel's answer of using the Pivot after the dynamic un-pivot and split makes more sense than filter+join. I'd be curious to see if Marcel's method or the manual method I started this answer with runs faster. The advantage of the dynamic-unpivot vs. manual appends is that it would be dynamic to different numbers of stages. You could have 1 stage or 50, and the same method works.
No Code JSON - Upload File Containing JSON Data
I am getting the below error message when trying to manually import a JSON file using the no-code JSON connector.
"Domo is ready, but there was an error parsing an expected JSON response from the API. Please check that the API is returning the expected data"
I am using a JSON account with no parameters other than the name of the account.
I am performing a number of steps to flatten out the data. The JSON is parsing well during this process (by the way this feature would be amazing if I could get it to work and would save hours working in Python).
Does anyone have an idea on how to fix it?
Many thanks
Re: ETL calculation to work out hours taken from a start and finish timestamp
@robdmitchell There are a couple different ways you could do this in MagicETL:
- Date Operations Tile: Use the Difference between dates operation, with hours as the unit of measurement
- Formula Tile: Add a field with the following formula:
DATEDIFF(`DateTimeOff`,`DateTimeOn`)*24 + TIME_TO_SEC(TIMEDIFF(`DateTimeOff`,`DateTimeOn`))/(60*60)
Re: Create Nested Beast Mode that nest more than two levels
sobo we hear you! Thanks for this feedback. Adding support for nesting calculations multiple levels deep is something we are looking into for the future.
Re: How do I filter by most recent date?
@MarkSnodgrass ah those trainings are coming back now. much appreciated, sir!
damen





