GrantSmith Coach

You can aggregate your Occurrences in the analyzer by selecting SUM from the aggregate option when you select the column.

Not within Magic ETL however, you could possibly utilize MySQL dataflow to query all of the columns in the table via the information_schema, sort them alphabetically and then build your select clause to then select those columns in your dataset.

Currently, there isn't a simple way to do this within the UI. You can utilize the Java CLI to export the dataflow definition using the list-dataflow and save it to a file. Then change the output dataset ID to your web form's ID in the file. You can then use the set-dataflow-properties command with the -d flag to update the…

You can't conditionally show or hide different filtering options. If you're looking to restrict the records returned for specific users you can look into PDP to automatically do filtering so they won't be able to see other records.

It's grouping based on all non-aggregated fields. Because you're not aggregating the NumberDelivered field it's including it in the grouping. If you aggregate it with Sum it should remove the duplicate SendDate fields and aggregate it for the entire month.

Views like federated data sets are refreshed when they are accessed. They are not like a regular date of the days that which would update based on a time or other DataSet updating. This means that they only get updated when the data is requested as in when viewing a card built off of these data sets, you can’t create a…

You can use three different beast modes to handle this: Combined: AVG(`Handle Time`) Inbound 1: AVG(CASE WHEN `Call Type` = 'Inbound 1' THEN `Handle Time` END) Inbound 2: AVG(CASE WHEN `Call Type` = 'Inbound 2' THEN `Handle Time` END) You can then graph all of those on the same chart.

Have you looked into the premium Sandbox product that Domo offers? This may help with your ability to track and deploy versions. https://domo-support.domo.com/s/article/4403367344023?language=en_US

@AdamC Will you have multiple records with the same ID or is it just one record per ID and you want to check the latest date based on multiple columns for the one record?

Typically when you're getting an Infinity error it means you're dividing by 0. Have you tried wrapping your formula in a CASE statement to check against having a 0 denominator and then return a 0 or some other default value?

You could do something like: CONCAT(HOUR(`Timestamp`), ':', FLOOR(MINUTE(`Timestamp`)/30)*30) Minute will return the number of minutes in the timestamp (0-59) /30 will return a number between 0 and < 2 FLOOR will convert your fraction to 0 or 1. *30 will convert the interval to either 0 or 30. This will then give you your…

Hi @user046467 You'll likely need to add a third-party IdP to enable MFA. Here's the documentation on it: https://domohelp.zendesk.com/hc/en-us/articles/360043428233-Domo-Mobile-Security

Have you used a try/catch block to trap the error?

Take the output from the last formula tile and feed that into a group by tile. Then feed the output of that and the same formula tile to a Join tile and do the inner join. Then take the output of the join and feed it to your output dataset.

You'll need to utilize a Magic ETL for this. You can take the dataset as your input. Then feed it to a Select Column Tile. You can then select the Supervisor Name and the Email columns where you rename the Email Column to 'Supervisor Email'. Then feed your original dataset into a Join tile where you will left join your…

Take a Group By tile to group by the ID and Status Fields, take the MAX of your UPDATED field then inner join your data back into your original dataset based on the ID, Status Fields, and where the UPDATE fields match. This will remove any records where it's not the last updated value.

Hi @brandon_johnson@Brendon I'd recommend using a new date dimension dataset to solve a few of your problems. First, you can mark which fields are considered working days within your dimension dataset which would allow you to then include or exclude non-working days within your calculations. Second, it simplifies your…

This appears to be a change that Domo must have done in the back end to display US Dollars as US$ for users outside the United States instead of just $.

Ah, you can't use it within a formula tile. That's just the format for a beast mode. If you're looking to use Magic ETL take your data and feed it into a Group By tile. Group based on the loan_id and COUNT the loan_id to get the total number of records then join that back to your original dataset based on the loan_id. That…

SUM(SUM(1)) OVER (PARTITION BY `loan_id`) This window function beast mode will count the total number of records seen with the same loan_id value. You can compare it to see if it's greater than one to determine if it has a co-borrower.

Hi @Louie you can refer to my answer in your other post: https://dojo.domo.com/main/discussion/57293/adding-1-year-to-a-date-and-returning-the-new-year#latest

In that case, you can offset your data by one month to get the correct quarter. Try something like this. CONCAT(YEAR(`hireDate` - INTERVAL 1 MONTH) + 1, '-Q', QUARTER(`hireDate` - INTERVAL 1 MONTH))

What about dates that come in January / Month 1? Or dates that happen in other quarters? Should those be returning Q1 or their respective quarter?

You can utilize a LAG window function to get the prior month's value: LAG(SUM(CASE WHEN `jobtype` LIKE '%service repair part%' AND MONTH(`completedondate`) = MONTH(DATE_SUB(CURRENT_DATE(), interval 1 month)) THEN 1 ELSE 0 END)) OVER (ORDER BY `Month As Date`)

You'll need to do the first part within an ETL as you're needing to do a window function on a window function which isn't possible within a single beast mode.

You can't just do this with the way your data is currently structured. Domo required each month to have a record for it to be displayed. You'll need to feed your data into an ETL and have a record for each month with the monthly amount. First use the formula above in an Add Formula tile to calculate the amount per month.…

You can't use 30 different passwords to encrypt the data unless you have 30 different datasets which I highly recommend against as that's quite a bit of management overhead. Typically using a password manager where you can grant or revoke access to the different accounts / passwords is good practice so you don't have…

What is the locale of this user? Are they in the US or are they outside of the US?

Currently this granularity of displaying a label for just those datapoints isn't an option. I'd recommend adding this as an idea to the idea exchange to see if Domo can add this enhancement in the future.

The following beast mode / formula would get you the number of hours per month of work that would need to be done `Total hours` / PERIOD_DIFF(DATE_FORMAT(`end date`, '%Y%m'), DATE_FORMAT(`start date`, '%Y%m'))