MarkSnodgrass Coach

I would try submitting a ticket to support@domo.com to see if they can enable it for you if it currently isn't.

Looks like @Data_Devon proved me wrong as I needed to reset my chart properties first, Great job Devon!

It does not look possible to show it within the center of the chart. However, I would suggest using the summary number to display the total. That is the most common use of the summary number.

@DanHendriksen will likely know the answer to this.

Did you have a question about datasets?

You can use the line chart for this. Create a beast mode for each of your metrics. Put the first one in the y-axis and put the second one in the series. It will cause it to create two lines. A couple of these videos may be helpful for you. https://youtu.be/JlTJ6z401r4 https://youtu.be/mDwSQGAjIrs

There is nothing in Domo that would allow you to do this. There are some browser extensions that you could install that would allow you to view pages offline. You could also look into doing this in Chrome: https://support.google.com/chrome/answer/7343019?hl=en&co=GENIE.Platform%3DDesktop

I am on consumption so I can't say for sure what it is like for non-consumption, but I haven't heard that it was a consumption only feature. You could check with your CSM to be sure. In Admin - Roles - Grid, do you see the AI Chat listing?

If you are using the new navigation, the AI Chat icon is now located on the left navigation.

I'm not seeing Brent in your sample table so I'm having trouble visualizing a solution, but maybe that is part of your issue because that is how the data is coming across? Regardless, I often use a webform or similar to create a lookup table to help with the effective date piece. I may have some other ideas based on what…

I would use the variables feature to accomplish. You would want to use the radio button control in the variable creation and create two options: Last 3 months and Last 6 months. Then, create a beast mode that looks to see which option is selected by the user: CASE WHEN variablename = 'Last 3 months' THEN CASE WHEN UTC_DATE…

If you don't want records where the actual end date is after the current date, then you would want to filter them out by doing this: Date(ActualEndDate) < CURRENT_DATE()

Andrew Chaffin at Argo Analytics has a solution that exports out ETLs and converts them to SQL. You may want to reach out to him. https://argoanalytics.ai/

I find it easiest to use the formula option in the filter tile to do this sort of thing. I usually wrap my field in a date() function to make sure it sees it as a date as I have had Magic ETL get confused sometimes. DATE(startdate) < CURRENT_DATE()

Mixing window functions with non-window functions can often be challenging. That message is just a warning and not saying that what you did won't work. I did refactor your formula to make it more concise if you want to use it ( SUM(IFNULL(Disconnects, 0)) / (SUM(SUM(IFNULL(ServiceStatusValue, 0))) OVER (ORDER BY…

I have received that message as well. It is actually potentially just a warning. If you save and close the beast mode and use it, it can still work. Did you

Using the UNIX_TIMESTAMP function is the way to go to get the time difference. I would start out by just doing the simple subtraction between the two dates using the UNIX_TIMESTAMP around both of them and making sure it validates. Then, start adding in your additional logic for the CASE statement and make sure it…

You can look into using the SharePoint Writeback Connector to push a Domo dataset to a sharepoint directory. Here's the KB article to look into how to set it up. https://domo-support.domo.com/s/article/000005677?language=en_US

I'm experiencing the same issue where I have set the Filter and PDP icons to not show on the dashboard, but the PDP icons are showing anyways. I have toggled it to try and reset it, but it didn't help. Will likely be submitting a ticket. I would encourage you to do the same so that it gets elevated.

Yes. If you can manually remove the parentheses and use a minus sign instead, that should allow for a safe conversion.

The presence of the $ sign prohibits the alter columns tile to convert it to a decimal. I would add a formula tile before the alter columns tile and use the replace function remove the $. I would do something like this on each field: REPLACE(totalpaid,'$','') REPLACE(totalcommissionable,'$','')

That's a good call out that they haven't updated that type of information with the addition of app studio. I would start by submitting it as a bug to support@domo.com and see what their response is. If they say it is not a bug then I would submit as an enhancement in the Ideas Exchange.

I did some testing and it doesn't look like you are going to be able to achieve what you want in a single card. Since you are specifying that you want 5 lines in the series on left scale property, it is going to prioritize that as it works through the number of series items before adding bars. I would suggest building a…

Do you have anything in your Sorting section? That can affect items being grouped.

Can you supply a screenshot of what you have set up in Analyzer? Seeing what is in the x-axis, y-axis and Series will be helpful. Also, in the chart properties - general, are you specifying the number that you want to see in the series in the left scale?

Based on the red message, it seems as if the support portal is having issues. I create my support tickets by e-mailing Domo support at support@domo.com . You will get an automatic reply back with a case # that you can refer to and continue to manage the ticket through e-mail.

Hi @ArborRose workflows don't have any porting capabilities, so you have to build it from scratch when recreating it in another instance. (I plan to submit an Idea Exchange to have some sort of porting capability in the future).

Case statements are case sensitive. It looks as though your data has those statuses in all caps, so you need to do the same in your evaluation. Change it to this and you should be good: Status IN ('CLINIC','SURGERY')

Your issue is that you need to use the IN clause when you need to look for multiple items. Notice how in my statement I put parantheses around the list of items I am looking for. Like this: Status IN ('Clinic','Surgery') That should resolve the error

Here is how I typically do this sort of thing: SUM(CASE WHEN Status in ('Clinic','Surgery') THEN 1 ELSE 0 END) / COUNT(Status) Using 1's and 0's allow you to use the sum function. Then divide it by the count of all the status.