MarkSnodgrass Coach

Is your data in all uppercase? The evaluations can be case-sensitive.

It looks like you are using the heat map table. If you switch to the mega table chart type, you can use the expand/collapse feature I suggested.

You could do this in the table by putting your classification in the first column and the content type as the 2nd column and the % as the 3rd column. Then, in the chart properties, go to Subtotal rows and and select Show Subtotal Rows. This will create an expand/collapse feature on the first column, which will allow the…

If you put two single quotes there instead of just one, it will know you will want to use a single quote. BISCAYANE MEN''S WELLNESS CENTER

In the Chart Properties - General, you can enter a value in "Maximum Slices Before Other" and that will limit. Make sure you also have your sales metric in the sorting properties and set to descending.

When troubleshooting these kinds of things, I will temporarily create multiple beast modes that is just extracting a single component so I can see where the logic is off. Try making a beast mode just for days using the logic for days and see if that reveals to you what additional logic you might need to add. My days logic…

It looks like your data has extra spaces at the end, which is why it is displaying the full value at the beginning when there is no day at the start. Adding a TRIM function around the field would help. Also, looking to see if there is a space towards the start of the string to see if there is a day value will work as well.…

You can use the SPLIT_PART function and CONCAT function to build this. It would look something like this: CONCAT( split_part(Time,' ',1),' days ', RIGHT(split_part(Time,':',1),2),' hours ', split_part(Time,':',2),' minutes ', split_part(split_part(Time,':',3),'.',1),' seconds ' ) You would need to add additional case logic…

Possibly. Something like this might work.

You would need to add an additional output dataset, but if you did a group by to get the max date in the dataset and then also apply the LAST_DAY() function to make normalize to a single date in a month. This should give you a single row. You can then set the alert for when the any row has changed. Hope this helps.

You might need to define closely match. The first thing I would try would be to use the TRIM() and LOWER() functions on both addresses to remove any hidden spaces and eliminate any case sensitivity issues.

@chetan_cricut here is what @GrantSmith is suggesting. From the list of charts, choose Gauges and select Multi-value Columns chart. In the date range select Previous and Last 4 Days Create a beast mode called "Last 3 Days" that looks like this: CASE when date >= DATE_SUB(CURRENT_DATE(), INTERVAL 3 DAY) THEN confirmed_total…

I see what you mean in the series for the non-hovered bars in the series. I would start with a support ticket and see if they acknowledge it as a bug. If you don't have any luck with that, I would submit it as an enhancement in the Ideas Exchange and see if it gets incorporated into the future. Glad you are enjoying my…

I'm not surprised if you are having trouble as I have found changing background colors to be problematic. I believe there is hope in the coming months with the release of App Studio that was shown at DP23. However, I tested changing my dashboard background to black and the card background to black and left the hover text…

Seems like a support ticket might be necessary. In the meantime, you could copy and paste the contents of your ETL into a new ETL and try and run it. You will have to create new output datasets in the process. I would also suggest breaking it out into two ETLs and try and determine if it is the lower smaller workflow is…

Possibly. Can you go back in and Edit the dataflow and then click Save and Run?

Looks like a permissions issue. Mine is like this: I would reach out to your admin and get the permissions adjusted.

In the data center, click on the dataflows icon on the left side of the page. then search for your dataflow name, "constructor ETL" and click on the title. This will take you to the Settings section of the dataflow. In the far right, you can click on the 3 dots and click on Run to force it to run.

These are frustrating errors. When this has happened to me, if it says it saved, then I just close the tab and then run it from the ETL overview page. If it runs successfully, then I'm good. Otherwise, I go back in and edit again. Usually it runs fine after that. Hope this helps.

@larryjacobs Here's a screenshot of a dataflow that I use to find unused datasets. Here's the JSON for it, which you can copy and paste into an empty ETL and then connect your Domo Governance Datasets at each input spot and then see which fields I am using for each. Hopefully, this will help you know which field to use in…

Sounds like you just need to look at the Equipment # column for your beast mode, which evaluates by row automatically. It would look like this: CASE WHEN 'Equipment #' LIKE '%100%' THEN 1 ELSE 0 END

Each workflow has a settings tab which is where you can schedule how it should be kicked off. Your 2nd workflow can be kicked off by when your input dataset is updated. Choosing the Trigger of When Datasets Update and then selecting the appropriate datasets will cause your 2nd dataflow to once any of the selected datasets…

Displaying the quick filters directly on the card in the dashboard view is not currently an option. You could submit it as an idea in the Ideas Exchange as a future enhancement.

You can create a second card that uses the slicers chart type and have that at the top of your dashboard. This will interact with your main graph on your dashboard.

You can take your result object of your first workflow (which would be your output dataset) and make it the input dataset of your second workflow. To use these objects as "parameters" against your main dataset in your second workflow, you can set a constant of 1 on both datasets and join on that value. This will make it so…

Yes, you can do this with some of the dataset that are available in the Domo Governance connector. Specifically, you would want the Dataflow Details dataset and the Datasets Dataset. You can then build an ETL to let you know which ones are used and which ones aren't.

I agree with you that it doesn't appear to operating the same as the indicated definition in the formula editor. I would suggest sending it in as a bug to support@domo.com and see if they will fix it. In the meantime, I would use WEEK() as you definitely have more control with the extra parameter options.

Beast mode functions tend to follow the MYSQL definition. https://www.w3schools.com/sql/func_mysql_weekofyear.asp Where are you see inconsistencies? I got the same result in my card and the w3schools editor when entering in 6/19/2023.

Is it also possible that some of your rows don't have leading zeros and some do? If so, you can use the LPAD() function to add leading zeros if everything should be a certain number of characters.

Here are a couple common issues with joins in Magic ETL It is case sensitive Leading or trailing spaces An easy way to address both of these is to add a formula tile to each table prior to the join and use the following functions UPPER() - converts the text field to uppercase TRIM() - removes any leading or trailing spaces…