GrantSmith Coach

Hi @at326 I'd recommend reaching out to Domo Support as they'd likely have more information on this error and would be better able to help diagnose your problem.

Here's some code you can copy and paste into a Magic ETL 2.0 which I think highlights Mark's solution: {"contentType":"domo/dataflow-actions","data":[{"name":"Sample…

Dang @MarkSnodgrass I thought I was faster than you! His solution is the better one since you're wanting to calculate the difference and don't always want 0 displayed for your null values. You will need to come up with a cross product to determine all possible year + client + state combinations, left join your original…

Hi @MattLynn It's because there's no data for Domo to evaluate in your pivot table to even apply a coalesce on. What you can do is under the General Properties of your pivot table you can check the "Fill Empty Data Cells With 0" option to tell Domo to display 0 instead of blanks in your pivot table.

One option is to utilize the lag window functions to calculate the difference between the current year and last year. The caveat to this is you can't have missing years between each salesperson and state (going from 2019 -> 2021 missing 2020 for example) A pivot table would end up looking something like this which isn't…

@amehdad Your beast mode won't work correctly as count(0) is still 1. You'd need to drop your else clause if you're using count (how many non-null values are there?) COUNT( CASE WHEN status = 'A' AND 'Hire Date' <= DATE_FORMAT(CURRENT_DATE(),'%d/%m/%Y') AND 'Termination Date' IS NULL THEN 'ID Number' END) @Abhijith Here's…

Hi @Adrien You can use partitions in your window function: SUM(`TOS`) / SUM(SUM(`TOS`)) OVER (PARTITION BY `Sales Leader`, `Month`)

You wouldn't need the /4 and your total shipped should be surrounded in a parenthesis. (LAG(SUM(`OT Shipped`)) OVER (PARTITION BY `Customer` ORDER BY WEEK(`Date`,2)) +LAG(SUM(`OT Shipped`),2) OVER (PARTITION BY `Customer` ORDER BY WEEK(`Date`,2))+LAG(SUM(`OT Shipped`),3) OVER (PARTITION BY `Customer` ORDER BY…

This methods assumes you have no missing weeks. If you miss a week it will cause your calculations to be incorrect. Are you attempting to calculate the rolling average across all your customers or within each customer? Also with your SUM function the way you're calculating it now is an average of the average which isn't…

Hi @Ashleigh Are you wanting to the City DC to show up or have data for DC to show up? Showing the city name can be done with the Cities > Show Cities option and turning it on. If you're wanting to show the data you can make sure you're using the ZIP to FIPS connector (or the Domo Dimension connector with the…

Hi @Derreck You can just add a day to the date: DATE_ADD(DATE_SUB(`dt`, INTERVAL (DAYOFWEEK(`dt`) - 1) DAY), INTERVAL 1 DAY) End of the week: DATE_ADD(`dt`, INTERVAL (7- DAYOFWEEK(`dt`) + 1) DAY)

@Madz_A I'd also recommend logging an idea in the idea exchange to allow the removal of the dotted line on the notebook cards.

Hi @Ainash I've tried using the Google Sheets method but it's hard to know if / when the data is finished importing into google sheets to then have Domo pick up the correct data. I ended up utilizing the pydomo SDK and the Google Ads python SDK to query Google Ads, process my data and then upload it into Domo via their API…

@jaeW_at_Onyx I believe the issue is that the Glue process happens on AWS's end so the CLI wouldn't be able to kick it off and know when that job has finished.

Looks like I need to wake up earlier get my answers in before @amehdad :) I agree with @amehdad but wanted to add some clarification - The MagicETL or MySQL recursive dataflows will allow you to filter possible duplicate records however the larger your dataset becomes the slower / less performant it becomes because there's…

Hi @Tow Typically when I have a more complex scheduling pipeline like this with data outside of Domo I’ll use a Python script to kick off each of the jobs serially in a single script so I know it’ll run each step in order.

Hi @Hiraayub You can utilize a beast mode LAG and LEAD functions to determine if it's in a 3+ day run. LAG 1 and LEAD 1 = Day with one before and after LAG 2 = Day with two before LEAD2 = Day with two after CASE WHEN (LAG(MAX(`Date`)) OVER (ORDER BY `Date`) = `Date` - INTERVAL '1' DAY AND LEAD(MAX(`Date`)) OVER (ORDER BY…

Looking at the existing Azure connectors they don't appear to fit your needs with that API endpoint. the JSON connectors may allow your to connect to it but I haven't used those heavily so I can't answer for certain. You may need to write a custom connector.

Graphsql endpoints can work in Domo but a connector needs to be written as each endpoint is unique in it's processing and data being returned. There are some prewritten connectors for things like Facebook which uses Graphsql in the connector library.

@Ashwin_SG Glad you got it sorted out! If you could accept my solution so that others who are searching for your issue could find it more easily I'd appreciate it.

As someone who can't seem to stay away from the Dojo I agree but make sure you have access to all the features of the dojo and not just some subset of things you can do like it currently is when you access the Dojo via mobile: I logged Respect Load Desktop Website on mobile a while back to make sure we can get access to…

Your days are negative because your date assigned is coming after the application started date. And because -27 is less than 15 they're all falling into the bucket. You have a few options. One is you can utilize the ABS function to convert any negatives to positive so in you cases where the difference is -27 it'll evaluate…

Hi @Hiraayub This is because you have your dates swapped. Which date is supposed to come first? You need to do your end date - your start date since the end date will be greater. Swap `Application Started` with `Date Assigned` such that `Date Assigned` is coming first.

Glad you got it figured out!

Hi @George_LL This sounds like a bug. I would reach out to Domo support and raise this issue with them.

Hi @Tsharma8724 The main difference is from a security standpoint. The cloud connector will have Domo connect directly to your database and are typically easier to get up and running. With workbench Domo doesn’t have direct access to your database but rather you have a local windows machine that will connect to your…

Hi @WorldWarHulk I'd be a bit wary of using just the beast mode name to check if it's a duplicate as you can have the same named beast mode on multiple different datasets doing the same calculations but with different columns. What I've done in the past is utilized a Magic 2.0 ETL and the Domo Dimensions - Beast Modes…

Hi @Pierce13 Typically when doing period over period charts I'll use a custom offset dataset along with bar + line type graphs to display prior values. I've done a write up previously on this methodology here: https://dojo.domo.com/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest In a line +…

@nbrx - Glad you were able to get the metrics. If you could mark my answer as accepted so others can more easily find it in the future I'd appreciate it. Thanks!

Hi @user000253 You can use a beast mode to create your custom buckets (Name 1 & Other) and use that as your quick filter. CASE WHEN `name` = 'Name 1' THEN `name` ELSE 'Other' END This is assuming your column is called 'name'