MarkSnodgrass Coach

@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. https://youtu.be/MgB__mhgrU4

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: https://youtu.be/9iNpzSL5V6U

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: https://domousergroup.carrd.co/

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.…

Are you using Domo Workbench to connect to your SQL database? Or are you using a connector that you choose from in the Data Center?

You can use the Line + Grouped Bar to have your bars plus lines as running totals. You will need to edit your chart properties to this:

Listagg is not a supported function in beast mode. You can use GROUP_CONCAT in a MySQL dataflow as an alternative. You could also look to use the pivot/unpivot tiles in Magic ETL as another option.

Yes, many people are dealing with it right now. Seems to be timed as to when Domo pushed out an update. Brought a lot of things to a crawl. Some people are starting to see an improvement. I expect Domo to have it worked out in the next hour or so.

Agree with Michelle that you should use the timezone transformation if you actually need the time. If you don't actually need the time in your analysis, go the schema tab and change the data type from datetime to date. When it is just a date field, Domo won't try and apply any timezone shifts to that field.

Unfortunately, it's definitely not on the admin page of your screenshot and I don't see that as a field in Domo Stats or Domo Governance to be able to build a card that would tell you which ones need locking. Looks like a good suggestion in the Ideas Exchange as you suspected.

Definitely interested in seeing more about app studio. Would like to see more about the office add-in and how someone has really taken advantage of it besides adding a single card.

Domo has a lot of free classes available in their University section of Domo Central (click on University at the top of this page or go to https://learndomo.domo.com/ ). You can choose to learn by skill or role and look for the free ones. Domo is also doing a Domo Customer Orientation workshop that is online and free. Your…