ArborRose Coach

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…

Subject regex should be written such that it matches every incoming email. If all rows are disappearing, it suggests the regex does not match the subject. Thus, Domo rejects the email entirely. An expression such as .*Version.* tells the connector you want all emails where subject contains the word "Version". A regular…

The email regex can match structural patterns to allow or deny loading. But apparently it cannot extract regex groups to add them to dataset fields. Thus, you can't get the version number from the email subject as a data field. But you should be able to put the version number inside the file itself as a column, or put the…

Two points for Gryffindor! Sorry, I missed that last message. Glad you got things working.

Yes, it sounds like another aggregation issue. If you did someting like Actual - Budget, it can calculate because its mixing aggregate fields within a non-aggregate expression. As opposed to SUM(Actual) - SUM(Budget), in the same aggregation used i the pivot. If both are already aggregates then {backtick}Actual{backtick} -…

When you pivot in Domo, the pivot expects the incoming dataset to already be defined with the fields you want to pivot on. If you include extra fields, the pivot will collapse those rows and cause things to dissapear. The "Group By" forces the dataset to the right fields before you pivot. You are aggregating (SUM, COUNT,…

Yes, it’s possible to combine multiple datasets into a single one. There may be more efficient or elegant approaches than the one I use (and I’m always open to learning from others), but my approach relies on Python and the Domo API. I’m happy to walk you through it if you haven’t worked with Python in Domo before. {Edit:…

As @ellibot stated, you don't need a date column to rank. You just need a column to order by. RANK() OVER (ORDER BY Value 1 DESC) If you want something like top five: CASE WHEN RANK() OVER (ORDER BY `Value 1` DESC) <= 5 THEN 'Top 5' ELSE 'Other' END In an ETL use a Rank & Window tile, partition by your group (such as…

I think you need to define only the grain you want after the pivot. If you want Dept + Month > Actual vs Budget to get Variance then you group by only dept and month. Everything else would be removed or aggregated before the pivot. You may need to group by before the pivot. All the fields except your Actual/Budget.…

Your users’ concerns about Domo being “too complicated” aren’t really a platform issue—it’s a consumption issue. It comes down to how people receive and interact with data. When you’re working with large datasets and shared aggregations, spreadsheets just aren’t the right long-term tool, even if they feel familiar. Domo’s…

I have a continual problem with Domo Workbench de-authorizing. Over the course of this full year it's happened to me more than once per month. So, I'm not pleased with Workbench. @GrantSmith - Have you used Workbench Enterprise yourself?

Domo Private Embed requires the viewer to authenticate into your Domo instance. Through the single SSO provider configured for your Domo tenant Through a native Domo username/password account There is no separate authentication flow for Private Embed, and Domo does not support multiple SSO providers per tenant. Because of…

Sounds like maybe something is corrupt. Have you tried removing and recreating the tabs or the layout? There may be something wrong (corrupt) in the code interpretation of the tabs when they were created such as duplicating pages that already have tabs, renaming or moving, undo/redo kinds of things.

401 is an authentication error. Which I interpret as - the workflow is executing, but when it tries to call the web crawler, the external service is rejecting the request because it’s not properly authenticated. Domo is not authorizing it.

@GrantStowell - I believe this post is in the wrong area. It's a feature request. Can you move it to the proper area such as product ideas.