GrantSmith Coach

As this app is developed by Domo you’ll need to contact support as it sounds like an issue with how the app is trying to send your data.

Currently Variables only support storing a single value so checkboxes are not an option for variables. I'd recommend adding this to the idea exchange to have variables support multiple values.

You can utilize what Domo calls a Beast Mode or Calculated Field. You can refer to their documentation on the Knowledge Base as a good starting point: Also, Domo does provide a Pivot table for you to use as a visualization if you're needing that type of visualization.

Create a duplicate beast mode with the same logic you're using to create the ranges but instead of returning the ranges return a number to sort on (0, 1, 2, 3 etc) then use that new sort beast mode as your sort on your card.

If you copy and paste the actual arrow instead of the code it should work for you

This is an issue with X / Twitter's API usage restrictions coming from Domo. You'd need to reach out to Domo Support to have them help you with this specific error as it's their API connection that's being utilized to pull the data.

@Tung Currently there isn't an option to hide the others. As you can see there's a lot of great ideas coming from the community and more than one way to do something within Domo. Welcome to the forums!

@Jean_McDonald Yes, the Domo Dimensions Calendar Dataset has dates through 2030 in it so you can view future dates.

Domo doesn't have a way to display a vertical line as you're wanting. You could utilize a beast mode to check to see if it's today, if it is return the value. CASE WHEN `dt` = CURDATE() THEN `random_number` END You can utilize a symbol line to display your values and then have Today being displayed on top of it like this:…

Currently this isn't an option. You're not able to dynamically set the column labels like you're wanting to do. Have you looked into utilizing data labels and tool tips in your visualizations?

Here's a link to an existing Idea Exchange post to create something like a block tile which may be similar:

@MichelleH has written up a great article on the community blog you can reference on how she did geospatial distance calculations using a Redshift dataflow.

You can't aggregate your data three times. Try taking out the SUM(`Loads`) in favor of just `Loads`. Same thing for the carrier pay field. Also another alternative to DATE_FORMAT(CURRENT_DATE(), '%Y') is just YEAR(CURRENT_DATE())

You could configure a beast mode to return the opposite and then do a NOT IN CASE WHEN Target Go-Live Date` IS NULL THEN 'Blank' ELSE 'Not-Blank' END Alternatively if you're wanting to do that exact value then set the Blank value for when it's populated. Do your filtering then change your beast mode back.

It appears you're using the Last_Production_Date as the date field in your date picker but you're filtering in your ETL based on Order_Completion_Date. Do these end up being the same data or are they different? If they're different you can try and drag the Order_Completion_Date field into your analyzer to force the date…

It's attempting to connect to the database but running into connection issues. Are you able to get a response from the server that's hosting the data source? Are you behind a firewall that would restrict access?

Do you have some sample data to see what your dataset looks like?

When you're evaluating this beast mode it's going record by record so one part of your equation will always be null, you'd need to calculate the max BatchTimestamp date. Are you keying based off a specific identifier field in your chart? Something along the lines of may work depending on how you're displaying your data:…

Create a beast mode which returns YEAR(`CreatedOn`) to return the year and save it to the dataset. Alternatively you can calculate this within a dataflow. Then use this new field in your slicer filter to allow users to filter for a specific year.

Perhaps it may be an issue. I'd recommend reaching out to Domo Support to engage them as they own the connector code.

Domo has released a Domo Brick "Searchable Filter App (Multiple Columns)" which may be helpful for your user case. I'd recommend searching for it in your app store.

Are you using a date field in the graph? Does your data have different date values or are they all the same date? Can you post a redacted screenshot of your analyzer with the date picker expanded?

There's a 30 second timeout for adrenaline dataflows. You'll need to either improve your query performance by rewriting it or attempt to process less data so that the execution time is less than the 30 seconds.

Have you tried using the limit and offset parameters in your GET request to extract the data from Domo paginated?

Not with the out of the box HTML table. You can leverage a Domo Brick and some javascript to perhaps display the pie chart within the graph itself.

It's a permissions based issue. You need to make sure the user is part of the Windows group "Domo Workbench Users" on the actual windows machine where workbench is hosted.

@jgRugby_123098 Since your invoice number field is a string you need to use strings in your IN clause. You can do this by putting them in single quotes SELECT * FROM CHARGE_DETAIL WHERE INVOICE_NUMBER IN ('217653436', '217668183', '819802440', '820092602')

Currently no but I'd recommend adding this to the Idea Exchange

because you’re filtering on price differences and valid and invalid it’s filtering out all downstream data which is why you get what you’re seeing. If you’re wanting to filter on the top level then you’d need to calculate the top level value and included that on all you records so you can filter on that value instead

Seems like an error with your id and secret. Can you create a new pair and try with those?