MarkSnodgrass Coach

Ok. It seems like your case statement is working properly to get the Marketing, SDR, and Sales names for the series. Have your tried just putting Lead Source in your Y-Axis and choosing Count for the Aggregation? See if that works before we go into using a beast mode for the count.

@henryfact can you mock up a display of what you want the end result to look like? Can you also take a screenshot of how your Analyzer is currently configured, making sure to show the filter and sorting properties? With this additional information we will better be able to provide you with a proper solution.

There is not currently, but that is a good suggestion for the Ideas Exchange as it would make a lot of sense to do that.

@jaeW_at_Onyx I was assuming 'Marketing' was a numeric amount, but maybe I misunderstood what that field represented.

Have you tried wrapping your case statement with a SUM function like this: SUM(CASE WHEN `Lead Source` IN ('Event','Display','Direct') THEN 'Marketing' WHEN `Lead Source` IN ('LeadIQ','Prospecting') THEN 'SDR' ELSE 'Sales' END) Also, another reason why you might not be able to sum is if you have things in your sorting…

Gotta earn those Dojo points! :)

@Ritwik and @amehdad21 I added this to the Ideas Exchange if you want to help vote it up. https://dojo.domo.com/discussion/53480/hide-sorting-indicator-arrows-when-not-hovering-over-them#latest

In your example with counting Employee IDs and Job Codes, in order to not show the Employee IDs, you can use Magic ETL to aggregate the information for you by using Group By and Count and then build the card off the resulting output dataset. That way, the dataset that is used for the card does not have sensitive…

Have you tried using the Sorting Properties to define your sorting rather than clicking on the elements in the chart to pre-sort it? I think that is the only way I have been able to keep them from showing up initially.

Done!

I have seen people have issues with renaming fields in their view, especially with group by statements. You certainly did the right thing with opening a support ticket as I imagine there are still some bugs since it is a fairly new feature. I would recommend sending the ticket number to your CSM and have them advocate for…

Right now, you have it coded as a string. If your datasets has columns called Q1, Q2, etc. then you could have those in your case statement, but you need to fix that in your statement so it is actually referencing those fields. If Q1, Q2 are calculations, you would need the actual calculation in your case statement.

It looks as though you are trying to sum the lbs field with the string values: Q01, Q02, etc. You can't sum string values. That is probably where you error is occurring.

Just in case you aren't already aware, source datasets can be set to replace or append. They don't all have to be replace. Additionally, you can use recursive dataflows to create an appended dataset. See these two KB articles:…

It is really just for display purposes in Domo as you have noticed. It would have nothing to do with Writebacks because you don't use Workbench for writebacks. It is just there to make it easier for you to identify your workbench jobs.

@cthtcc I would recommend reviewing some of the information here: https://developer.domo.com/docs/embedding-into-sites/embedding-into-sites-and-web-portals I think the key is to look for a platform that works well with the SSO framework that Domo Everywhere uses. Domo is also developing a brand kit where you can take a…

@StefanoG Have you figured this out? One thing I noticed is that your column widths don't add up to 100%. They add up to 126%. That could be affecting things. If you comment out all properties will it display something? I would then try adding in properties one at a time, starting with the total row property and see where…

Good suggestion by @GrantSmith . I just tested this in a beast mode and it worked properly. Using this syntax: CONVERT_TZ(`_BATCH_LAST_RUN_`,'UTC','CST') Properly converts. See screenshot below. Again, the Batch_Last_Run field is coming in as UTC, so I put UTC and parameter 2. I want to convert to CST, so I put CST in…

I would check to see if one of the data type of one of your fields is different. Such as changing from integer to text because some of your data is different. This would cause the error. Also, if you are using Domo Workbench to import the data, you need to refresh the schema in there. Click on your job, then click on the…

I would refer to this page again to know the offset: https://www.timeanddate.com/time/zones/ CST is -6 from UTC, so you would enter -06:00 for parameter 3. If you datefield is coming in as UTC, parameter 2 will be +00:00

If your start time is coming in as UTC then you want to have +00:00 in parameter 2. In parameter 3, is how many hours you want to adjust it. To say it another way, parameter 2 is to specify how many hours offset from UTC is the datetime in parameter 1. Parameter 3 is how many hours from UTC it should be offset.

Here is a link with additional documentation:

No, it wants it in this format: CONVERT_TZ(dt,from_tz,to_tz) It would look like: CONVERT('date',"+00:00","+06:00") Also, according to this CST is 6 hours off of UTC.

I think it is important to note than when datetime data is imported into Domo, it assumes it is UTC. If you are doing this work before importing into Domo, you will end up with undesirable results when looking at it in Domo. I would suggest doing the timezone work in Domo via a beast mode or a MySQL dataflow or the Magic…

You could write a beast mode like this to exclude the current month (CASE WHEN MONTH(`date`) = MONTH(CURDATE()) and YEAR(`date`) = YEAR(CURDATE()) then 'Exclude' Else 'Include' END) Then just add this to your filters and choose Include

You could create a drill path so that when a user clicks on a state, it would take them to a pie chart to show them that public vs private. Your other option would be to have a quick filter that a user can select public or private or both and the map would change based on the filter.

Try doing this for your beast mode to get the counts you want: SUM(CASE WHEN `activityName` = 'Open Email' THEN 1 ELSE 0 END) / SUM(CASE WHEN `activityName` = 'Send Email' THEN 1 ELSE 0 END) This should eliminate any issues with nulls or blanks

I think you can use the Activity Log to determine which pages are a story page and which ones aren't. I just converted a standard page to a dashboard page and two events were created in the activity log: Organized Dashboard and Edited Dashboard. You could create an ETL that would look for this event and then create a…

@User_32265 You can e-mail Domo Support at support@domo.com . This will automatically create a support ticket with them.

Percent of total typically requires using window functions in beast modes, which is not enabled by default. If it isn't enabled, ask your CSM to enable window functions in beast modes. You can then use the following beast mode to calculate the percent of total: sum(amount) / sum(sum(amount)) over ()