Best Of
Re: How to make my BeastMode dynamic
You can use the QUARTER function and the YEAR function eliminate all of your case statement. You could do this:
CONCAT('Q',QUARTER(`dt`),' ',YEAR(`dt`))
New Beast Mode Format - Save as calculation on dataset
I think the 'Save as calculation on dataset' should be up next to the 'SAVE CALCULATED FIELD.' I've already forgotten to check the box numerous times because the notifications cover it at the bottom.
a10hall
Re: Magic ETL or Beast Mode?
There are perks for having something as a beast mode and perks for having something in an ETL.
If something needs to be recalculated on the fly utilizing a filter then I'll go with a beast mode.
Most of the time I'll try and put calculations into the Magic ETL so that the processing may take a fraction longer to prepare the data but won't give a negative UI experience if there are too many beast modes saved to a dataset. Whenever a card is rendered all beast modes are evaluated whether or not the beast mode is actually used on the card. This can cause delays when rendering a page giving a poorer user experience.
In your case it doesn't sound like you'd need to have filters applied so I'd recommend putting it into the ETL you're using to prepare the data. You can use a formula tile to do many similar operations as a beast mode (except window / fixed functions).
You can use @Jones01 's formula to conditionally set the value based on your logic.
Re: Data Flow Help
Every analysts favorite game... Spot the disparity!
Do you have any duplicate, or blank loan_ids?
Did you try Full Outer Join?
Have you confirmed that your input datasets are exactly identical as the inputs for your excel file?
Does your excel file possibly have manually entered data?
Lastly, identify exactly which loan_ids are in the output in Domo, compare that to your Excel sheet, then if your Excel sheet has loan_ids that exist but are not in the Domo output... query your Domo source tables for those loan_ids.
Re: How to Remove Duplicate rows in analyzer?
@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.
Re: Heatmap: Only drill in one category
Currently this isn't an option as you're only able to drill with both values being filtered. I'd recommend adding this as an idea under the idea exchange section of the Dojo so the product team can utilize your feedback for their roadmap and to allow others to vote for this idea.
Re: DDX Demo: How To Implement a Custom "Tab" Navigation Element in Your App
@NoahFinberg I LOVE THIS!!!
Re: How to Remove Duplicate rows in analyzer?
@SaloniShah Based on your screenshots, those duplicates don't appear to actually exist in your dataset. Try removing the sorting in your card. Sometimes unnecessary sort fields can cause cards to not display correctly.
Re: How to Remove Duplicate rows in analyzer?
@SaloniShah is the data actually duplicated in your dataset? If so that's probably something to be concerned about if it's not intentional.
Take a look at the connector that's bringing in the data, is it set to APPEND or REPLACE?
Is the data actually duplicated or are just a few rows duplicates? If you run the connector multiple times do you accumulate a copy of the dataset each time? (if so that implies that you're running an APPEND instead of REPLACE in your connector settings.
Sometimes Domo's datasets are 'broken', to deduplicate a row, you can use "remove duplicates" tile in Magic ETL or use a rank_window tile and apply a row_number to each row partitioned on date then apply a filter. (remove duplicates is probably conceptually easier to understand, rank_window is more precise).