ArborRose Coach

The best thing about Magic ETL is being able to trace logic step-by-step without digging through 500 lines of SQL. The second best thing about Magic ETL is how simple it is to maintain and hand off to someone else. My favorite thing about Magic ETL is that it makes me look way smarter than I actually am. It's basically…

It looks like you have at least one combination of AccountNum + Account + NewMonth + FY with multiple underlying records. Because Beast Mode is evaluated before aggregation, the pivot is encountering multiple results for the same cell. Try pre-aggregating the data in Magic ETL by grouping on AccountNum, Account, NewMonth,…

Bump - Beast Modes on variable default value. I've had to go through all cards that have a default date and set them to a new date because I can't do something as simple as set the default to January 1st of the current year: STR_TO_DATE(CONCAT(YEAR(CURDATE()), '-01-01'), '%Y-%m-%d') I don't want arounds and gimmicks. This…

That warning means Domo is finding more than one record for the same row/column combination in the pivot table, and it doesn’t know which value to display. The fix is to change the value field to an aggregation like SUM, AVG, or COUNT so Domo can combine those multiple records into a single result.

I was unaware Domo removed the functionality. I just went to "developer.domo.com" and I still see the create button at the bottom. And delete next to each. As far as I can see, they exist in both locations. I do have admin rights. Is that the difference in still seeing the create client id link?

This post looks related: https://community-forums.domo.com/main/discussion/68592/starting-a-workflow-from-a-domo-app

Interesting question. I’m not aware of Domo exposing theme colors to bricks. You could try to do it in reverse — define color or theme properties in the brick manifest and allow them to be configured per card instance. That way the same brick can be reused, with colors manually set to match each app or client’s theme.

When you publish or update an app, Domo reinitializes the app state, so in-app filter selections aren’t persisted and queues reset to their default state. One way to minimize the impact is to design queues with personalization (for example using USER() in Beast Modes or variables). This allows queues to auto-filter to the…

I may have misunderstood. Are you wanting to display a marker across the gauge?

The way Domo cards work, you can pre-select a value using a filter (you are already doing this). Users can clear this filter. There are many ways to implement behavior. You can also create beast mode to enforce a default such as CASE WHEN `Month End Date` IS NULL THEN '2026‑02‑28' ELSE `Month End Date` END Or use a dynamic…

You can show percent against target. Use the multi-value gauge instead of a filled gauge. It let's you display the actual value, the target, and the % to target.

No. Workbench has it's own version. It is a client-side Windows application that you install locally. As @ColemenWilson mentioned, Domo is a SaaS production. You don't install or manage versions yourself. Updates roll out continuously. You will not see anything like "Domo version X.x".

I have given @MarkSnodgrass comment thought. It's a better explanation than anything I can come up with. I was hunting the card to see where the dataset was in use before I delete the dataset. Many of my datasets are populated via Python. And sometimes, I remove the dataset from the Jupyter workspaces {or otherwise} to…

DATA_APP would be the app such as a Custom App, Brick, or App Studio app. The number looks like an internal id for that app in Domo. It's a unique number associated with a specific app. It looks like Domo found a dependency that your user does not have access to. You could try finding the app using the id. Such as…

I’m familiar with the abandoned warning, but this was an active dataset, just like others showing the same indicator. The only thing suggesting an issue was the AI readiness message. Once I defined a column as an identifier in the AI dictionary, the lineage appeared. It's not that I am completely against AI. But Domo isn't…

A true dropdown component is not supported in standard table cards. Those cards are intentionally limited to data display and navigation actions. If dropdown behavior is required within the card itself, a custom app (via the Domo App Framework) is an appropriate path, with writeback handled through Domo APIs. However, it’s…

I don't like this. My head hurts. 😵‍💫 If I'm wrong, I'm wrong. I barely understand the question. Using a sample dataset of: Month End Date,YTD_Amount,Month,Fiscal Year,FY End Date 2024-02-29,1000,Feb,2025,2025-01-31 2024-03-31,2200,Mar,2025,2025-01-31 2024-04-30,3500,Apr,2025,2025-01-31 2024-05-31,4800,May,2025,2025-01-31…

Here's a blank brick example. Go to AppStore, search blank brick. When you create a dashboard, you will fill in an area with JavaScript, html, and css. Here's code. JavaScript: var select = document.getElementById('animalSelect'); var output = document.getElementById('output'); select.addEventListener('change', function ()…

You could make a dropdown in an html card. Which would look just like a regular table card…but alas, how would you get the selected value to pass back to the Domo filters. You could create a custom app or use a brick.

… peanut butter with no jelly. 🥪 … a phone with no charger. 🔋 … a keyboard with no "S" key ⌨️ … Domo without the community forum. 😏

I don't work with that writeback connector. But I here are a few thing I would try. • Make sure all folders are already created. (Don't assume a connector can create folders.) • Keep naming simple. Use snakecase with underscore_instead_of_spaces. Avoid special characters. • Use the main site, not a subfolder. At least to…

Take a look at the Governance Connector. https://domo-support.domo.com/s/article/360056318074 It has a beast modes dataset the includes: Fields: Card ID, Card Title, Dataset ID, Dataset Name, Beast Mode ID, Beast Mode Name, Beast Mode Formula, Beast Mode Status, Beast Mode Saved to Dataset, Beast Mode Applied to Summary…

I don't think there's a "one click solution". But you could probably migrate content using Domo Sandbox. Enable sandbox in the source instance. Then invite the destination instance to the sandbox and create a repository of objects. Then share and promote to the destination instance.

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.