GrantSmith Coach

This sounds like a bug. I'd recommend logging a ticket with Domo Support.

Have you tried using an i frame in your HTML code with a link directly to your card url in the Domo brick?

Are you dealing with percentages / decimal numbers and have it set using whole numbers? Does your mom and max values go under your max value in your dataset?

You can tell the Magic ETL DataFlow to run only when certain input datasets have been updated. This document may be of use: Since you're not wanting to replace the old data you can bypass the join and filter sections of the ETL in the documentation.

You'd need to reach out to Domo Support directly as this would require them to do a custom environment installation for you if they even allow it. Have you looked into other packages which wouldn't require a driver like beautiful soup?

You'll need to stack / pivot your data so you have a singular date field instead of multiple per row. You data would look something like: Order ID | Date | Date Type | Order Total 1 | 1/1/2023 | Created | $123 1 | 1/7/2023 | Sales | $ 123 Then you can use the new Date field to make sure you're getting records affected by…

If you have your raw dataset (not the snapshot version) as an input and the snapshot dataset as an input you can just calculate your current date with your formula and then use an append tile to join the new version to the historical snapshot dataset and then output to the historical dataset.

This sounds like a bug with the Domo APIs / SDK. I'd recommend logging a ticket with support to have them investigate deeper.

You can use a dataflow / magic Etl to pivot your dataset so that you have the columns member and event and signed up and then filter for signed up = TRUE You can then use that output dataset in your pie chart with the event as the series and do a count of the members

Does your dataset ID exist in the instance you’ve authenticated to? Does the user you’re authenticated as have access to edit or create datasets?

This happens when the response back from the API is empty. You had mentioned that you're attempting to append to your dataset but by default data_import will utilize REPLACE. Have you tried adding, update_method=UpdateMethod.APPEND to your data_import call?

Domo offers the Data Science package which includes Python tiles and Jupyter notebooks which you may be able to leverage to perform the translations via something like the Google Cloud Translation API ( The data science package is a premium feature. Alternatively you do the data processing via a python script outside of…

Hi @JoshBethers It appears that access and the APIs for the feedback survey data are in Beta only so it's likely Domo doesn't have access to this endpoint yet. You could attempt to join the beta and pull the data yourself and upload it to Domo with a custom connector or the Domo APIs. You can find more information on these…

You can also create your own custom connector to pull eBay data if you are technical enough and know javascript https://developer.domo.com/portal/5d8f965eb3469-overview

Alternatively you can combine both together and use a coalesce and NULLIF COALESCE(NULLIF(TRIM(`fieldname `), ''), 0)

@Pellogat Does you old system have an email address associated with the usernames or do you only have the usernames? How can you determine in the old system if a user has multiple usernames / accounts?

You can utilize the Java CLI and the backup-card command to export the definition of a card to a JSON then modify the JSON definition to include your color rules to include values which don't currently exist in your dataset. Then utilize the restore-card command to upload those changes to your instance. Make a copy of the…

The code is appending each record to the end. If you want to change it to add them to the beginning you need to use prepend: $table.find('tbody').append($row); Becomes $table.find('tbody').prepend($row); in the addRow function (originally around line 198)

Here you go: https://community-forums.domo.com/main/categories/ideas it’s another section on these forums.

You could possibly use a FIXED function and the FILTER ALLOW clause to only allow filtering on a specific date field when calculating your totals. Here's a link to documentation on FIXED function:

Currently this isn't possible with the default scatter plot. You can add this recommendation to the idea exchange to possibly add this to Domo's roadmap. Alternatively you could look into utilizing a Domo Brick to write your own scatter plot and allow for this type of line but that's a much more technical and involved…

To expand on @MarkSnodgrass 's answer you'll need to use the FILTER DENY or FILTER NONE clauses in a fixed function to prevent filtering from happening on the value. SUM(`Value`) / SUM(SUM(`Value`) FIXED (FILTER NONE))

Domo would suggest the Data Science package to allow for R or Python tiles to do the NLP processing in a magic ETL dataflow but it's an extra cost. You can utilize rdomo to extract data from Domo and process it and re-upload it (or pydomo if you're a Python fan). There's nothing currently out of the box to do NLP.

Currently the data table will only display the data that's displayed on the graph. There isn't a way to have it included in the included table without displaying it on the graph. You could have a separate chart for just the graph and include the data you wish there on the page. Alternatively you can suggest this through…

You can use a formula tile to populate a new user id column in your old dataset by just appending the @email.com with a CONCAT formula: CONCAT(`Old User Name`, '@email.com') Then you can use that new field to join to your new dataset and get similar records.

Good clarification @MichelleH @jtrollinger it should end up with something like this CASE WHEN `HdrParentItemCode` IN ('ZROUGHIN', 'ZWATER', 'ZSEWER', 'ZROCK', 'ZVANGUARD') THEN 'Rough-IN' WHEN `HdrParentItemCode` IN ('ZTOPOUT', 'ZGAS') THEN 'Topout' WHEN `HdrParentItemCode` IN ('ZTRIM','ZDROPIN') THEN 'Trim'…

Alternatively you could filter the rows for non null values, feed that into a remove duplicates based on your two ids and the use a join tile to join them back together based on the id fields and then rename the new category

If the category is the same across for each store and ticket I’d you can use a rank and window tile to get the max value of the category for a new column and then use an alter column tile to drop the old category field and rename your new category field

@Aag2023 there aren’t individual edit permissions currently within Domo for dataflows. Permissions are based on the input datasets. I’d recommend adding an idea to the idea exchange for added dataflow security

Only the first CASE keyword is needed you can remove the others but leave them when and clauses