ST_Superman Domo Employee

I would actually like the ability to set the order. Sometimes you would prefer to not have them in either ascending or descending order. In my case, we have categories that we would like to see in a specific order and that does not align alphabetically. Would be nice to place the categories in the order I want to see them…

I did specify that the option was only for filter cards, and not page filters:

@gbrown this was a fun problem to dive into. Unfortunately, I do not believe this can be resolved with a calculated field. I used magic ETL. If you have access to the community Domo instance you can view my solution here. You can bug @jaeW_at_Onyx or @DataMavenLLC for access to the instance. If you get to my page, scroll…

This is an interesting ask. I'm not aware of a way to do this with variables. I would probably recommend adding this data to the dataset via an ETL and then you could use a combination of filter cards (one for region and one for Country) to accomplish this on a dashboard. However, maybe you could reach out to @chucki to…

CASE WHEN MONTH(CURDATE()) IN ('1','2','3') THEN CONCAT(RIGHT(YEAR(CURDATE()),2),'-Q1') WHEN MONTH(CURDATE()) IN ('4','5','6') THEN CONCAT(RIGHT(YEAR(CURDATE()),2),'-Q2') WHEN MONTH(CURDATE()) IN ('7','8','9') THEN CONCAT(RIGHT(YEAR(CURDATE()),2),'-Q3') WHEN MONTH(CURDATE()) IN ('10','11','12') THEN…

@MichelleH is correct. When defining the color rules, only the options that are "visible" to the card will show up. That means that you need to define the color for the default options, then use the variable controls in the analyzer to select a different option, go back to the color rules and create the color for the…

@NIKKI You should put your date column in the x axis then use the “trellis/tiered dates” chart property to include a trellis category. Then drag location over to the “category 2” field. I would recommend making location also be the series when you do this as well.

It's pretty difficult to tell where the error is here. I tend to try to break these complicated calculated fields up firts to make sure that I am getting the correct values for each "step". For example, make sure your numerator value is coming through correctly, then confirm the denominator value. Then put the whole thing…

Hi @lotto67 - Not sure why no one has addressed this question yet. But I have come accross the same issue It turns out, that there is a solution, although not an ideal one in my opinion. You can change the justification of the column in the format options However, center justified (or left justified) number values are not…

Or an option to only duplicate the layout

@AnwarBham - You can use filter cards, instead of page filters. If you leverage filter cards then you can define which cards on the page those filter cards will interact with.

Yes, you can use calculated fields in a filter card, but should you? Whenever possible, I would discourage using calculated fields as a filter for a page. Best practice, in my opinion, is to handle as much as you can in the ETL. If it is a calculation that needs to aggregate data or respond to filters prior to calculating,…

What are you expecting the card or dashboard to do with the macro information? @ttronson

@JedP - this is great. Thanks for sharing. @AnnaYardley - this seems like the kind of post that might make a better blog post then a Dojo topic as it really isn't a question, just a well thought out solution to a common problem.

@NathanDorsch couldn't you just exclude both 0 and 12 from your period_diff calculation?

@DanielShurina690 - I think your only option currently would be to try to create the visual using a DDX brick. However, this would be a good feature request to add.

@JedBenson - I would consider splitting these two metrics up into separate visuals if I were you. Maybe have a bar chart or variance chart showing the % change month over month and then this table below it. Trying to fit a calculation into a pivot table that will only calculate for certain columns is not something that I…

Do you have access to all of the input datasets? If you don't have full access to an input dataset, you won't be able to edit the dataflow.

I agree with @MarkSnodgrass - I would attempt this with variables. Create a variable with your full project list. Then create a calculated field for "Selected Project". case when variable = `ProjectName` then 'Selected' else 'Not Selected' end When you build your cards, you would use two different filters, one filtered for…

Just to clarify, but is StudentIndex always populated and is it unique for each partition?

@SlickVic - this is a great question that I would like to hear the solution to as well. I'm tagging a few members that I hope can help provide a solution. @GrantSmith @Ellibot @jaeW_at_Onyx My hunch is that if these guys don't know, they know someone who does.

If you know the possible values for each multi-select answer, you could create different calculated fields for each. Something like this: `apple` sum(case when `column 1` like '%apple%' then 1 else 0 end) You would then do similar fields for cherry, banana, blue, red, green... Then you can create a table card and drag…

Hi @Zel I used a filter tile to identify all alarm IDs that have both "Lost Connectivity" and "Disregard". I then left join that back to your original dataset after adding a column that says to exclude those IDs. The resulting dataset looks like this: Here is the JSON code that you can copy and paste into an ETL to mimic…

This feels like it would be a feature request. I'm not aware of any way to do this in the product currently. Could you post this again on the Ideas Exchange? Ideas Exchange — Dojo Community (domo.com) I would up-vote it, it's a great idea!

My approach would be to use a group by tile here. I would group your orders by whatever your unique identifier is for a single order (the one with 5 items in this case). I'll call this field OrderID for demonstration purposes. You would use a group by tile and group the data by OrderID . You would then add an aggregate…

For the final calculation, you could try something like: (SUM(CASE WHEN `Field` IN ('9','10') THEN 1 ELSE 0 END) -- Sum of 9 and 10 - SUM(CASE WHEN `Field` IN ('9','10') THEN 0 ELSE 1 END)) -- Sum of all Other Values / COUNT(`Field`) It's hard to be too sure without seeing more of the dataset, Could you post a few lines…

@WorldWarHulk See if either of these works: sum(count(`Location`) fixed (by `Name`,`Title`)) or count(count(`Location`)) over (partition by `Name`,`Title`)

can you try: DATEDIFF(`Transaction Date`,LAG(`Transaction Date`,1) OVER (PARTITION BY `Customer ID` ORDER BY `Transaction Date`)) I'm not sure if LAG() works in beastmode or not

Not sure if it was a typo or not... but you have some commas in strange places. Try this: STR_TO_DATE(CONCAT(`YEAR`,'-12-31'),'%Y-%m-%d')

you could also try a formula tile to combine: CASE WHEN `column A` IS NULL THEN `column B` WHEN `column B` IS NULL THEN `column A` ELSE CONCAT(`column A`, ', ', `column B`) END ... Sorry, just re-read your entire post and I noticed that you are combining 8 fields. CONCAT(CASE WHEN `column A` is NULL then '' else…