Comments
-
@Jbrorby Since your ETL formula is incorrect, are both 'lag min start' and 'max end date' present and populated in your data for the example you showed? Also, could you post both formulas you wrote? I know sometimes I think I've written something exactly the same but I realize I had a typo or something different that I…
-
@damen This means that your formula is doing an aggregation (your weighted average) but your data is not aggregated. You can think of it as your formula is trying to create one number, but since your data is not one row, it doesn't know what row to put this single value on. If you tried this in SQL Server or MySQL, you…
-
@damen Don't do the BY 'Loan ID' because then you're basically partitioning the data by Loan ID, so you're counting how many occurrences of that 'Loan ID' there are. Also wrap your denominator in an additional COUNT, so you have the following: COUNT('Delinquent Payment 2')/COUNT(COUNT('loan id')FIXED(FILTER DENY…
-
@SLam The beast mode as you have it won't work because both the numerator and denominator will only be counting loans in each group. You will need to use the FIXED function in your denominator to get the total of everything: https://domohelp.domo.com/hc/en-us/articles/4408174643607-Beast-Mode-FIXED-Functions
-
@damen Use FILTER DENY inside the FIXED function in your numerator: COUNT('Delinquent Payment 2`)FIXED(BY 'Loan ID' FILTER DENY 'Delinquent Payment 2') When you exclude 'Current', the FILTER DENY will ignore that filter and keep counting the overall number of loans.
-
@damen You will want to do just a generic calculation and then use 'Delinquent Payment 2' as a column or series. Your beast mode would look like this: SUM(1)/SUM(1)FIXED() When you use this and a 'Delinquent Payment 2' column or series, Domo will do the grouping for you. The denominator of the beast mode will count the…
-
@newbee You can use a beast mode to create the column. Something like: case when CURDATE() <= 'DateField' then 'Actuals' else 'Forecast' end This is just an example and depending on your data, you may have some other way of determining what is Actuals and what is Forecast. Then you just use that beast mode to set your…
-
@AdamC You can use a Rank & Window tile: https://domohelp.domo.com/hc/en-us/articles/360042922814-Old-Magic-ETL-Tiles-Rank-and-Window Using Row Number as the function, then ordering by EVENTTIME descending, and partitioning by EQUIPMENT_NUMBER. This new column that's created will assign the most recent date for each…
-
@bdx If you want to use the Group By and not need to type out each item and modify your beast mode each time a question is added, you can use the Unpivot tile in ETL. This can change your data to be: question 1 OPP1 question 1 EXP1 question 1 ACH1 question 2 OPP2 etc. Or however you want the unpivot to happen. This can…
-
@foppc In Magic ETL, you can use the Rank & Window tile with a LAG/LEAD function to create columns with values from different rows that you can use for your comparisons: https://domohelp.domo.com/hc/en-us/articles/360042922814-Old-Magic-ETL-Tiles-Rank-and-Window
-
@damen What is your y-axis field? Is it a beast mode or a column from your dataset? If it's a beast mode, could you post what it is?
-
@lb1234 Try throwing a SUM around your denominator and see if that fixes it.
-
@damen Just from the syntax error standpoint, it looks like you might be missing a final end statement:
-
@TheScotsman If the file an folder haven't been renamed, from the error it sounds like the location of the folder may have changed. Is the folder still in the same location, or has the file path been changed? If it's still the same, then I'd put in a support ticket with Domo, though you may need assistance from Dropbox as…
-
@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
-
@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.
-
@damen Under General chart properties, set Divide Value By to 'None'.
-
@Joe_M Would using a beast mode like the following work for the date on those cards? case when DAY(CURDATE()) < 7 then DATE_ADD('Date', interval 1 month) else 'Date' end This says whenever the day of the current month is before the 7th, add one month to the dates in the 'Date' column (show the previous month). On the 7th…
-
@Pau You can use Variables in Domo. Right now it's in beta but is going live with the feature update on Oct. 19th (I think that's the date I remember). If you want access before then, you can contact your CSM about having beta access to it.
-
@mroker Agree with@GrantSmith above. You can just aggregate as normal in the card using SUM() and it will take into account negatives. Then in the drill path, your raw data will show the amount as you posted above.
-
@SaloniShah The less than ideal solution is to create an ETL that and use the Remove Duplicates tile, but that doesn't solve the underlying issue. One thing you might try is delete and recreate the connector. If that doesn't solve the issue, it's most likely a bug with the connector and you should put in a support ticket.
-
@SaloniShah Looking back at what you posted about not seeing duplicates in your dataset in the data tab, I actually do see duplicate rows, they just aren't right next to each other:
-
@damen I would recommend using a beast mode and sharing it on the dataset. That way if you need to tweak it, you can do it in the analyzer and get the update right away without having to edit the ETL and run it.
-
@damen In your formula, instead of doing COUNT('withdrawn'), do this: SUM(case when 'fallout_reason' = 'withdrawn' then 1 else 0 end) As you have it now, the numerator is essentially creating a "column" with the string 'withdrawn' in every row, so the numerator is doing the same thing as your denominator. You need to…
-
@andersson_morales19 I would modify your statement further. Right now when you look at how many tools are used and you look at 'Basico', if they just used one 'cantidad _noticias' an that was it, they would qualify for Basico even though they only used one tool. For level one, does it have to be two different tools, or…
-
@andersson_morales19 You're case when statement isn't working because of the waterfall. CASE WHEN statement go through each part of the statement and once a condition is met, it doesn't evaluate anything else. So in the case of your beast mode, if a row meets the 'Basico' condition, it assigns it as 'Basico' and won't…
-
@damen Just noticed that the beast mode you posted of what you're using, you put: then 'amount' end You're using 'amount' as a string so you're saying when the row meets that condition put in the word 'amount' and since the column is intergers, it comes in as nothing. You need to use whatever column contains your values.
-
@damen The beast mode I gave you that you were using and wasn't working for YTD is actually the beast mode for Current Year, Current Month. My original post also has the Previous Year, Current Month beast mode.
-
@louisshh It sounds like your data is by day and you've just using your Derived Persona Date to use for graphing. Then you need to make sure all your columns that you're graphing are aggregated, otherwise it will graph each row individually. So you would need to aggregate !3monthlag and !Count of matched persona
-
@damen The beast mode you have is for current month, not current year. It will only have values for the current month (2022-Sep).