Comments
-
You might try to pre-aggregate or see if you can reduce the level of detail used in the denominator. Instead of day, try month for example.
-
It seems to be pushing your data to datetime rather than just date. You could try to force just a date with DATE() or DATE_FORMAT(Date, '%Y-%m-%d') maybe?
-
The filters are going to affect both numerator and denominator. Your denominator will need to ignore filters. You can do most of that with FIXED. But you may not get every scenario. SUM(`Sales`) / SUM(SUM(`Sales`)) FIXED (BY `Date`,`Retail_Category`) You said ALL SALES should only depend on: Date Range Retail Category If…
-
What chart type are you using?
-
I don't think you can remove the card link using that action from the Workflow. Instead of sending a card report to people, you could send an email with a CSV attachment generated inside the workflow. The attachment would be a snapshot in time and won't change later. No Domo branding or link back to Domo.
-
One of us! One of us! One of us!
-
Congratulations @JasonAltenburg. Ten years, holy cow! I'm such as newbie. I'm sure we all look forward to meeting @tjoyarz at Domopalooza. I wish him the best of luck in rounding up that 40% of us into some corner for greetings and a group photo.
-
If you're using a map type that is based on provinces, then you’ll need to assign ECOM to a valid province value — otherwise you’ll have to switch to a different map type. In the example I shared, the formula substitutes Yukon because it behaves just like a regular province in the map. It’s also a good choice since it has…
-
You could just pick an open province and create a beast mode to label that with your ECOM value. The others would plot where they belong CASE WHEN `Province Code` = 'ECOM' THEN 'YT' ELSE `Province Code` END Another way to do it - instead of provide code for the map, use latitude and longitude and include ECOM. Store_ID…
-
I'm having trouble understanding the question(s) asked. The YouTube documentation shows that the supported way to embed a video in a webpage/app using an iframe uses the URL format as https://www.youtube.com/embed/VIDEO_ID https://developers.google.com/youtube/player_parameters Some standard URLS, won't render in iframes…
-
Yes, your statement looks correct. "Controls cannot be removed from the card unless the variable logic is first removed from the Y-axis, series or sorting configuration.” Removing the variable from the card solves the visibility issue but also removes the dynamic behavior you wish to keep. If the goal is to keep the…
-
You should be able to do it with a Magic ETL. Use a Group By to get one row per month. Create a sequential month index using a Rank and Window tile. Partition if needed, ordering by Month ascending. As a row number, call it something like month_rank. Add another branch duplicating it as month_rank_2. Use a join tile and…
-
I concur with Grant. The token generated from settings > admin > access tokens is not the correct token type for the API. The datasets API needs an OAuth token generated via a client id and client secret key. Look under admin > authentication > API clients.
-
My understanding is that in MySQL dataflows, the Explain SQL is only available in some SQL types (like Redshift). As for performance issues….it's always useful to filter the data up front to put less stress on the SQL engine. But some things like joining on CAST values are a performance killers. ON CAST(c.id AS SIGNED) =…
-
If someone unsubscribes from a Domo email campaign using the unsubscribe link, how can they subscribe again and start receiving campaign emails? I don't use the campaigns app, but I can see the documentation page. You should be able to manually remove them from the unsubscribed list and then re-add them. But that doesn't…
-
If your client is external, a scalable approach is to use Domo Everywhere with row‑level security. Create a single dashboard, apply RLS so each client only sees their own data, and then embed it in your portal using SSO embedding. This would give you data isolation and avoid managing external Domo accounts.
-
I can think of a couple possible things that might cause an issue. Use named fields. Do not use an asterisk in a SELECT statement. Try UNION ALL rather than just UNION. Union removes duplicate rows, while UNION ALL includes all rows. Make sure your fields are consistent with aliases and types. Try your view out with just a…
-
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…
