Best Of
Re: How to create a recursive dataflow with multiple unique dimensions?
Are you attempting to utilize a single field in your recursive dataflow join for your key field? You should be able to select multiple key columns which uniquely identify each record. Just make sure you're joining on all of your key columns in the join
Re: Vertical Faceted chart not sorting correctly
It looks like you are limiting the data to 150 rows. When you move the Year | Month to your first sort, then it moves the most recent month to the top of the data, and you only get the most recent month. You should remove that limit to see all months.
If you're limiting to 150 rows in order to get a more limited number of products, you should create a formula that ranks products based on the relevant metric, and then filter on that formula. Or, you could add a filter card that allows users to filter by the SUM of Net… value you have in your X axis now, so they can tune the appropriate range to look at products of interest.
Re: Validate Syntax
For the mod operation, you can't use %, you'll need the MOD() function.
For example, for your hours:
FLOOR( (MOD(record_age , 86400000) / 3600000)
Re: Transpose columns into multiple rows
You can utilize Magic ETL and the Dynamic Unpivot tile to take your columns and convert it to rows.
Here's more information:
Re: How to Sort by ASCII (caps first)
This can be done using the ASCII() function in a SQL dataflow. Doesn't work in a beastmode or Magic ETL.
Re: Spreading out labels so it's easier to read
There isn't a way to spread out the data labels currently as they're tied to the end of the lollipop. You can submit an idea to the Idea Exchange to improve label positioning and spacing.
You can make the chart longer or display less data so it has more space to display the labels and lollipops.
Re: Unexpected error with pydomo "ds_update"
This appears to be a system-wide issue. I'd recommend logging a ticket with Domo Support. I'm having the same issue as well.
Re: beast mode calculation
You could create a beastmode that would count the number of tickets per customer site:
SUM(COUNT(DISTINCT `TicketNbr`) FIXED (BY `Site_Name`))
Then, you should be able to use this as a filter for your card.
Re: A filter based on weekday or wknd
CASE WHEN DAYOFWEEK(CURRENT_DATE()) IN (1,7) THEN 'Weekend' ELSE 'Weekday' END
Re: Page filter add contains + allows "ORs"
This post deserves a monthly bump until taken into development queue. Anytime my user base wants to do an OR filter I have to create it via beast mode so they can leverage as a page filter. Not an ideal solution and fully hardcoded so no flexibility. Page filtering where we can use the OR qualifier should be a priority for the product team. I love what Domo is doing with new advanced tools and new products but we've got to have this base functionality.
