@SaloniShah Yes, when you save the ETL, you can choose how you want it to update, and one of the options is to update it when ever datasets used are updated.

@Saloni I don't think there's a way to extract everything together as there are differences in API's and things like that. You could use Magic ETL to combine your different sources into one dataset.

@louisshh Try adding sorts. Add your Derived Persona Month as a sort (may or may not need to do an aggregation when you do it, so try it both ways).

@damen Current month: case when YEAR('Transaction Date') = YEAR(CURDATE()) and MONTH('Transaction Date') = MONTH(CURDATE()) then 'amount' end Previous year, current month (assuming this means same month last year): case when YEAR('Transaction Date') = YEAR(CURDATE()) -1 and MONTH('Transaction Date') = MONTH(CURDATE()) then…

@AaronCrouch If your card is going to be broken out by customer, you can try it with the unpivot method you were thinking and then in your card use MAX('Software Seats') or aggregate it with MAX when you add the column.

@damen After adding the column that calculates the days between orders, you can do a Group By tile to group the customers together and average the days between orders.

@damen In the Rank & Window tile, use the LAG function, ordering by transaction date and partitioning by customer. The LAG function looks at the nth previous row. So if you did a lag of 1, it would look at the previous row and the column would now provide you with the previous date, and you can do a formula to calculate…

@damen Since it's a practical test, I won't give the answer, but I will give a hint. Look into the Rand & Window tile. https://domohelp.domo.com/hc/en-us/articles/360042922814-Old-Magic-ETL-Tiles-Rank-and-Window

@louisshh What do your sorts look like on the card? If you're sorting on your y-axis columns without doing an aggregation in the sort, you can get multiple lines.

@domodonuts SUM(case when 'DaysToAssigned' <= 10 then 1 else 0 end)/SUM(1)

@Christianjmzc I think I remember seeing something at the last Domopalooza that custom palettes are in the works.

@damen You'll need to remove 'instrument' from Series, and create the separate beast modes for each instrument you want to measure. Ex: AVG(case when 'instrument'= 'first home exempt' then 'spread' end) and a separate one: AVG(case when 'instrument' = 'home again' then 'spread' end) Then you'll take one of these and put in…

@damen You should be able to do a beast mode like the following (using 'Product' for your 1st Home or Home Again column): AVG(case when 'Product' = '1st Home' then 'spread' end) - AVG(case when 'Product' = 'Home Again' then 'spread' end) If you want to keep your chart as is and have the difference as another bar, you'll…

@akki Are your values actually null or just blank? These are two different things. In your case statement for your filter, try the following and see what happens: case when 'Count' = '' then 'Blank' else 'Not Blank' end

@louiswatson If you do the beast mode for each percentage in a card, this becomes a lot simpler because you can do: SUM(case when 'Type' = 'Approved' then 'Approved or Refused' end)/SUM('Type') And do the same for Refused and Other. If you want to do it in the ETL and do a separate column for each success rate, then you…

@louiswatson You would use the formula I gave you as a beast mode in a card if the data was at an application grain. You can use a Rank & Window tile to get the totals after the Group By tile and join it to your groups and do the calculation from there, or you can use the FIXED function in a formula tile to do the…

@Chris_Wolman If you have access to variables (I think it's still in beta), you can use a variable and beast mode to create a toggle to switch between normal values and thousands. If you don't have variables, you can contact your CSM about getting the feature activated.

@PRC Instead of placing Avg. Duration/Engaged/Transferred as columns or values, put them in the Rows section of the pivot table in Analyzer.

@AshleySizemore If you want the users to always see there own data on the dataset and no other locations, then you can look into PDP's. https://domohelp.domo.com/hc/en-us/sections/360007334593-Personalized-Data-Permissions-PDP-

@louiswatson As you have it set up now, if you haven't already, you'll need to add a column to each branch named something like 'Type' that identifies 'Refused' for the Refused branch and 'Approved' for the Approved branch and then append the two. Then do the following: SUM(case when 'Type' = 'Approved' then 1 else 0…

@Jmoreno If you're open to using OneDrive, you can use the OneDrive connector.

@robdmitchell Yes, use the ROUND() function on your division in the beast mode: ROUND(SUM('U')/(SUM('N'),2)

@robdmitchell Also to build on what @MarkSnodgrass posted, if you have unusual ratios (216:81), then you could do the following: CONCAT(SUM('UsedField')/SUM('NewField'),' : ','1') This would always give you the number of used for one new.

@zgranperc With your Audience field having multiple options in each row, you're going to need to do a beast mode for each option. First one would be: SUM(case when 'Audience' like '%C-Suite%' then 1 else 0 end) Then just repeat, looking for the corresponding option for each one. You'll need to be careful on the Manager one…

@NateBI Sounds like a bug that will need a Domo Support ticket.

@AdamC Welcome to Domo and SQL! So your statement will look like this: case when `Column A` IN('ONEY','CMDU') then 45 else 30 end or case when `Column A` = 'ONEY' or `Column A` = 'CMDU' then 45 else 30 end Your CASE WHEN is basically your IF. I'm guessing one problem you were running into is that if the data in your column…

@louiswatson You can use the Add Constants tile in ETL. You'll add one tile per branch of your ETL and name the column the same for each one (Stage), and then for each constant, put the name of the stage that corresponds to the filters. Additionally, depending on your comfort level with CASE WHEN statements and the…

@chapman Not sure if this will work 100% or not, but it's a crazy idea I just had. In your ETL, after your join could you just do a formula that calculates for each row what the percentage is? Then in your card, just do a sum of the percentages? Ex for Store A: (1/50)+(1/50)+(1/50)+(3/50)= 6/50 = 12% is the same as:…

@RocketMichael Is your dataset organized at day grain like your table? Or are you doing the aggregation in your card? If it's in your card, you're going to need to throw SUM around all your case when statements: (SUM(CASE when `Period Type`='Current' then `Shipped CoGS`end) - SUM(CASE when `Period Type`= 'Last Month' then…

@chapman Domo recently rolled out the FIXED function which should accomplish what you're after. You can write a FIXED function that will ignore filters applied to your card. https://domohelp.domo.com/hc/en-us/articles/4408174643607-Beast-Mode-FIXED-Functions