MarkSnodgrass Coach

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 ()

It sounds like it could be a bug, in which case I would recommend opening a case with Domo Support. I would also try creating a new ETL from scratch and see if the issue persists.

@Jbrorby if you can avoid the recursive dataflow and make use of the append, that should prove to be a better long term solution for you as far as performance and maintenance. I would definitely recommend working through that option first and seeing if that works for you before going the recursive route.

Hat tip to @GrantSmith who wrote the articles, but I didn't initially call out because he is supposed to be on vacation and not on the Dojo. :)

A recursive dataflow is the most common solution to this. You can read about it in this KB article: https://domohelp.domo.com/hc/en-us/articles/360043428133-Creating-a-Recursive-Snapshot-SQL-DataFlow There are also KB articles for doing it in Magic ETL. I would also recommend looking at this YouTube video by @jaeW_at_Onyx…

I recommend formatting it to currency with the concat function in a beast mode. If you try and do it in an ETL, then they would become strings and the card wouldn't be able to sum them when a user is interacting with the card. Here is a beast mode that will format it for you and abbreviate the millions and thousands:…

@106004258 CSM = Customer Success Manager AE = Account Executive These would be employees at Domo assigned to your company's account.

That actually isn't specific to the shape card. I have noticed that applying a background color in a dashboard alters the size of other card types as well. I think it is worth submitting it as a bug to support@domo.com. A workaround might be to include a hexadecimal value of a value really close to white, so then those get…

The column widths will dynamically expand in order to fit your column title until it runs out of room due to the number of other columns and data you have in your card. A couple things you can do: You can use the column widths setting as you pointed out. This setting is expecting a comma separated list of values that total…

When evaluating a date, your date needs to be in single quotes. I would also suggest to have something in your outer case clause as @GrantSmith suggests. I'm guessing you would want to exclude those, so I have re-written it with that in mind. (case when `Date` > '2021-07-01' then (case when `company` like '%company1%' and…

The Dojo was very helpful to me when I first started. Now I use it to help out others and learn new and better ways to accomplish things.

@Anna Yardley may be able to group the threads together and get the various ideas consolidated. I agree it would be a nice feature enhancement

You could create a custom beast mode sort order to get the order you want. This, for example, would move Sunday to the end of the week: CASE WHEN DAYOFWEEK('dt') = 1 THEN 8 ELSE DAYOFWEEK('dt') END I would also suggest looking at this post for several other date functions that might be useful for you.…

You might want to look at using the Trellis properties for your chart. That provides a form of multiple x-axis functionality. https://domohelp.domo.com/hc/en-us/articles/360043429793-Properties-Available-for-Most-Charts#8.

Unfortunately, that card type doesn't allow for that type of drilling. Could be worth submitting it as an enhancement in the Ideas Exchange section of the Dojo, though.

I agree. It seems pretty redundant. The KB article doesn't give a good use case.

Reading the KB article: https://domohelp.domo.com/hc/en-us/articles/4404148803479-DataSet-Copy-Unload-Connector It sure seems like it is does the same as the dataset copy connector except that you are using a developer account and generating a client id and secret instead of an access token like you do with the copy…

As far as I know, the waterfall chart is not built to show three different variances. You could make a quick filter that would allow users to toggle to each variance. Or, build three different cards. Here's a link to the KB article for the waterfall card if you haven't looked through it already.…

Based on your example, if you are adding them all together, you would have a single beast mode that looked like this: SUM(1+1) + SUM(2+2) + SUM(3+3)