MarkSnodgrass Coach

I do have a video about incomplete months as well if you want to watch it, but the short answer is to change your date range filter to 13 months and then create a beast mode that checks to see if the data is in the current month and exclude it, otherwise include it. Drag that into your filters and filter to include. Here…

@NathanDorsch this video may help you where I show how to move dates from different years into the current year so that you can do a year over year comparison.

In the date range filter, change your Graph By to Day instead of Year.

yes. you can do this a couple different ways. Option 1: You can drag the quantity into your filters and filter to less than a number you think would exclude outliers. Option 2: You could add a case statement to your beast mode that only will do the math if the quantity is less than a certain amount. i.e. CASE WHEN qty <…

You can create a beast mode that multiplies cost * qty and then put this in the y-axis of your card and choose sum. Put your date in x-axis and choose last 5 days in your date range filter.

Yes, a Domo Webform is a common way to do this. If you tie the form responses to an ETL, then you will see the results once the ETL has run. You can also use the ETL to join it to other data to incorporate into your visualization if needed. Form Builder is another option, but that is a premium feature.

I think the solution is to build a card that would meet that criteria and then set an alert when the summary number is greater than 1. For example, if you set your date range filter to last 2 weeks and then add a filter that is a count of your isLate column that is greater than or equal to 10 than your employee should show…

You can use the pivot tile to pivot your engagement type values into individual columns. This KB article will be helpful for you. https://domo-support.domo.com/s/article/360044951294?language=en_US

@M_Gonzalez I apologize. After thinking about your situation more, I realized my last suggestion would not get you what you want. I did come up with a way to do it, though, and have created a video to walk you (and anyone else) through how to do it.

I use the Dataset Copy Connector to copy the DomoStats datasets from my "child" instances to my "main" instance and then append them together in an ETL in my main instance. That might be a solution for you in the meantime.

@M_Gonzalez glad you are enjoying my videos. I think my "Filling in Date Gaps in Domo" would walk you through some of this. As far the the IFNULL, starting with your rank & window, the name you are assigning for your lag value is what you would be using in your IFNULL along with your main status column. With rank & window…

Here's a rough outline of how you would construct your ETL to do what you want. Bring in the calendar dataset. I suggest filtering it a bit as it has about 30 years of dates in it. You can use a formula in your filter rule to make it dynamic and not hard-code dates in there. Get a distinct list of products. I used the…

You might want to look into the faceted bar chart. https://domo-support.domo.com/s/article/7508982399767?language=en_US

You could create a beast mode that creates an include/exclude output and then drag this beast mode into your filters and filter to include. CASE WHEN DAYNAME(CURRENT_DATE()) = 'daycolumn' THEN 'Include' ELSE 'Exclude' END

Are you using ds_update? That allows you to update an existing dataset. Data sets - This set of functions is designed to transfer data in and out of Domo. ds_get - downloads data from Domo ds_create - creates a new data set ds_update - updates an existing data set, only data sets created by the API can be updated ds_meta -…

Here's a re-worked case statement: CASE WHEN Date of Death is NULL THEN FLOOR(DATEDIFF(CURRENT_DATE(), Date of Birth)/365) WHEN FLOOR(DATEDIFF(Date of Death, Date of Birth)/365) < 1 THEN '<1' WHEN FLOOR(DATEDIFF(Date of Death, Date of Birth)/365) < 3 THEN '1-3' WHEN FLOOR(DATEDIFF(Date of Death, Date of Birth)/365) < 6…

Yes, you can't create a "variable" in a beast mode and try and reference it later in your beast mode. Domo is working on functionality to allow you to nest beast modes, so you could create a beast mode called age and then in your age range beast mode you could reference the age beast mode. Your workaround right now would…

Agree with @trafalger . Here is a video on how to do it:

Have you tried the pivot table card? That would allow you re-orient your columns.

Great idea! Smart text is great and hope they continue to add improvements to it like this one.

BVK, I think you are going to need to elaborate on your idea a bit more in order to get it voted up. :)

@colemenwilson you might want to join the Domo Slack Group as there is some discussion there about people moving to this. You can join it here:

Domo is working on allowing for nested beast modes so that you can reference one beast mode inside of another one. Not sure the ETA on it, but it is being worked on.

You might want to look into the AutoML feature in Domo. If it isn't enabled, you can ask your CSM to enable it as a trial.

You can use a beast mode to exclude dates prior to today by doing this: CASE WHEN startdate < CURRENT_DATE() THEN 'Exclude' ELSE 'Include' END You would drag this beast mode into your filters and filter to Include. You could also choose to use enddate instead, so it wouldn't show all past projects. However, your 2nd part…

That is odd. I would suggest creating a beast mode that results in numerical values to put in your sorting. For example, I would do something like this: CASE WHEN Preferred = 'Yes' THEN 1 ELSE 0 END Put this beast mode as your first sorting and sort descending and remove the Preferred from the sorting. See if this does the…

Federated datasets are typically fully materialized and come from another Domo instance or from Snowflake, etc. They currently can't be used in ETLs because of how Domo stores the data. If you are using Workbench, these won't be federated datasets and you can use Magic ETL on these datasets to combine or manipulate them.…

You can install Workbench on a VM. That's where mine is installed. Just needs to be any Windows OS. A VM would be the best location because, as you said, if it is on your laptop, then it will only run when your laptop is on and connected to the internet.

Personally, I would make a plan to migrate all of your datasets over to Workbench so that they all run through that. Your security should like that better actually. As far as the SQL connector, if you have some that are running and some that aren't, if you have verified that they are all configured the same, then you might…

I would suggest using Workbench if you are able. It is very easy to use. With the SQL connectors, you are going to need to make sure the correct firewall ports are open, which can be challenging for some organizations. In Workbench, you can create an ODBC connection and then use the connection for your connection string.…