GrantSmith Coach

Currently virtual datasets aren't included in the governance datasets and there isn't a way to easily get this information.

Ideally you'd use a window function to do this but selecting the MAX of a string isn't available in the Rank & Window function in an ETL. Instead use a group by tile and group based off your loan ID and select the MAX of your T/F field (since T is greater than F alphabetically it'll return TRUE if any one of them is true).…

You can get a list of the available column types from the pydomo code: https://github.com/domoinc/domo-python-sdk/blob/dacdee87d9e798f4c83f270b38c8ea2b1b6c7923/pydomo/datasets/DataSetModel.py#L16

You can pull a custom defined report in the connector setup with Google Analytics and select the fields you wish to pull in. You can select Source and Medium as two separate fields to include.

These are untested but something like this should get you what you're looking for: Previous Quarter Start Date LAST_DAY(`Report Date`) - INTERVAL (MOD(MONTH(`Report Date`), 3) + 3) MONTH + INTERVAL 1 DAY Previous Quarter End Date LAST_DAY(`Report Date`) - INTERVAL (MOD(MONTH(`Report Date`), 3)) MONTH Previous Two Quarter…

Are you wanting just a simple number or are you wanting to graph this over time? If you're wanting a simple number: Topics needed per month: (MAX(`Goal`) - SUM(`Topics`)) / (12 - MONTH(CURDATE()) + 1) -- +1 to include the current month Average amount of topics prior 10 months: CASE WHEN MONTH(CURDATE()) <> 1 THEN --…

Here's a more detailed writeup of how to configure a date dimension dataset which will go over how to set up everything and allow you to do simple YoY or PoP % calculations. https://dojo.domo.com/main/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest

The MySQL dataflow runs slower because it must transfer 16MM rows to the MySQL server process it and then transfer the data back. Queuing via the api doesn’t need to transfer the data across systems so it’ll be much faster

You can use a recursive dataflow and use a formula tile to calculate a TIMESTAMP on when the ETL runs using CURDATE() as the formula Ideally if you can calculate a run TIMESTAMP within your input dataset it would be more accurate as to when the data was actually pulled

You’d need to calculate it in a beast mode and then use that value in the text

You’ll need to reach out to the connectors team to get assistance with your error as the JavaScript is compiled into Java using the Nashorn engine and doesn’t give any helpful error messages. Are you using ES5 (the older version) for your code?

It's easiest to just instantiate a Domo object with your client ID and secret which will handle the transport object creation. Something like this: import logging # Logger object # My Domo Client ID and Secret (https://developer.domo.com/manage-clients) # Update these CLIENT_ID = 'MY_CLIENT_ID' CLIENT_SECRET =…

You can utilize a Line + Group Bar chart to replicate something like this. In the general settings you'll defined the number of series which make up the lines on your chart and the rest default to bars.

We don't have the ability to delete the posts but an admin might be able to. I'd recommend leaving them up but posting how you ended up solving your own question so others can also learn who may be having the same or similar questions.

Get the left characters up to the length of the last 5 characters. LEFT(`Field`, LENGTH(`Field`)-5)

Glad you figured it out. For those who may come later this was because 'en-ca' was being used as a string in a logical expression. It should use an IN expression or multiple logical expressions to compare for both 'en-us' or 'en-ca': CASE WHEN RIGHT(TRIM(`URL`),5) IN ('en-us', 'en-ca') THEN 'Yes' ELSE 'No' END

You can view the save comments on the Version tab of the dataflow's page. There isn't a governance dataset that contains the information though.

You can use a window function in an ETL to calculate the proximity rank where you partition based on your store and order by the proximity distance in ascending order then in your card you can filter for where the rank is <= 5 Alternatively you can try and do the same thing with a beast mode on the card: SUM(SUM(1)) OVER…

You can use a case statement within your SUM aggregation: SUM(CASE WHEN [CONDITION HERE] THEN `Quantity` END)

It may seem a bit complex but because you're wanting to get YoY for dates other than this year this is the best option.

Wrap your beast mode in a case statement to check for this year and then another to check for last year This Year Count: CASE WHEN YEAR(`Fiscal Date`) = YEAR(CURDATE()) THEN COUNT(`Field`) END Last Year Count: CASE WHEN YEAR(`Fiscal Date`) = YEAR(CURDATE())-1 THEN COUNT(`Field`) END You can then put both of these beast…

Logger is a python builtin logging.logger object. You can read the documentation on that object here: https://docs.python.org/3/library/logging.html transport is an instance of DomoAPITransport object: https://github.com/domoinc/domo-python-sdk/blob/dacdee87d9e798f4c83f270b38c8ea2b1b6c7923/pydomo/Transport.py#L8 You need…

What you'll want to do then since you want historical values you can configure a date dimension dataset to then compare the data to itself with a specific offset (in your case the year). I've done write ups on how to do this here:…

Ok, you can utilize a Magic ETL and the Rank & Window tile to calculate the customer's order number. Make sure you sort on the order date and partition based on the customer identifier and calculate the row number. This will then get you a number for each customer's order with their first order having a value of 1. You can…

Did you have users get created or removed during the month? For example if we're at 50 but you removed 5 users and added 5 users Week 1: 50 users Week 2: 50 users - 5 removed, 5 added = 50 Week 3: 50 users - 5 removed, 5 added = 50 At the end of the month you'd have 60 different users instead of the 50 you're seeing each…

Hi @zuchu Do you have the customer's first order date as part of your dataset or do you need it calculated?

Yesterday: CASE WHEN `INVOICE_DATE` = CURDATE() - INTERVAL 1 DAY THEN `INVOICE_TOTAL_AMOUNT` END Last Year: CASE WHEN `INVOICE_DATE` = CURDATE() - INTERVAL 1 YEAR THEN `INVOICE_TOTAL_AMOUNT` END

You'll want to do something like: ( AVG(CASE WHEN YEAR(`purchase_date`) = YEAR(CURDATE()) THEN `purchase_price` END) - AVG(CASE WHEN YEAR(`purchase_date`) = YEAR(CURDATE())-1 THEN `purchase_price` END) ) / AVG(CASE WHEN YEAR(`purchase_date`) = YEAR(CURDATE())-1 THEN `purchase_price` END)

What you could do is use a recursive ETL to store the current value that's being updated and the old value that was in the former dataset. Then compare the two, if they're different you can set a flag on the record saying it changed and then alert on that specific value.

Have you looked into subtotals on the table card and having your red/green column be your subgroupings?