GrantSmith Coach

Domo doesn't have a Clover connector yet however you can write your own connector using Domo's framework and some javascript. You can read up on how to create your own connector here:

Add your DATEDIFF beast mode to your sort section on your card.

Likely these demo dashboards are shared with the Default Group that users automatically get added to when they're created. Unshare them with the Default Group and it should solve your issue.

You can use the settings on a table card under General > Number of Locked Columns to specify the number of columns on the left you want to freeze.

You can use the Date Dimension dataset and join your hours and wages dataset based on the day of the week, then you can use the year and month values in the date dimension dataset to aggregate on a monthly basis.

Currently Domo doesn't have an Apache Iceberg connector. It also doesn't appear to support ODBC connection either. You can attempt to write your own connector or utilize Workbench and an ODBC-JDBC 3rd party bridge to convert ODBC to JDBC and use JDBC to connect to Iceberg.

Domo functions on a row basis, so you need to have the records in your dataset you need to display. It can't infer values based on a start and end date.

You'd likely need to utilize an event on your drop down to store the order in which the values are selected and also handle it when a value is deselected. You could store it in a hidden input type in a form on your DDX brick and then reference it when the event occurs so that you add or remove it out of the csv list you're…

That’s what I’m referring to. You see there’s an error where the mapbox token variable is undefined. Have you defined it yet? Also there appears to be an issue with a forEach loop. If you click on the error file name it should show you where the issue is occurring. I’d start looking into both of those errors

If you inspect network traffic are there any errors that are being thrown in the console?

Whenever I'm doing Period over Period analysis I will structure my data with my own custom date dimension dataset. You can then define how the offsets are and allows you to more easily filter your datasets so that you can look at this quarter but also have records for last quarter. I've done a write up on this approach…

DDX Bricks are pre-built with the number of datasets available. You can't modify these. If you're wanting more control over the number of datasets you want to use or their aliases you can leverage a custom app which is similar to a DDX in terms of having an HTML, CSS and JS files but you also get a manifest file to define…

Clever @MarkSnodgrass!

The Fixed function is returning a single value for each row and you're adding that to an aggregation across your entire dataset so it doesn't know how to handle this. You'd need to aggregate your fixed function again so that you can add the two together. SUM(SUM(DISTINCT Balance) FIXED (BY Client, Item)) + SUM(Received)

Wrap your entire outer/first case statement in a SUM function and replace all SUM(`Budget`) with COALESCE(`Budget`,0). Do the same for Actual its doing the subtraction after all records have been added together instead of summing the differences for each record causing the discrepancy

Currently there isn't a simpler way to do this within Magic ETL. You could attempt to utilize MySQL dataflow to programmatically rename the columns if you have a consistent format you want to rename it with.

Are you aggregating anywhere else within your card? If so Domo doesn't know how to handle the results of your window function as it returns a single result for each row.

Another alternative is to re-architect your data so that you have different offsets for your different dates. This way you can select the current year but show the current year, last year or any other period you've defined. I've done a write up on this in the past here:

The card errors happen when the card is rendered but not recorded. The closest you can get is having the status at a specific time and then look through those cards specifically. There isn't a real-time option to see which cards are actively broken.

Due to how DDX bricks are designed and iframes work in general this isn't possible. <iframe> is another separate browser window. It's just a means of 'seeing' inside that web document through your parent document. It's different than a normal in which you can extend elements outside of its margins. Also, it is considered a…

You'll need to log a ticket with Domo Support as they control the code to this connector and would be able to give you a bit better support as they would have access to their internal logs.

The DomoStats connector has a new dataset called Card Loads which will return an error code to see if it was a Success or not.

Currently this isn't an option within the smart text. I'd recommend adding an idea to the idea exchange. You can utilize an ETL to populate a field within your dataset to show the date / timestamp when the data was updated in your dataset and then use that field in the smart text.

Without having more information about what your issue is I'm assuming it's dealing with your prev month where it's subtracting a month. You want to make sure you subtract a month from your date before getting the month and year for it. CASE WHEN 'metric'= 'CURR MONTH' THEN CONCAT(MONTH(NOW()),'-',YEAR(NOW()) WHEN…

This sounds like a bug with Inline Editor. I'd recommend logging a ticket with Domo Support to have them investigate the code on their end.

Have you tried using a window function and adding it to your sort at the top so it's sorted first? SUM(SUM(`Balance`)) OVER (PARTITION BY `CustName`)

There isn't a programmatic way of doing this but you can edit the beast modes a bit easier within the Beast Mode Manager instead of having to do it by opening up individual cards.

I'd recommend logging a ticket with Domo Support as it sounds like a bug with Workbench they'd need their development team to look into.

Depending on your groupings and the metrics you're calculating you can either group by and then join it back to your original dataset like you mentioned or possibly use a Rank and Window tile to do your aggregation within your entire dataset and leave your columns in place. But @ColemenWilson mentioned, aggregation drops…

What is the students field? Is that the number of students, or is it some other value? Is it numeric or text?