Best Of
FORUM FRENZY DAY -- answers from Domo employees
Hello Community!
Today is our Forum Frenzy day. We've recruited members of Domo's consultant, technical support, and education teams to be in the Forum to answer questions in real time.
If you usually answer questions, today is a day to kick back and take a break. Hopefully you have some questions you can bring to our Domo team.
Let's flood the forum with questions today 🎉
Re: New to Data Analytics - Loving Visualizations, Problem Solving, and Data Empowerment
Welcome to the Domo Community!
Re: Workaround to Pivot tables pushing non-valued categories to the bottom.
Maybe, I'm mis-reading the post, but I see the sorting issue when there are missing attributes in the source file: For example, there is no record with "a" and "1" attribute values.
So, happy path is that the source file has a record for all attribute combinations, like this:
With this file, I have no problem sorting ascending or descending and keeping the serial order of the two attributes:
Unhappy path is when the source file is missing attribute combinations when there is no count:
With this file, I am not able to guarantee the serial order of the two attributes
The work around I use is to generate 0-count records for all combinations in a dataflow, but that feels like make-work. Surely there must be a way to force the sort order when the source file is missing records with attribute values.
Rob_E
Re: How can I get additional Groups in this Pivot Table?
Thank you for the additional context, @Barb. Here's what I recommend doing for the time being:
- Move your 'Actual v. Forecast' and ROAS calculations into the ETL
- Have two separate output datasets in the ETL: One that contains the current output dataset you are using to power all of those cards without any changes made to it, and a separate output dataset that includes the calculations
- Replace the dataset in the pivot table card with the new output dataset you just created
By doing this, you can build your ETL in such a way where you are able to incorporate the grouping logic in the dataflow without disrupting your existing visualizations.
Re: How to use Line + Stacked Bar Chart
to the original poster / @MichelleH and @Ashleigh , the design of the dataset was flawed which is why the user struggled to solve their problem.
"Operational Places" is grouped by "ACPR Name" and "Organisation Type". "Number of Clients" is grouped only by "ACPR Name" in a different ETL, hence why the numbers are the same for each ACPR throughout."
the big walk away is to try to avoid having columns that are non-additive or semi-additive. (a fully additive column means you could take the whole column, sum it up and get 'the right answer'. in this case, b'c 'number of clients' was duplicated across rows, the column is only semi-additive. (it's the same as if you had a dataset that had one row per month and the balance of the AR account. the balance column is not additive, b/c you cannot sum all balances across all months and get the right answer. in that kind of data structure you'd always want 'the most recent balance.' and that's way more difficult to do in ANY visualization platform.
SOLUTION: split the metrics into a set of rows for "number of clients" and a set of rows for "count of location"
from there it's just a matter of putting ACPR on the X-axis, Organization Type on the Y-axis. and then your metrics on the series.
Re: Pie Chart does not showing full data when Legend has the Bottom Portrait view Legend position
Can you provide a bit more context about what is the question here?
I am seeing different results depending on screen size and options selected.
Re: Budget to Actual - Multiple Dimensions & Different Datasets
Append!
Use Magic ETL to:
1. Match column names and data types where appropriate (like date)
2. Get both datasets in the same granularity with same aggregation
3. Remove unneeded columns
4. Append the data together rather than join.
Re: Identify Column vs Row PDP policies
@ColemenWilson - great idea! They even already have an appropriate icon they could add on that's currently an option in App Studio. Something like this for columns…
or this one for rows…
Re: What is difference between Form viewer, Form builder, Form & Dataset brick and App studio forms
Form Builder and Form Viewer are custom apps that provide a system to create and submit forms. Builder can build and submit while Viewer is submit only from the forms built in builder. These use AppDB collections that sync to DataSets. These are considered legacy applications however and the plan is to replace them with Forms in Domo.
Forms in Domo can be used in App Studio and Workflows currently and is where we are actively developing and adding new features. These Forms write directly to DataSets.
The Form & Dataset Brick is a custom app that is meant to be an example of how you would make an app that writes to AppDB that happens to be using a simple form as the submit mechanism. It's meant to be a starting point for AppDB based apps where you can make your own customized form or other app. It can also sync to a DataSet but the current example app doesn't use DataSets. We are working on converting Bricks into templates in the Pro Code Editor which is currently in beta.
Re: STR_TO_DATE throwing Parsing error in ETL
%M is for full-month name "June".
Try %b for three-letter abbreviated month name.
That's as far as I got in checking, but I would double check the rest of your codes, too:
