Best Of

What aggregation is the field using? Click on the pencil icon next to the field in the card and choose Sum for aggregation.

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.

You can set a different landing page for your users if you're trying to have them log in to not a blank page? https://domohelp.domo.com/hc/en-us/articles/360043439093-Setting-the-Landing-Page

Looks like I need to wake up earlier get my answers in before @amehdad :)

I agree with @amehdad but wanted to add some clarification - The MagicETL or MySQL recursive dataflows will allow you to filter possible duplicate records however the larger your dataset becomes the slower / less performant it becomes because there's more data that needs to be imported and read in.

Using Dataset Copy (with append) will be more performant as it's only appending the records to your dataset with less data to import and process however its processing will be detached from the underlying dataset you're appending. Meaning with the recursive dataset you can trigger it to run based on when the underlying dataset is updated however with Dataset Copy you have to run it at a certain time and have the possibility to have the Dataset Copy run before the underlying data has been updated.

In your use case you'll need to utilize a recursive DataFlow and not the Dataset Copy as you're needing to process the data to update the status and add a datetime when that status changed (removed from the original dataset)