GrantSmith Coach

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'))

I'd utilize the LAST_DAY function on the dates to return the last day of the month and then filter out the date dimension table to only have those specific records. Then you can use LAST_DAY for your dates as well when you're comparing against the dates.

Currently there isn't an option that would allow you to change the font size of the legend. I'd recommend adding an idea to the idea exchange to see if Domo can add it to the product.

Have you tried using a COALESCE and filtering on the default value? COALESCE(`field`, 'Empty')

Add a constant to your dataset and call it grouping column and set it to 1. Then feed that into a group by tile and group based on the grouping column. Select the MAX of the _BATCH_LAST_RUN_ field. Then use an inner join to group that result back to the original dataset where the two dates match.

What does your query and python code look like? It's easier to help debug if we have an example.

Interesting workaround. Thanks for sharing!

I’d log a ticket with Domo support to look into their connector as it should be expecting json and not xml

You’ll need to probably start over as it’s expecting cards that no longer exist

This sounds like an internal platform issue. I’d recommend logging a ticket with support for them to look into the issue on their end

You can utilize a beast mode and subtract the two: COUNT(CASE WHEN `Type` = 'List' THEN `Date` END) - COUNT(CASE WHEN `Type` = 'Completed' THEN `Date` END) Then also have a beast mode for the completed count: COUNT(CASE WHEN `Type` = 'Completed' THEN `Date` END) Use these two beast modes in your pie chart instead.

Hi @Puja_Tayade Domo Knowledge Base has some good articles on creating alerts for datasets and cards: DataSet Alerts: https://domo-support.domo.com/s/article/360042925994?language=en_US Card Alerts: https://domo-support.domo.com/s/article/360043430513?language=en_US

Hi @Natalia , This currently isn't an option but I'd suggest adding it to the Ideas exchange for a potential future enhancement.

According to their documentation Net Sales is Gross - Discounts - Returns + Taxes + Shipping so you should be able to back into Gross sales with: Gross = total_price + total_discounts + returns - total_tax - total_shipping_price_set_presentment_money_amount Refunds/Returns isn't included in the All Orders report in the…

Have you tried updating the dataset's schema before you upload the new dataset? https://github.com/domoinc/domo-python-sdk/blob/master/examples/dataset.py#L32

Currently this isn't possible within the pivot table. You'd have to do this within an ETL to process your data.

It should allow multiple columns with a comma. Is your code using back ticks ` or actual forward ticks´ and it's just a copy and paste issue? The documentation clearly outlines multiple columns are allowed: https://domo-support.domo.com/s/article/4408174643607?language=en_US