ArborRose Coach

The problem appears to be with the character set interpretation. The CSV UTF-8 is a universal standard for encoding text. Especially special characters such as non-English. If Excel saves using default csv, it is limited in the characters it supports and may truncate or skip sections. But 17% data loss sounds extreme. I…

You can use Domo’s Magic ETL to simulate recursion if your hierarchy isn't too deep or large. Filter rows where ManagerID IS NULL (top-level). Join the result to the hierarchy where ManagerID = EmployeeID. Repeat the above as multiple steps (one per level).Append each level's result together. You’ll be limited by the…

I'm going to venture a guess and say you expecting too much from the SQL tile. When it was introduced to us, we were told it would have limits. Having the SQL tile reference itself isn't something I'd expect it to do.

A bit difficult to visualize without an anonymized data example. I'm thinking there's an issue with NULL.

What about using FIXED? Something like SUM(`served`) FIXED (BY `Physical County`, `CABINET`) / NULLIF(SUM(`passed`) FIXED (BY `Physical County`, `CABINET`), 0) * 100

Your code looks like its sending JSON as a string rather than sending as JSON. This might work once, but then fail if it can't be properly parsed as JSON. This const appDBQuery = `{ "content.ac_page_id": { "$eq": ${pageID} } }`; appears to create a string. Try it as const appDBQuery = { "content.ac_page_id": { "$eq":…

Have you tried using a generic Domo JSON Connector?

Can you just put Physical County and Cabinet on a card and then add a formula (beast mode) as (SUM(`served`) / SUM(`passed`)) * 100 Your group by is in essence the Physical County, Cabinet.

I believe the total row at the bottom will give the same aggregation as you have above. You could create two versions of the column, a second one for sum. Pivot tables would give more flexibility for creating custom aggregations.

This link may be helpful:

It can be difficult to work with large datasets across systems. In SQL, I prefer using OPENQUERY to run the process on the remote server and return just the result. Similarly, Dataset Views and Magic ETL in Domo pull in full datasets before doing joins, which isn't ideal for massive tables. Limiting fields helps, but not…

It's working now, thanks. It just hung there doing nothing. With any connector. I called a co-worker on a different network and had them try…they got the same thing.

I don't think you would ever want workflows to override permissions or set a role if the user didn't already have permissions. You could try to setup an indirect workflow that triggers or "listens" for updates to a dataset. Have the user fill out a form or submit whatever….and have that trigger the admin owned workflow.

Ah. I have used a custom brick to do this inside the app. Anyone else know another way?

A domo webform acts as a user-editable table. The data values are a dataset which can be incorporated into a Magic ETL, etc. Go to Data > Upload Spreadsheet….and look to the bottom right where it says Create Webform.

It sounds like the datetime is being treated as a numeric values such as seconds, which Domo must be interpreting as float. In your Magic ETL, try isolating the field using select columns and a formula tile with FROM_UNIXTIME. I believe the format is FROM_UNIXTIME(`your_float_column`) Or you could try formatting the time…

Even if I used the formula as you showed it, it should have worked. Are your fields numeric? Example above would give the same output I showed in my formula screenshot.

Using: Year,Season,VendorName,QtyMarketingForecast,DeliveredMarginDefine 2025,Spring,Vendor1,580,-68.23 2025,Spring,Vendor2,276,2548.93 2025,Summer,Vendor3,142,1050.75 2025,Fall,Vendor4,833,763.5 2025,Winter,Vendor5,902,-400

There's also an API for audit. I tried using Python to connect but received an unauthorized response from the API. I'm checking with our rep to see if it needs to be exposed for use.

I did not see it but I'm not very familiar with it. Which is why I asked it as a question. I saw a web reference that said it might be there, but may need to be requested. I'm assuming you need to automate something vs export it to a csv.

Yes, that's what I was thinking. Maybe its something Domo has to turn on for your instance?

Is it available in the Domo Governance Connector?

Sample data Item,Category,Cost Widget A,Electronics,1200 Widget B,Electronics,1450 Widget C,Furniture,980 Widget D,Furniture,860 Widget E,Office Supplies,430 Widget F,Office Supplies,390 Widget G,Tools,1500 Widget H,Tools,1330 Widget I,Tools,1420 When I do this as a bubble chart And then I expand it and filter it I do see…

I think that is the expected behavior - by design. What about adding a dynamic summary as it's own card? Create a separate card using the same dataset and filters. And it will change with the selections.

Great. Do they have a better explanation of what "fixed" means in the following? Bug Fixes Fixed how Workbench writes Database null values to Domo.

forecast_date run_date forecast_value 2025-07-15 2025-06-03 $45.00 2025-07-15 2025-05-27 $43.50 Month Category (which month) CASE WHEN MONTH(`forecast_date`) = MONTH(DATE_SUB(CURRENT_DATE(), INTERVAL 1 MONTH)) AND YEAR(`forecast_date`) = YEAR(DATE_SUB(CURRENT_DATE(), INTERVAL 1 MONTH)) THEN 'Prior Month' WHEN…

lol…sorry about mixing the avg headcount in the months. Obviously, I was straight typing off sample data.

I think that depends upon whether you use aggregates in your columns. Month,Dept 1,Dept 2,Dept 3,Dept 4,Dept 5,Total November,132.0,251.0,59.0,477.0,70.0,989.0 December,127.0,250.0,57.0,366.0,68.0,868.0 January,123.0,235.0,53.0,391.0,68.0,870.0 February,128.0,233.0,58.0,311.0,69.0,799.0…

This is the only document URL I see for Workbench 5.2. And it's just an overview. I suggest you reach out to Domo support. I don't see anything in settings that would affect it. https://domo-support.domo.com/s/article/000005138?language=en_US

Some of the information you are looking for is probably in DomoStats: DataFlow History, Dataset History, or Scheduled Reports. But I don't think there's a DomoStats that logs workflow executions. Yes, you could have the workflow log its own execution status to a dataset…self-logging. Do an append row to dataset with a…