Best Of
Drilldown stopped working on Beast Mode field with HTML (previously worked)
I have a table card where one of the columns is a Beast Mode calculation that outputs HTML (using concat( '<div title=' ,`Internal ID` ,'>',Job Number,'</div>')
Previously, this field worked as both:
- a formatted HTML display column to just show the Job Number, and
- the trigger for a drill path to a specific Internal ID (because just drilling down by the Job Number itself would bring more records than desired - I want to be able to drill down to a specific ID that the row in my table corresponds to. I do NOT want to display that ID in the table as it doesn't mean anything to the user.
Without any intentional changes to the Beast Mode or drill configuration, the drilldown has stopped working when clicking this column.
Current behavior:
- The HTML renders correctly in the table (doesn't show the <div> in the table, just the Job Number that I wanted to display)
- Clicking the cell no longer drills down how it used to - it just shows No Records.
What I’ve checked:
- Drill path is still configured correctly
- Dataset and fields have not changed
- Other (non-HTML) fields still drill as expected
Question:
Has there been a change in how Domo handles click interactions on HTML-rendered Beast Mode fields?
Is it no longer supported to use the same Beast Mode column for both HTML display and drill interaction?
Attach a PDF to an Email
I created a custom function to create a PDF file based on some text being passed to it from an AI agent output. The create file function works correctly (returns a file id) but when I go to attach to an email, I receive a "null" attachment, not the file name or format I was expecting.
Any suggestions?
Filter Section
When I have too many filter cards on an App Studio say 10, it can look very busy.
I would suggest to have an expandable section/button that store all the 10 filter cards I have in there.
Filter behavior on dashboard/app vs Details View
I wish the default behavior for filtering via-the-legend at the dashboard/app level would mimic what happens when viewing a card in full screen/via the details view.
When I click a colored block in a legend, I'm intending to remove that color from my view and allow the chart to re-scale. I think it's confusing that this behavior isn't consistent for a given piece of content when it's viewed on its own vs as part of a layout.
A few images to illustrate:
- Card Details View, you can see I have 2 colors stacked and the chart engine has scaled me to 6k
2. Card Details View - I have removed the purple color via clicking the legend, and my scale has adjusted to 2.5k
3. The same card is placed on an App dashboard, and when I click the same purple box the card maintains its scale and simply grays out the purple section.
4. The same behavior as above - but shown on a card with many more series items:
Yes, I can get the filter activity I need by using page filters or filter cards, but I think it's valid to consider that filtering via-the-legend should behave the same way no matter what kind of screen the user is looking at, especially if it's the exact came card.
If Domo wants to consider making the two behaviors toggle-able, I would love to see the behavior shown in image #2 be the DEFAULT for all.
Pretty-print Error on Android
I've created 3 different apps using App Catalyst. The apps work on desktops and the Domo mobile app when viewing on iOS. However, when trying to use Android devices, it throws a "Pretty-Print status 403" error every time. I tried using VAR at the top level and an IIFE wrapper. Neither of those is working exclusively or independently.
Jessary
Workflow Notifications
I have just finished creating and deploying my first workflow. It's doing what I need it to do. I'm struggling to figure out how to consistently get workflow completion notifications to who I need to get them.
I am one of several admins. We are all in the "Domo Admin" group. I have given the group Admin access to the workflow. The only notification settings I can find for workflows are personal settings (annoying but I can tell others to set them up). But none of the settings will work. It is being started by and alert so the "you started" options won't work. And the "you own" options don't seem to work because there is no "owner". Only creator and contributor set as me and unchangeable.
So next path, setting up and email task in the workflow. Well after digging through a bunch of functions I landed on the Workflow Executions function. Technically I could get everything I needed, but if the workflow fails the Email task would never get triggered. Meaning I would only get the emails on success, not failure.
Pivot again. Found the DomoStats: Workflows dataset. Ok cool. I can just setup and alert for when a new row is added. I can even split things. Completion/Success just to me. Failures to the entire group. Cool. Except I only can run once a day (this is fine for normal days). I need it to update anytime the workflow runs. So add a task to run the dataset. Cool, except once again, if the workflow fails, it just stops. Meaning no trigger for failed workflow except to me.
If this workflow fails I need to know asap so the tasks can be manually triggered. I'm about to leave the country for 11 days. I need other people to be able to get alerts. Is my only option to set up a rule in Outlook to forward any failures?
Ability to Cancel or Stop Publication Refresh Jobs
Currently, when triggering a publication refresh in Domo, the process must run to completion once started. There is no option to pause, cancel, or abort an in-progress refresh job.
According to Domo documentation, users can initiate and monitor publication refreshes, but there is no control to stop a job once it has started.
This creates challenges in real-world scenarios where:
- Refresh jobs can take a long time depending on the number of datasets, dashboards, and subscribers.
- A refresh may be triggered accidentally or at an inconvenient time.
- Issues are identified mid-refresh (e.g., incorrect content, missing datasets, or configuration errors).
- Users want to avoid unnecessary processing or system load.
Proposed Enhancement
Introduce the ability to:
- Cancel or abort an ongoing publication refresh
- Optionally pause and resume refresh jobs
- Provide clear status feedback when a job is stopped
Business Impact
This enhancement would:
- Improve operational control and flexibility
- Reduce unnecessary compute/resource usage
- Prevent propagation of incorrect or incomplete content to subscriber instances
- Enhance user experience when managing large or complex publications
Tag dataflows automatically based on tags of output dataset?
Is it possibly to tag the dataflows automatically with the tags added to the output dataset? So basically whenever adding tags to a dataset, the dataflow that spits out that output you are tagging should be default also get the tags.
Currently when creating a new dataflow, I navigate to the output dataset to tag it with a business unit or source type, etc. But then afterwards always have to remind myself to navigate back to the dataflow to tag it manually again.






