Best Of
Re: Setting up specific Alerts
@damen I'd suggest setting up a card using your webform dataset for the alert. You can use a beast mode filter to only include rows where action is needed from Department B like this:
case
when column A is not null and column b is null and column c is null and column d is null
then 'Include'
else 'Exclude'
end
Then you can set the summary number to be a count of column A and set the alert to send a notification when the summary number is greater than 0.
Re: Using beast mode to compare strings
@Mark Puddephatt - just to second what @Sean_Tully is saying, it's part of my standard practice to wrap text strings in UPPER() before comparing. It just helps to minimize any chance of variability.
String != string != STRING
Re: Using beast mode to compare strings
The upper function just helps standardize the strings so that they'll match even if they have different cases within the data.
For "matches field 3" you would just add another line to identify them:
case when instr(upper(`field2`), upper(`field1`)) > 0 then 'matches field 2'
when instr(upper(`field3`), upper(`field1`)) > 0 then 'matches field 3'
else 'Looks bad'
Re: String Operations
@damen It sounds like the LPAD function in the formula tile is what you're looking for. In your case you would want LEN = 10 and PADSTR = '0'
Re: Using beast mode to compare strings
I'd probably do something like
case when instr(upper(`field2`), upper(`field1`)) > 0 then 'Looks good'
else 'Looks bad'
end
Re: Export on cards with embedded Domo Everywhere App Studio
I hear this the most from client's switching to app studio.
Definitely would be a very useful feature that I know 4 clients are waiting on to switch to App Studio over dashboards.
Loom video of what's requested:
https://www.loom.com/share/cb08e5db4acd4f42b8632e6b04cfc108?sid=7c6b98ca-b479-4618-a833-2bfe1300e778
I also attached an image
Re: Using beast mode to compare strings
@Mark Puddephatt You can use the INSTR function to return the starting position of the email address within field2. If field1 is contained within field2 it will return a number greater than 0.
case when INSTR(field2,field1) > 0 then 'Looks good' else 'Looks bad' end
Re: Multiple Level of Detail Tables From One Dataset
Based on your description, you want three tables with totals for each of Product, City, and Store.
Each table card shown would be alike, with a different dimension in the first column.
There would be no beast mode calculations needed. And if each card uses the same dataset, you can have filters on it (shown) that control all the cards through selection.
But there are other ways to do this as well…pivot tables, etc.
These examples use this sample dataset as a csv…
Product | Store | City | Address | Sales |
|---|---|---|---|---|
Product A | Store 1 | City X | 123 Street X | 100 |
Product B | Store 1 | City X | 123 Street X | 150 |
Product C | Store 1 | City X | 123 Street X | 200 |
Product A | Store 2 | City Y | 456 Street Y | 130 |
Product B | Store 2 | City Y | 456 Street Y | 170 |
Product C | Store 2 | City Y | 456 Street Y | 210 |
Product A | Store 3 | City Z | 789 Street Z | 160 |
Product B | Store 3 | City Z | 789 Street Z | 190 |
Re: Export on cards with embedded Domo Everywhere App Studio
100% agree. I'm completely ready to switch to domo app, but the inability to export standalone cards prevents it. I completely understand the hesitation/complication for the whole app, but on the card itself it seems straightforward enough.
LeeJo
Re: Flexible SUM Aggregates With Duplicate Values in Dataset
@jmmc you can do this with SUM(DISTINCT ())
SUM(DISTINCT Price) FIXED (BY Product ID)
Yields the following results. You can see that the column fixed1 only includes the total once per id.
