Best Of
Re: Being able to use 2 datasets (or more) for 1 card
@EmmaH wouldn't you need some relationship between the 2 datasets to combine them? I often use Magic to stack similar but different datasets together. That could be a good option here as well.
Re: Can I display data in Kanban Board format or would I have better luck finding a unicorn?
@Kellerry That makes sense. In that case, I'd suggest adding is as a new chart type request in the Ideas Exchange
Problems launching analyser
Hi,
I've noticed a new version has been pushed to our instance as the share on dataset checkbox on the beast mode dialog box has moved up towards the save button.
Anyway we are having problems launching the analyser for lots of cards now. You just get infinite loading and have to close and retry to get it to show up.
Anyone else experiencing this?
Re: Can I display data in Kanban Board format or would I have better luck finding a unicorn?
Hi @Kellerry it sounds like you're looking for Domo's Projects and Tasks feature: https://domohelp.domo.com/hc/en-us/sections/360007295954-Projects-and-Tasks
Re: Exporting a filtered file
Hi Damen,
I think that using Views Explorer on your dataset would make this a very easy lift. Once you're in there, click on the 3 vertical dots at the top of the purchase date column and select "Remap nulls"...put in a value like "rows to inspect" or whatever. Then you can filter just on those column and export to CSV. (repeat as needed for any other columns of interest)
Domo performance
Has anyone else noticed that lately Domo is incredibly slow? I've been trying to reduce dataset size, but even editing cards, it takes 30 seconds to 1 minute just to open the analyzer. I've also noticed that data sometimes doesn't change when I edit the card, but when I save, close, and reopen, then the data changes. Also when editing dataflows, it takes forever for the magic etl tiles to load and change the tile joins from dashed line to solid line. And sometimes making changes in the tiles doesn't get recognized at first and it looks like there is still an error on the tile when really there isn't. Just some really buggy stuff been going on. Anyone else having these issues? It seems like there was a huge code change after the last release or something.
Re: Dashboard Date Range with Multiple DataSets
Hi ancasselman, have you had much luck on this one yet?
The page-level date filter is pretty handy. It adapts to set the date range on every card based on each own card's date dimension. Say you had 2 cards, one for "product sold" with "PO date" as its date field, then another (or same) dataset for "product delivered" with "ship date". Pick "previous month" on the page date filter and it's going to set filter the sold card on PO date and the delivered card on ship date. Depending on your application this may or may not be the user experience you're shooting for.
For this to work there must have a date column applied to the card...it can't just reside on the dataset powering the card. (see link below) So if I have a filter card looking at some text dimensions but there is no date column, then that card isn't going to be changed by the page date filter. They don't work on sumo cards. Also watch out for cards that may have date filters coded within beast modes or greater/less than limits on the date range in the card analyzer filter...you could run into conflicts there.
The page filter isn't smart enough to know which card/date/dataset was put onto your page first...it's likely that your first card just has a date column configured in the way that allows the page date filter to work. Look for the small filter icon in the bottom corner of each card when you apply the page filter. If you see the filter icon, then the filter was applied but if you don't, then you need to add the date you're wanting to filter on to the card.
Re: Beast Mode for Conditional Formatting of Standard Table
I would really like for this to be a standard feature without requiring Beast Mode. Doing this as Beast Mode severely limits how you can use this for numeric values. For instance, because it becomes a string and can't be displayed as a numeric, it prevents you from using a Total row.
It's a major gap to me that you can't format a cell based on its relationship to a different cell.
Re: How could I generate an end date for each row of data based on the start date of another row?
@wilbaile You can do the ordering and everything within the Rank & Window tile. It has options for ordering the data to take care of the dates being in the correct order as well as partitioning to take care of the client_id
https://domohelp.domo.com/hc/en-us/articles/360042922814-Old-Magic-ETL-Tiles-Rank-and-Window
Re: How could I generate an end date for each row of data based on the start date of another row?
@wilbaile Use the Rank & Window tile in Magic ETL with the Lead function with an offset of 1 and ordering by summary_date, and partition by client_id. This will get the summary_date from the next row, and will look at it by client_id so the last row of each client_id should still be null.


