Best Of
Re: MTD, MTD Last Year Beastmodes do not work properly with Date filter
You're right, in hindsight it does seem redundant! I guess I was thinking by minimizing the rows by filtering would ensure that you'd get the correct results. However, now especially because you want to add YTD on the same card it seems like you can handle it all without any special filtering.
Re: Changing Column Names for App Studio Forms
You can change the name of the column by going to Admin-Governance-Toolkit and select your dataset to edit as shown below. you should be able to change the name of the column here.
Re: Bucketing different text fields if there is a match
An easy way to get accurate counts of this is to break up your lists into individual items, with each item in its own row. You can do this dynamically in Magic ETL using this process:
Re: How do you change the value format of an Alert?
The card probably isn't the value going to the alert. That would be the field in the dataset. If you set a field up to represent percentage in the dataset, it should show up as a percentage in the alert. You might even have to do it as a string representation in the dataset.
Re: Page filter add contains + allows "ORs"
Leaving another comment to highlight the need for the above. Thanks!
Re: Page filter add contains + allows "ORs"
We need 'Contains' so badly! None of the workarounds work for the use cases I encounter the most.
Re: Income Statement: How do I join 'Chart of Account' table & 'GL Records' correctly
I see. So some branches and months may not exist and the join won't create rows for missing combinations. Sounds like you need a way to make sure the combinations have all relevant GL accounts, if if they don't exist in the GL Records.
You could handle this by creating a master dataset. Complete with all possible branch, month, and GL account combinations: Branch, Month, Year, GL Account. You could do this by joining a table containing all branches, a date table with years and months, and you chart of account table….which contains all the GL accounts.
After you have a dataset with all possible combinations of branch, month, year, and GL account, perform a Left Join or Right Join (depending on how you set it up) with your actual GL Records table. If a record does not exist, the Amount will be NULL. Handle that as described previously.
Re: Is it possible to duplicate an entire dashboard and all cards on it?
You can, on the dashboard there's a wrench icon in the upper right. Select Save As and it'll ask if you want to duplicate the cards or not.
Re: Does domo allow a dataflow to run for more than 24 hours
You only have 323k rows, so there are likely some chances for efficiency improvement. When I'm designing an ETL, I like to be a teapot—short and stout.
Short—Filter your data as soon as possible to reduce the number of rows. Use a select column or alter column to select or drop columns, respectively, so you're left with just the columns you need. This should also take into account your joins so that you don't accidentally do a giant cartesian join and exponentially increase the size of your datasets with your join.
Stout—Do many things at once. If possible, do several joins at the same time instead of chaining joins together. Don't just have a single flow of your data.
With that, you can also look at the execution history of the dataflow, click the success icon, and it'll show you the execution flow and path to give you a better understanding of which part of your pipeline is taking the longest to identify potential areas for efficiency gains.