MarkSnodgrass Coach

This was an issue that was spotted and engineering pushed out a fix today to address the issue. If you are still seeing the issue, send in a support ticket.

I have heard that you can put it in a request to support to get it configured to 1 minute. The other workarounds I have heard are using webhooks or workflows to kick it off.

The administrator needs to do it by going to Admin - People - clicking on the user and then clicking on the Change Password button and creating a new password. This process unlocks the account.

On your 3 slicer cards, you can edit the dashboard and choose change interaction for each of them and de-select the other two slicer cards to keep them from reacting to each other.

The way your original case statement is constructed, and assuming that all rows have the Leverage Ratio column populated with the string Leverage Ratio and the Leverage Ratio Values column has a value in it, then only the first 3 WHEN statements will ever be used in your evaluation because CASE statements automatically…

A couple thoughts on this: The first thing I would try would be to re-order your WHEN statements so that all of your Low Risk items are first, followed by the Medium Risk and then the High Risk items. Since case statements stop evaluating once they find a match, if you want someone to be low risk if they meet any of those…

@emaynez it looks like dt is not an actual field in your dataset. Replace dt with the date field that you want to use, and see if it validates.

Try this: CONCAT('<span style="font-size:10px;">Data as of ', MAX(Transaction Date),'</span>')

You can add HTML/CSS in the beast mode and add color and control the sizing. A simple example would look like this: CONCAT('<span style="color:red;font-size:10px;">Vehicles</span><br />', SUM(Vehicles)) One thing to note, you won't see the changes while you are editing in Analyzer. You will need to Save and Close in order…

Glad you figured it out.

@GrantSmith may know the answer to this one.

Unfortunately, the smart text doesn't allow for that in the card title. I have utilized the summary number to display this information. You can create a beast mode that utilizes the CONCAT function and your MAX date to do it. Something like this: CONCAT('Open date max date is', MAX(opendate))

Adding a PARTITION BY would do it. Perhaps by WEEKNUMBER(datefield)

How does a user access the pro-code editor? I'm not sure where to look for it.

To get rid of dates that are older than today, you would want to modify this statement to look like this: CASE WHEN DATEDIFF(MAX(Billing Month New),CURRENT_DATE()) >=0 AND DATEDIFF(MAX(Billing Month New),CURRENT_DATE()) < 60 THEN 'Program Ending' ELSE 'All good' END

Hard to say for sure without seeing your data, but something like this might work: CASE WHEN DATEDIFF(MAX(billingdate),CURRENT_DATE()) < 60 THEN 'Program Ending' ELSE 'All good' END You can then drag this into your filters and filter to Program Ending. Your table card would need to have your program name and then your…

I have been using this one for a few years now for earthquakes from the USGS. https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_month.csv You can use the CSV Advanced Connector as set it up as an HTTP Request. Hurricane data has been trickier. You can get a CSV file from here:…

I haven't found very many good pre-built weather connectors myself. If you find a good API to query, you can use something like the Jupyter Notebook to pull in the data and create a weather dataset and then use Magic ETL to join that to your property data based on date and location.

This thread may be relevant to you as far as the colored directional arrow. I made this video a while back about the color options in Domo. It may be helpful to you.

You could potentially do this using Domo bricks. It's going to require a fair amount of Javascript and the Phoenix chart libraries to switch it based on your different types. If you aren't skilled in Javascript, it's going to be quite challenging.

I would suggest hiding the legend with the chart properties and then using the data label settings to show the information that would be in the legend, but within the pie slice, which would allow you to use the tooltip field and show a negative number.

The pie chart is going to have a hard time determining a percent of total, and the size of each pie slice, with a negative number. If all your numbers are negative, you could try creating a beast mode and multiplying the value by -1, or use the ABS() function to force it to be positive. You can then drag that beast mode…

That would be nice. I would suggest it as an idea exchange. It will bring in the descriptions if you utilize the dataset schema to write descriptions on columns. I have been doing that before going over to the AI Readiness section as I find that area quicker to fill out and then the descriptions are also available for card…

Have you run it through and looked at the completed output dataset? I have found the preview within Magic ETL to be misleading on date/times.

did you look in the data center under datasets? That is where I have seen them as I often include them in a Magic ETL dataflow.

I think you might want to do some troubleshooting to see what is actually in there. I would suggest creating a beast mode that uses the INSTR() function will return the character number for the searched character. I think you should look for a single quote and as well as a full quote. To look for a full quote use this:…

One way you can connect your Azure SQL database to Domo is through Domo Workbench. You can create an ODBC connection to your database and then use that connection in Workbench. Workbench allows for a lot of scheduling options and transfers the data securely.…

An easy way to get accurate counts of this is to break up your lists into individual items, with each item in its own row. You can do this dynamically in Magic ETL using this process:

I am not a fan of regex as I find it difficult to read, maintain and troubleshoot. I would suggest the following: Take this example: I use the formula tile and start by using the RIGHT() and INSTR() to find the starting position of Amount USD: I then use the SPLIT_PART() function to look for the amount by getting the…

@Domolex welcome to the forum (and there are no bad questions here). It is certainly smart to first try and build what you need off the source dataset and see if you can skip the ETL execution. To count distinct event ids you can create a beast mode that looks like this: COUNT(DISTINCT eventid) You can put your date on the…