Best Of
Re: Map Only Certain Values from One Column to Another Column
I figured out what I was doing wrong - thanks for your help!
micheleb
Re: Map Only Certain Values from One Column to Another Column
You're missing a single quote and a few back ticks (these designate column names).
CASE WHEN `Journey-Pathway Content Progress` = 'Completed' THEN 'Completed' ELSE `Content Progress` END
Doing this as a beast mode will create a second column in your dataset as that's how beast modes function. You can rename your column's Display Name value clicking on the column name and changing Label value. Then you can use this new column / beast mode field in your report instead of the old column so it's only displayed once.
Re: Map Only Certain Values from One Column to Another Column
Hi @micheleb
You can use a case statement to conditionally set column B to completed if column A is completed
CASE WHEN `Progress Column A` = 'Completed' THEN `Progress Column A` ELSE `Progress Column B` END
If you don't want an extra column in your dataset from this beast mode you can use the same formula in a Formula tile in the new Magic ETL and set the column name to be the same as the existing one and it'll overwrite the value for you.
Re: I want to create a card that provides an average monthly overview
You could just set your date range selector on your new card to be Last Month and then in the column aggregation (click the column name after you add it to your card) and select Aggregation > Average.
Re: Private iframe and Clickjacking
I'd recommend reaching out to your CSM to get an official answer to this question and they can run it by their security team if necessary.
Re: How to output list which can't be joined
You wouldn’t necessarily need a full outer join as the left join would work just fine. After your join just add a filter tile to say where shop is null and then feed that into another output dataset
Re: Warning: Not all the data is shown
That seems a little dramatic, Domo it plenty useful for hundreds of other things, just because a limitation exists on the amount of rows shown on a table card doesn't make the whole platform worthless. I don't know whether it's a technical limitation they set because of how Domo handles that data being shown or they limit it due to browser performance degredation or something else but I usually take it as a hint that looking at thousands of rows of data isn't really the best thing for the end user to do. Are you expecting them to actually look through 10,000 rows of data? The whole point of Domo and other BI platforms is to take all of this data and present it in a meaningful, higher level way and then with the power of drilling down dive deeper into specific sections. So you build the cards so that when they get down to the table it is a smaller subset of data that hopefully is less than 1,000 rows. If it's more yes, you should export it out and perhaps use something like Excel to do further manipulation of viewing. What is your use case that you need a user to read all over 1,000 individual rows? Why don't they add a filter to reduce the amount of rows? It may be nice if the limit was raised to something over 1,000 but what's a realistic number you'd want? Why would you ever want a user to browse 100,000 rows in a table in a browser?
Re: How do I aggregate a Beast Mode to a number rather than a case statement?
In your 2nd statement, don't put your quotes around your numbers, that will make them strings. Try this instead:
(CASE WHEN `CustomerName` LIKE'%AGRODEX INTERNATIONAL SAS%' THEN .14 wHEN `CustomerName` LIKE'%ALTURISA GUATEMALA%' THEN .14 WHEN `CustomerName` LIKE'%ANGLISS HONG KONG%' THEN 3 WHEN `CustomerName` LIKE'%BEN FOOD%' THEN 3.20 WHEN `CustomerName` LIKE'%BENISAND MERCHANDISING%' THEN 5 WHEN `CustomerName` LIKE'%BIGOS S DE RL%' THEN .15 ELSE 0 END)
You could put a SUM function around this if that is what you are trying to sum.
Re: Help on recursive dataflow
Hi @user048760
Use a select Columns Tile to select your columns except for your delete after your filter so you don't include delete into your dataset. It's only used within the dataflow.
You can look at step 7 on https://domohelp.domo.com/hc/en-us/articles/360057087393-Creating-a-Recursive-Snapshot-DataFlow-in-the-New-Magic-ETL or look at step 9 for how the final version should look.
Re: SSO Sign-in Problem with Domo Mobile App for Android
Hi @Tow, do you have any error messages? Looking at https://status.domo.com/, there was a minor incident early in the day which looks to have been addressed. It may take longer for the effects of the resolved issue to be felt in your instance so hopefully soon you can get back to normal operations.
amehdad