MarkSnodgrass Coach

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.

I have not seen anyone get this error before and it's unclear as to where exactly you are seeing this message, but the first thing I would do is check the accounts section in Workbench. Make sure that the account is authorized and doesn't need to be re-authorized. Also, if you do have to re-authorize, make sure you hit the…

@user026529 if you can accept answer and/or like any of the above responses that will help others in the community as they search for similar questions. Hoped all of this helped!

That is correct about the "<" and ">" in the IN statement. The parentheses are optional around the CASE statement. Domo automatically adds them when you start typing in the formula editor and use the auto-complete option.

If you wanted to use an IN operator, your WHEN line would need to look like this: WHEN `wps score` IN (6,7) THEN 'Passive' IN clauses hold a list of values. You can't use greater than or less than operators within the list. You can technically use whatever is most readable to you and others that would need to understand…

Case statements exit after finding a match so you don't need to do a between or in statement. If, for example, your score is 7, it will evaluate the first line and since it is not less than 6, it will go to next when statement and see if it evaluates as true. It would then exit out after evaluating a true being less than 8…

Actually, after trying a similar statements, you can't do a < or IN statement like that. You need to write it like this: (CASE WHEN `wps score` < 6 THEN 'Detractor' WHEN `wps score` < 8 THEN 'Passive' ELSE 'Promoter' END)

I think all you need to do is have a space between CASE and your fieldname 'WPS Score'. It looks like they are together so Domo can't read it correctly.

Teams stores files in SharePoint, so you will want to look in the app store for the SharePoint connectors and choose the one that works best with your environment.

It appears that it is still not an option. Domo uses the dashed lines for the min max and average values, so maybe that is why they have kept it from being available as a choice in order to avoid confusion.

If the numbers you want to combine are each in different datasets, then you will need to use Magic ETL to bring them together. You would add all 4 of your datasets as input datasets in Magic ETL and then use the Append Rows tile to bring them all together and choose the option to include all columns. Add your output…

You might want to watch this video that @jaeW_at_Onyx put together on using the Date Dimensions dataset

Yes. You would want the calendar.csv file. This will have a row for every date that you can join your ads data to.

Domo has a Dimensions dataset in the app store that you can join your Google Ads dataset to do this. You would use the Date Dimensions dataset and then join it to your Ads dataset so that all dates are listed and every campaign has a value of zero instead of null for each date. Keep in mind, your dataset will end up being…

You are correct that you would need to create a separate calc in your dataflow if the user wants to filter to the current month but still the running total. You could do this pretty easily with the rank and window tile in Magic ETL. You might also look at some different card types. Maybe using the multi-value card or a…

Your beast mode is giving an error because you have an equals sign at the beginning of it. Remove that and it should return as valid.

Unfortunately, Domo webforms aren't designed for that and have no data validation logic or capabilities such as dropdown lists. An alternative would be to build a custom app that is a form and you could build in dropdown list capabilities. Adding enhancements to the webform is a good idea, though, and could be worth…