ArborRose Coach

Good job DataMaven. Congratulations and thank you.

SEC_TO_TIME should be converting duration in seconds to a time format. It looks like the value is for the average session duration displayed with K, indicating thousands. As in average session duration of 170.85 seconds. The "0" indicates no change from the average in the current month to the same month last year. Your…

Hmm….sorry my workload is heavy today. As DataMaven mentioned…I'm not sure what I'm looking at with your fields in x and y. As for the %…there might be an issue in how your calculate the percentage of the total. You can try to calculate the % of a column total separately for each plan and combine them. Something like this…

Eat an elephant one bite at a time. Based on your description, it sounds like you are trying to create a dataset of all possibilities….every combination. I would try some kind of user interaction. For example, create a dashboard where users select their starting location from a dropdown filter. Then, based on their…

Try this: (1 / ((spend / revenue) / (sum(spend) / sum(revenue)))) * (2 / MAX(bid_multiplier))

I think the approach you mention is going to give to many records. You could try creating a separate table with unique combinations of routes with start and end points. Then create a filter with logic based on the last selection made. There's a searchable filter app in Domo but I've never used it.…

Your numerator appears to be totaling the billable orders by country. Over the total of attempted transactions and voucher transactions by country. The use of "FIXED" seems redundant. What happens if you simply to something like SUM(BILLABLE_ORDERS)/SUM(ATTEMPTED_TXNS + VOUCHER_TXNS)?

A few possibilities… • You may need to use the WHERE clause to select only customers with rank less then equal to 10. • Make sure your data doesn't have any issues or missing values that could cause an error. • Verify your sum(NET_SALES_CY) aggregation is functioning as expected.

And something that has driven me nuts….color and borders. Add the following to CSS. table { border-collapse: collapse; width: 100%; } th, td { border: 1px solid black; padding: 8px; text-align: left; } th { background-color: #4CABC5; color: white; font-weight: bold; } td:nth-child(3) { border-left: 3px solid black;…

Expanding on my answer above…the following will retrieve the whole dataset.

Go to the AppStore on the ribbon bar and search for Blank Brick or DDX Blank Brick. Pick a new dashboard or one you setup as a test. If you are appending, select your dashboard from the list. It will open with a new card. On that card it wants you to enter javascript in the first window, your html in the next, and your…

CONCAT(DIVIDE(`YourColumn`, 1000000000), ' BN')

Hours: DATEDIFF(timestamp2, timestamp1) * 24 Minutes: DATEDIFF(timestamp2, timestamp1) * 24 * 60 Seconds: DATEDIFF(timestamp2, timestamp1) * 24 * 60 * 60

Change the values from % to decimal. For example, instead of 21%, use the value .21 so Domo sees it as a measurement. Create a card and choose the "Line Chart" option. For the X-axis (categories), you'll want to select the Row Labels (good, bad, evil). For the Y-axis (values), you'll want to select each of the Plan columns…

Responding to @DataMaven….trying to explain as best I can recall. Users need to pay close attention to data structures and accuracy. If I retrieve a date, I don't want it converted to a string or a datetime value. I want a date. And I want an accurate date. When we first configured Domo, we needed to pull from a third…

I agree with Grant. You should check on the error to find out why you're getting the error. An alternate method - you can automate the download of the file from the SFTP site and then upload the file into Domo using Workbench.

I'll have to read up on @timehat's suggestion. I don't use the Views Explorer because I don't want it altering my ability to use standard tools as the warning says. That message always keeps me from exploring…bad pun intended. Michelle is absolutely right about speed. Domo's implementation of SQL is horrendous. I too am…

While I have our instance set at UTC, I hate it. Domo treats API data as UTC. But the APIs I connect to are not UTC, they are in the proper US time zone. We worked tirelessly with Domo and couldn't get a solution working. Domo can't handle it unless we keep our domain set six hours ahead. That means I have to deal with…

Can you hold down the control key to open a card in a new tab? Unfortunately, if they made that a default…it would be the reverse for all us who do not want new windows opened.

Good job David.

@mmisky87 - I'm not much of a Python programmer btw. The method I use to export is quite easy. Install Python on the computer. Schedule a task that executes a small piece of python code (text file). In the code, the dataset identifier is given, and the export file path and name. Happy to share the code if needed.

I'm not sure exactly what you are asking. You can easily import an Excel file into Domo through the file upload. Or use Domo Workbench to schedule an upload/update to a Domo dataset. I'm not sure all the ways to extract. I use Python to extract a dataset out to Excel. Using this method, you can bring large datasets…

@DataMaven - Yes, I'd like to manage the schedules. But first, get an accurate account of what is scheduled. One of the problems with using the history, is that it shows what ran, not schedule settings. I see Domo running things far off the time I have set. I'm interested to see what you come up with in your Gantt view. If…

I haven't found Domo to be very flexible in creating cards with different borders or colors. I don't know a simple way to do this, but you could try it with a some kind of html chart that uses CSS. /* Default text color */ .myValue { color: green; } /* Text color when condition is met */ .myValue { color: red; }

On the recursive ETL, you can set the schedule that triggers. The timestamp formula you use will dictate what gets saved. I use a formula that runs on Monday on one my recursions, that gathers from the previous Sunday through the previous Saturday.

https://community-forums.domo.com/main/discussion/comment/90108#Comment_90108 Let me first state how excited I am that someone is looking at this. Imagine the company manages stores. We don't, but pretend we do. All the stores have sales transactions each night. And those transactions are customer purchases. Every night…

using: CASE WHEN SUM(CASE WHEN `Product`='c' THEN 1 ELSE 0 END) OVER (PARTITION BY `ID`) > 0 THEN 1 ELSE 0 END

A few suggestions… Maybe check the connector to make sure you aren't filtering the data to only include your own tickets. Check query parameters to make sure there's nothing limiting the data retrieved. Even though you have permissions to view and edit not yours, there might be restrictions on the data source that prevent…

Did you confirm there was headcount for Dec 2023 at the time it was pulled? You may need to use something like COALESCE() if there are nulls. Maybe check date ranges to make sure you aren't filtering it out.

It doesn't necessarily require logging as an admin. But the account needs to have the necessary permissions to access all tickets.