MarkSnodgrass Coach

You can do this very easily with the color rules. In the Chart Properties, click on Colors and then create a rule based on y-axis field that if the value is less than 25 then color it read. You can read more about color rules here:…

You would just create multiple WHEN statements. You can have as many WHEN statements as you want in a CASE statement. Yours would look like this: (case when (`Distributors`='DistributorA' and `Country`='CountryA') then 'Distributors' when (`Country`='CountryB') then 'Distributors' else 0 end)

That is a definite shortcoming. That would be worth submitting as an enhancement request to allow for date formatting. In the meantime, I think you can still get your card to work by using the tooltip fields. Create a couple beast modes that have the dates that you want in the format you want and put them in tooltip fields…

They are likely following the format of the time period field. Click on the pencil icon in your time period field and choose format and try date shorthand and see if that changes how it is displayed.

You can create a beast mode that assigns a value to each Job Type and then put that beast mode field into the values field. Then, use the ranges chart properties to assign colors to the values that you created. Example beast mode: CASE WHEN JobType = 'a' THEN 1 WHEN JobType = 'b' THEN 2 .... END Example Range Properties:…

In Magic ETL, you could do a group by tile that calculates your first average, you could then use a rank and window tile and rank by your new average field descending. The row with a rank of 1 would be your highest average.

If you are adding together multiple values and one of them is blank or null, it will not be able to add them all together and just produce a blank value. You would need to do this: IFNULL(likes,0) + IFNULL(shares,0) + IFNULL(comments,0) in order to add them together. If the fields aren't actually null, but blanks, you…

I just created a sample dataflow to confirm what I have been saying. See image below. I have a dataset that has 15 rows. I added a filter tile that filters out 3 rows. Notice that it still says 15 rows processed next to filter rows. This is how many rows came into that tile. The result of the filtering resulted in 12 rows,…

You could test with some sample data by making up a basic Excel file with 10 rows or something and run it through a few of the same steps in your current dataflow and see how the numbers look. When I looked at one my dataflow details, that is what I deduced: that it is telling you how many rows it processed (looked at),…

I played around with a pivot table card on one of my dashboard pages, it looks as though the chart display setting has to be selected in order for the summary number to be displayed. I'm not sure why Domo would decide to require that. It could be viewed as a bug, in which case I would suggest creating a case with support.…

@user077529 you would do isRegistered IS NULL and isregistered IS NOT NULL when evaluating nulls.

@user027926 I think those numbers are telling you how many rows came into that tile, not how many came out of it. So, there were 484,445 coming into the Remove Duplicates tile and after it completed, there were 468,410 rows. It would be a nice enhancement if they showed both the incoming and outgoing numbers for each tile,…

You can create custom summary numbers with a beast mode field. Create a beast mode like this: SUM(CASE WHEN YEAR(datefield) = YEAR(CURRENT_DATE()) AND MONTH(datefield) = MONTH(CURRENT_DATE()) THEN targetfield END) You may need to tweak slightly to fit your data, but this field should be available in your summary number…

Unfortunately, not that I have seen. Would be a nice enhancement. I have seen workaround for this where you create a dashboard page and create some single value cards to show the counts you want and put them around your main card. The interactive filters will allow you to keep all cards in sync if someone filters on…

I would suggest creating a Magic ETL and clean your data so that you have a numeric column and then you can use the built in chart properties to total different columns. You could also create a beast mode field to do the same thing. Replace your N/As with NULL should allow for proper counting.

You could mask individual fields by doing something like this: CASE WHEN SUM(COUNT(DISTINCT `ratingid`)) OVER () >= 7 THEN `comment` ELSE 'xxxx' END It would be nice if you could do a case statement like this and put it in the filters, but that feature isn't out yet. I believe I saw in DP21 that it is coming soon.

I would check your company's e-mail quarantine and seeing if it is getting stopped there. Sounds like it might be getting falsely identified as spam and is getting quarantined.

The error is because you are missing the ON clause in your join statement. A typical JOIN query would look like this: SELECT * FROM a JOIN b ON a.id = b.id However, based on what you are describing, you don't need a JOIN clause at all. You can accomplish it by doing this: SELECT * FROM b WHERE b.date > (SELECT MAX(Date)…

If it is a char column, you can't do a numeric type between statement. You would need to convert your column to numeric and then either write it as (c.result_code >= 9.5 and c.result_code <= 11.99) or (c.result_code BETWEEN 9.5' and 11.99) If result_code contains non-numeric characters, you would need to create another…

I would create a beast mode like this DATEDIFF(CURDATE() , yourdatefield) Then put this field in your filter and set it to values greater than or equal to 14. This will restrict to rows that are 14 days or older and your chart will do the rest.

You can do this by creating a dataflow and adding the Domo Date Dimension dataset that provides all dates for whatever range you need. Look for it in the cloud apps. You would then add a constant of 1 to each dataset and join on that column so that you would get all dates. You can also use the filter tile to restrict what…

@user026529 The error message could use some improvement, but it doesn't like the when <6 statement and it doesn't like your arguments in the In statement. You need to write it how I suggested earlier, which was: (CASE WHEN `wps score` < 6 THEN 'Detractor' WHEN `wps score` < 8 THEN 'Passive' ELSE 'Promoter' END)

Are you getting a syntax error? Or is the result just not want you are expecting? There are a couple other date functions you might want to consider using to make the function a little easier to read. You might consider using DATE_SUB to get the previous month and previous week as it has an interval parameter that lets you…

You could do this: sum(case when status = 'Converted' then 1 when status = 'Future Date Rentals' then 1 else 0 end)/count(`id`) This would add based on either one.

I believe my logic would work for what you are wanting. If it is a future dated rental, count it. If unit_rented_c is true, count it. Otherwise, don't count it. You could also write it this way if you want. sum(case when `unit_rented_c` = 'true' then 1 when status = 'Future Date Rentals' then 1 else 0 end)/count(`id`) I…

Based on the logic I added, this is how each would be evaluated: Does this look correct to you? Or am I not understanding something?

Are you looking for this to be your calculation? sum(case when `unit_rented_c` = 'true' or status = 'Future Date Rentals' then 1 end)/count(`id`)

You can ask your CSM to enable Magic ETL 2.0. It has a lot of nice enhancements is definitely worth moving to. Looking at your issue, it's hard to say if it will fix this issue. This seems like a bug with the connector and you might need to reach out to support@domo.com to have them look at it. You could also try creating…

Have you tried creating a basic ETL and using the Set Column Type tile to change the column back to text? Or if you are using Magic ETL 2.0 you can assign it right on the input dataset and then just link it to an output dataset.

@jgospel I use publish as well and have had various issues with things not showing up properly in the subscriber instance. I had to open up a support ticket to get them to fix it. Support didn't provide details, but there was nothing wrong with my beast mode. Seems to be just issues with the publish process.