Best Of
09/18 PRODUCT RELEASE SNEAK: Magic ETL Updates
We are excited to release these new updates to Magic ETL!
- Upsert Processing: Update rows in output datasets without reprocessing the full dataset, based on a unique row-level key. This replaces any of the remaining needs for recursive dataflows. This makes the pipeline pattern much more resilient and efficient due to an easy recovery process and no longer a need to reprocess data or perform complex comparison logic when updating an existing dataset.
- ‘Remove Duplicates’ Tile: Now includes “Add All Columns” and a corresponding “Remove All Columns” buttons that allows for easy adding or removing of columns in bulk.
- Increased Magic ETL Canvas Size: Build better, more organized DataFlows that are easier to document and easier to update. Perform all the operations necessary without having to arbitrarily split the flow into multiple flows due to the previous small canvas size.
- Magic ETL Mini Map: Provides a better navigation experience with a mini map in the bottom right corner to quickly and easily see the layout of the tiles.
Product sneak peaks are an exclusive perk for our Community members only 👏
Please note: these features are scheduled to release on September 18, but subject to change and could lead to a delay in its deployment for an unknown amount of time.
09/18 PRODUCT RELEASE SNEAK: Data Collection and Action App Building
We’re adding a few capabilities to Forms and App Studio which helps a low-code user easily create a powerful app that, for example, collects information, kicks off a workflow, and queues up an approval for a user who can act on what’s presented in the app.
- Question-specific Right Rail Drill: We’ve moved the more advanced form question settings into a question-specific right rail to enhance and simplify the interface and allow us to continue to add more functionality to forms.
- Cascading Filters: When configuring a form, now you can set up questions with cascading filters, so the previous question can filter subsequent questions.
- App Studio Queues Widget: We’ve brought queues directly into App Studio with a new widget. This integration between Queues and App Studio empowers the user’s ability to organize tasks efficiently, enhancing Workflow management and productivity. This integration allows for more customizability available inside a tailored and pre-designed app built in App Studio.
For example, imagine a customer who relies on accurate inventory data to maintain optimal stock levels across multiple store locations. If the stock for a particular item falls below a certain threshold, an alert is triggered to initiate a workflow. This workflow automatically generates a user task to approve a new purchase order, which then appears in a queue within their app. Store managers can access the app to review and approve any necessary purchase orders applicable to their store location, ensuring their inventory is promptly restocked. If approved, the workflow will automatically submit the purchase order to the vendor. With Domo, customers can visualize their data and take action in one centralized app, backed by an automated workflow.
Product sneak peaks are an exclusive perk for our Community members only 👏
Please note: these features are scheduled to release on September 18, but subject to change and could lead to a delay in its deployment for an unknown amount of time.
09/18 PRODUCT RELEASE SNEAK: Group Account Ownership
Historically, Account Ownership was tied to a single individual, making things like change management, or administration by groups next to impossible — which limits the ability to scale. Additionally, if that individual left the company, reclaiming those now-orphaned accounts was difficult and required workarounds in order to get data flowing again. The new Accounts Ownership model solves this by:
- Accounts can now be owned by Domo Groups.
- Accounts can now have multiple users or groups designated as owners.
- More granular sharing logic, allowing you to share accounts in a more limited fashion.
- Share with permissions as “Owner”, “Edit”, “Share”, and “Read Only”.
Groups of people can jointly and efficiently administer accounts, allowing them to scale their administration workload across more people, and have smoother handoffs of accounts between individuals.
Product sneak peaks are an exclusive perk for our Community members only 👏
Please note: these features are scheduled to release on September 18, but subject to change and could lead to a delay in its deployment for an unknown amount of time.
Re: Point ETL Output to Existing Dataset
if you connect with the cli tool
Then run list-dataflow -i 96 -f mydataflow.json
96 being the id of your data flow found in the url when viewing it in domo.
This will export the definition of the ETL into json.
In the json you should be able to see the output dataset definition.
You can then replace the dataSourceId with the Id of the dataset you want to output to. I would also set the dataSourceName to the name of the dataset as well.
Once done run set-dataflow-properties -i 96 -d mydataflow.json.
That should do it.
Heatmaps are some of my long time favorites....
So I have been meaning to post this for a while. And many here know I am very passionate about up leveling how we communicate new feature releases for Domo with our customers and our user community. While we have made huge strides, there are still some small things that sometimes sneak out without the formal release fanfare (which I was reminded of this again reviewing content for our upcoming customer release in 2 weeks!).
And well, heatmap cards have long been some of my favorite to use in Domo and we recently (or in the last couple months) added two cool setting for the Heatmap card type in Domo (note this is different than the Heatmap table type and is under Other or Popular Charts):
1) Add a total row and/or column (without having to pre calc a ton of things)
2) Set how many series you want to show (before if you used top X rows it would show 5 values not the first 5 set of data)See below for example showing the legacy view and then tabs showing the totals and Adding Top 5)
Screenshots attached and you can also go ahead and see how it works in this Domo App Studio App:
Have fun!
Re: Combine 2 data set (One to many)
Hi @Atieh can you please describe what your desired output might look like?
Some options I'm thinking about based on what you have typed:
Would you like to divide the spend across the multiple rows on table 1?
… or would you like to append the row from table 1 with a unique identifier so that you don't get inflated spend numbers? and if so, what would be the expected result of filtering on a date, say 7/21?
Alternatively, if you join those metrics and ended up with spend on every row, you could use beast modes to de-duplicate, check out the following beast mode that handles this:
MAX(`Spend`) OVER (PARTITION BY `Campaign`)
Note that if our values were $100, $110, $130 for the rows in c1, our beast mode would display $130.
Hopefully this is helpful!
Re: Case statement with fixed by
Sbhatia,
Domo provides a very good article on this topic:
Sample Beast Mode Calculations: Period-over-Period Transforms (domo.com)
Your formula will have to take the form of the following:
nmizzell
Re: How do I count the values in a column using beast mode?
Grant's solution will work if you want to count the total full time. If you want a percentage, the following extension of Grant's formula will work:
COUNT( CASE WHEN `Full-Time/Part-Time` = 'Full-Time' THEN 1 END)/ count(`Full-Time/Part-Time`)
nmizzell
Re: How do I count the values in a column using beast mode?
COUNT( CASE WHEN `Full-Time/Part-Time` = 'Full-Time' THEN 1 END)
This case statement will return a value if your column is full time and then count that many values













