GrantSmith 🥷


Last Active
Member, Beta Premier, Beta Program, Sweetwater
Social Media


  • Yeah that sounds about reasonable. The one caveat to recursive dataflows is the don't scale the best as the larger the dataset grows the longer it will take to run the ETL (more data to transfer means more time).
  • Correct. Looking at the history of the ETL and the history of the DataSet both. Once the ETL finishes running does the DataSet history say anything before it finishes like "Indexing..."? It may be a case where the ETL finishes processing the data but then Domo still is working on storing the data and preparing it for…
  • Does the dataset show that it's finished or is it still stuck on another step when you look at it through the UI?
  • You can define a beast mode to conditionally set the context description and then drag that beast mode to the tooltip section o. The tip of analyzer. You may need to click the tooltip icon on the top to display the tooltip option. Then in your hover text setting on the card you can include the TOOLTIP1 variable in the text
  • Correct, you'd only pull in the changes that you'd need to be applied to keep your data processing quicker (less records). You'd need an initial pull of all your data to establish your baseline but then can just pull in the records that changed since the last time you've run it.
  • You can configure a custom report with the GA connector to select the exact dimensions and attributes you're looking for.
  • It’d be easier to pivot your data in an ETL and then use a formula tile or beast mode to calculate the difference between the two column values.
  • Currently no, this isn't possible but I'd recommend adding this as an idea to the idea exchange to get this functionality added.
  • It's not a very well documented feature, I just happened to stumble across it when attempting to come up with a solution for you. If you could accept the answer so others will find it I'd appreciate it.
  • You can use the ERROR function to cause the dataflow to error out with a specific message in a formula tile. CASE WHEN `Number` < 0 THEN ERROR('Number is negative') END The one caveat to this is that you have to save the ETL immediately after you enter this formula otherwise if it attempts to validate your ETL it won't…
  • CASE WHEN `Date` + INTERVAL (7-DAYOFWEEK(`Date`)) DAY = CURRENT_DATE() - INTERVAL DAYOFWEEK(CURRENT_DATE()) DAY THEN 'Last Week' ELSE 'Not Last Week' END To add some additional context I'm adding a specific number of days to the date field to get to saturday (7) of that day's week then comparing it to last saturday…
  • I'd recommend importing your historical file into Domo, then creating an ETL to simply output your historical dataset to a dataflow dataset. Then you can remove the historical input and convert your magic ETL to be a recursive dataflow to then update any new records or update any records in your existing dataflow dataset…
  • Likely you're swapping the order of the parameters. If you reverse the order it should get you a positive number. The order is backwards where it expects the end date as the first parameter and the start date as the second parameter.
  • I’d recommend reformatting your dataset to use a custom date offset dimension dataset. This will allow the interactions with the page date filters and simplify your data structure. I’ve done a write up on this previously here:…
  • Currently this isn’t supported with a Gantt chart. You could uses drill path possibly to go to a table card which you can display and use a hyperlink to then open your project.
  • This sounds like a bug. I'd recommend opening a support ticket with Domo to have their engineering team take a look at for you.
  • You could pre-filter your dataset using two dataset views (period type = current and period type = last year) and then use those as an input into your ETL. That'll do the filtering in the adrenaline layer (essentially in memory) instead of having to transfer all 80M rows you have over the to ETL process and transferring…
  • You can use a case statement to conditionally return a value or NULL if it doesn't match the logical expression. Something like: CASE WHEN LAST_DAY(`Period Date`) <= LAST_DAY(CURDATE()) THEN `Value` END You can then use this beast mode in place of your original value. I'm using LAST_DAY to return the last day of the month…
  • Since you're using the PoP dimension you can create a new ETL with the PoP dataset as the input, have two filters `Period Type` = 'Current' and `Period Type` = 'Last Year' then do a join of these two fiilters based on the report date. That will combine them together on the same row for your output dataset.
  • I’d recommend looking into the DomoStats connector to pull metadata information about cards pages or datasets among other options from your instance to then visualize or alert on.
  • How are you attempting to clean these codes? What is the business logic you’re needing to replicate?
  • Are you using Date Query parameters? I'm assuming that's the case in which it would cause Domo to validate the date string. In this instance it won't work if you're using relative values. Have you tried passing it via a string query parameter?
  • When configuring your Campaign - does the dataset you're using still exist? Is the column that's configured to hold the email addresses correct / exist? Are you using CC or BCC?
  • Since it's not supported in Domo's connector you'd likely need to write your own connection to it. Currently there's two options you can pursue to make your own interaction with the Asana APIs: Write your own custom connector: (JavaScript) Utilize…
  • Since there's no built in connector for Ironclad to Domo you'll need to create one yourself. You have a few options, all being technical. Write your own custom connector: (JavaScript) Utilize Python to write your own script to interface with the API and…
  • You can filter your card to display only the latest information using analyzer and then on you can edit the dashboard it's on and change the interactions and tell it to not be affected by any filters.
  • Segments only creates a subset of your data but doesn't remove it from the original dataset. If you need to you can create two beast modes to do the Canada filtering for each of your metrics -- Canada CASE WHEN `Country` = 'Canada' THEN `Value` END -- All Others CASE WHEN `Country` <> 'Canada' THEN `Value` END
    in Segments Comment by GrantSmith August 9
  • You'll need to log a support ticket and have Domo's connector team update the API endpoint it's calling.
  • @Sudershan - Glad you got it figured out. Make sure to mark your answer as a solution so others will be more easily find it if they have a similar issue.
  • @MattBeal If you're not pre-filtering or dropping columns from your dataset with your views then you're likely not to see any improvement as the same amount of data needs to be transferred over to the ETL processing platform.