Comments
-
You can create it with a beast mod4e instead of adding rows. CASE WHEN `Series` = 'Goal' THEN 150 END And if your dataset includes a market column, drag that to the filter section or add a page filter.
-
Using a sample set, I'm thinking you are asking for something like this: Quarter,Series,Value Q1,2023,120 Q2,2023,140 Q3,2023,135 Q4,2023,150 Q1,2024,130 Q2,2024,145 Q3,2024,160 Q4,2024,170 Q1,Goal,150 Q2,Goal,150 Q3,Goal,150 Q4,Goal,150
-
Save the following code with an html extension, then drag it up to your Chrome browser to see example. <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8" /> <title>Date Range Filter Prototype</title> <style> body { font-family: system-ui, -apple-system, BlinkMacSystemFont, sans-serif; background: #f6f6f6;…
-
We are working blind without an example. Can you create some fake / sample data?
-
Trying taking your deviation formula, in whole, and put it into your next step. Account Payments (cash, model) * ( SUM(CASE WHEN Month <= CURDATE() THEN Account Payments (cash, actuals, projected) END) / SUM(CASE WHEN Month <= CURDATE() THEN Account Payments (cash, model) END) ) And since you don't want a divide by zero,…
-
I agree - that looks like a Domo issue.
-
I believe David is onto the basic problem…aggregation. Something like this should work: SUM(row_value) × aggregated_metric Something like this will not: SUM(row_value × aggregated_metric) Your deviation ratio is already an aggregated calculation because it uses SUM. And Domo isn't allowing nested aggregations.
-
I'm not sure that you can. I think it just leaves orphans behind if you delete the app without first deleting the contents. You could try using the Governance Toolkit to identify the lineage /asset to find which apps reference which cards.
-
Sounds like a good submission for a product idea. I don't do a lot in pro-code but I had a similar issue when I did. I couldn't find the notes after saving them. So, I wrote my notes and comments in the code. And when I saved the files, I put the version in the filename, mycode_v1_12.js. /* VERSION 1.14 2026-01-27 -…
-
In Domo, YTD breaks when you use a month filter because filters remove prior months (history) before beast modes run. I'd try to use a variable - or handle it in Magic ETL using a month-year field and pre-calculating YTD by year and month.
-
It depends what you are converting…labels, or full sentences. I typically setup a variable for "language" where the values would be things like "EN" for English, "ES" for Spanish, etc. Most recently I use AI to do the translations to populate the look up table. key EN SV revenue Revenue Intäkter profit Profit Vinst date…
-
Congratulations Elliott! One of us! One of us! One of us!
-
I don't work with BigQuery, but there are documentation pages that show example queries. https://developers.google.com/analytics/bigquery/basic-queries https://developers.google.com/analytics/bigquery/advanced-queries The documentations shows that the specifics (ie. fields) are nested as you stated. The page for basic…
-
Both parts are valid. This is non-aggregated: DATE_FORMAT((CURRENT_DATE() - INTERVAL 1 DAY),'%a') This is aggregated: COUNT( CASE WHEN DATE(`Opened At`) = (CURRENT_DATE() - INTERVAL 1 DAY) THEN `Opened At` END ) The CASE produces row-level values, and COUNT aggregates them into a single result. So each works on its own,…
-
This is the only link I can find: https://community-forums.domo.com/main/discussion/69144/sendemail-function-via-api/p1 Here's a JavaScript example of a fetch call: async function invokeHelloWorld() { const url = "https://<yourDomoInstance>.domo.com/api/codeengine/v2/packages/abc123-def456/versions/1/functions/helloWorld";…
-
I believe the issue isn't the way the visuals are displayed, but the way you are creating the underlying value. Make sure your value is a real percentage in your ETL. In the table, it multiplies by 100 such that a raw value of 0.473 shows 47.30%. If the raw value is 47.30, it shows 4730% instead of the calculated percent.…
-
You have an aggregation with a non-aggregated formula. I think it's having a problem grouping. It can do the date_format by itself but not while trying to do the count. What happens if you wrap the data format with a MIN statement?
-
I don’t think you’re imagining it, but I haven’t been able to find any documentation confirming that this behavior changed. I could be missing something. From the outside it seems intentional rather than a bug, but I don’t know that for sure. Personally, I’d really like to see support for both global (persistent) variables…
-
I had nothing. Except tacos. Tacos are the answer to most things. But I'm not sure our members will click "Love this answer. Mark it awesome!" The poem — just the observation that a quiet forum isn’t necessarily an empty one.
-
Still water reflects the sky; sunshine gathers on the surface. 🌞
-
Grant answered one question so well it solved three others nearby. Congratulations.
-
When I create support tickets, I receive regular reassurance that nothing has happened.
-
https://www.domo.com/consumption-terms Domo credits are supposedly consumed based on the execution activities a Workflow performs — not specifically labeled by “workflow name.” According to Domo’s Consumption Supplemental Terms, Workflow-related credit consumption includes: Workflow start — a small upfront cost per start…
-
No, a SQL workflow cannot send emails. That's for transforming and writing data. To send emails, I would use Domo Workflows - which is an automation feature that supports things like sending emails, AI integration, etc. On the black ribbon bar at the top of this forum, there is a link that says Community Forums. Hover over…
-
Even when a dataset alert is triggered by multiple new rows, Domo may send a single email covering all triggered rows. I don't think there is a supported way to force one email per row (Order ID) using dataset alerts. If you need one email per order, the workflow would need to send the emails itself, looping once per Order…
-
Adding to what Jason has stated… Domo does not support deleting an individual row directly from an existing dataset, but you can effectively remove a bad row by republishing the dataset without it. A common approach is to use Python to read the current dataset via the Domo APIs, drop the offending row (for example,…
-
Yes. Instead of evaluating row-by-row, you would trick the alert at the order level. Then include the order line details in the alert payload or drill through. Quick theory - create a second card that aggregates at the order id with metrics count of lines, total order value, or any condition that would trigger the alert.
-
No, a Magic ETL does not retroactively reprocess existing data or partitions unless you explicitly re-run or rebuild them. Your connector is scheduled every 7 days and is partitioned by the date field, so each run only adds or replaces data for the dates included in that run. Existing partitions outside that window are not…
-
Btw…I concur with Andrea. I believe the issue was addressed. But somehow it has found its way back to me. Sounds like a movie intro. "It knows you're there. It won't go away. And coming back to you in 2026, …"
-
I sent you a video clip. If you'd like to see it first hand, I can jump on a call and give you control of the screen. The problem appears to be that the program is calculating the cursor position from the mouse click using the visible window coordinates, but it is not accounting properly for the vertical scroll offset of…
