GrantSmith Coach

That typically refers to an issue that Domo has traveling your days from storage to the processing area. Does your dataset have data? Can you use it in a separate dataflow?

Use a formula tile to add a constant called Join Column and set the value to one. Do this for both of your input datasets. Then use a join tile to join them on this new join column. After that, you can feed it into a dynamic unpivot tile to pivot your data on the date field to get the output format you're looking for.…

Also, how is your data structured? Do you have your data aggregated for each day or is it each transaction? You can get the week max by doing something like: MAX(SUM(random_number)) OVER (PARTITION BY dt - DAYOFWEEK(dt))

Restructure your data so you have a single date field and then a second column with a date type field (submission or completion) and then a third column with your value. Then you can use the date type field as your series

Domo has a feature called Federated data which will utilize your warehouse and query directly against it so you have realtime querying of data. https://domo-support.domo.com/s/article/360042932974?language=en_US

Partitioning in Magic ETL: https://domo-support.domo.com/s/article/000005150?language=en_US Magic ETL documentation: https://domo-support.domo.com/s/article/360055259234?language=en_US

There isn't a simple way to do it within Magic ETL but you could attempt to calculate a specific value change id. To do this you could use a formula tile to conditionally set a column value of 1 if the field is not blank or 0 if it is blank / null. Then using a rank and window tile do a running SUM of your column so that…

Have you tried displaying your Actual / Budget / Variance and then the month in your pivot table so that the ordering is reversed?

Domo can do all three of those things. Regarding #2 Domo does have a MySQL type dataflow where you can utilize SQL queries to transform your data however there is also their drag and drop Magic ETL tool which does allow for some SQL like syntax as well in a formula tile and would be more performant than a MySQL dataflow.…

Your COUNT doesn't like the condition, you need to return a value for it to count and not a logical expression. COUNT(CASE WHEN [your condition] THEN 1 END)

Domo has a wide variety of capabilities. No two ETL tool has feature parity so I'd be interested in knowing if there are specific capabilities you're interested in learning if Domo is capable of?

Does your endpoint return the total number of pages in the response? When configuring the connector are you expecting that value to be there or is it set to No?

There isn't really an explode option (csv column → rows) within Magic ETL. You can leverage a MySQL dataflow to help normalize the data. Code like https://stackoverflow.com/questions/17269444/split-explode-comma-delimited-column-values-to-rows may help you do this.

@PJG Magic ETL dataflows are a great way to enhance your data efficiently especially in such cases as yours where you can translate one value to another and have that value then accessible to all your cards. Domo's Knowledge Base has some good articles on Magic ETL. I'd recommend you start there to learn more about Magic…

To add some additional context the first one works because it will return a singular value from your window function so any aggregation on your card will work on that field but can cause some issues depending on your sorting and grouping and other aggregation that's being performed on the card when it's displayed. The…

Hi @pauljames , Typically for connectors that Domo doesn't provide out of the box, I'll either write my own custom connector or I'll utilize a scripting language like Python and the pydomo library to ingest the data myself. It's a bit more technical to get the data but there's a lot of documentation out there.

You can utilize a window function to calculate the estimated month depending on the number of days that have elapsed in the current month. LAST_DAY returns the number of days in the month Running Total: CASE WHEN `Date` < CURRENT_DATE() THEN SUM(SUM(`Sales`)) OVER (PARTITION BY LAST_DAY(`Date`) ORDER BY `Date`) END End of…

How is your data being grouped? Are you looking for the max date across all records or within a specific partition of your data?

You would create a beast mode for each of set which would be a conditional sum where the period type = Last Year then use that beast mode for the prior year graph and period type = current for this year. Both are keyed off of the report date field but the data would conditionally be last year or current

I'd recommend utilizing a custom date dimension which would allow you to have a singularly selected date but then allow you to show last year's data. I've done a write up on this in the past you can find here: https://community-forums.domo.com/main/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons…

If you have a constant value from your calculation you can apply that value by doing a Cartesian join. To do this use a formula tile to add a new column called Join and set its value to 1. Feed this into a filter to only get your single value for the specific code. Then duplicate that filter and change it so it’s getting…

Does it accept a POST request instead of a GET request?

That would need to be an idea in the Idea Exchange for Domo to allow the ability to "zoom" to a specific time period in your data without filtering out your data as it's currently not supported.

Due to standard security practices a NOT IN option typically isn't provided as it opens up the data possibly to everyone on accident rather than just a single person on accident. NOT IN is a more risky security practice which is why Domo doesn't include it. Alternatively, you could configure specific groups to not include…

HTTP GET requests typically don't accept body parameters as part of the protocol specifications. GET requests typically pass parameters as part of the URL as URL parameters instead of body parameters. Are you able to pass those using addParameter before your request?

You need to add a comma to your date format: DATE_FORMAT(`MyDateColumn`, '%b %d, %y') For others who come across this there's a great Domo KB article on date format string you can find here: https://domo-support.domo.com/s/article/360043429953?language=en_US

I don't believe an official list exists however I'd recommend looking at the Beast Mode Function Reference page and avoiding using any of the functions. Alternatively, you could just prepend or append a character like an underscore to avoid name collisions dynamically.

In order to track the weekly stats you'd need to either use a dataflow to add in the timestamp and schedule it to run once a week and have it append on the output or alternatively use a dataset copy connector and set it to append to automatically copy the original dataset with the _BATCH_LAST_RUN_ timestamp field. As for…

You need to wrap your entire case statement in SUM instead of having your condition be the sum. It's evaluating each row at a time and then aggregating when you want to aggregate after evaluating all the rows. SUM(CASE WHEN … … THEN `INVOICE_AMT` END )

You’d need to explode your data so that you have a record for each month. You can do this with magicETL and filter where day = 1 to only get the first of each month. Then using a formula tile on your data you’d need to calculate the first of the month with something like `Subscriotion Start Date` - INTERVAL…