GrantSmith Coach

That's an odd error. You'd need to contact Support to have them help diagnose the issue.

CASE WHEN SUM(revenue) > 1000 AND SUM(CASE WHEN (`date` - DAYOFMONTH(`date`) + 1) = STR_TO_DATE(CONCAT(YEAR(NOW())-1,'-',MONTH(NOW()),'-01', '%Y-%m-%d') THEN `revenue` END) WHEN . . . END You can try something like this to check if date is equal to 12 months ago and has 100 or more in revenue and the overall revenue is…

Due to how Marketo returns the Program information it doesn't return the tags and you'd need a specific ID or Name to get the tags associated with that program. This currently isn't available in Domo's connector. To get all the program tags you'd need to likely write your own script to query all of the programs then call…

Google typically has a really good Python packages which help to connect to their APIs. Has your dev team looked into using ? You could pair it with pydomo to upload the data into Domo.

@AnnaYardley @eddiesmall can you remove this for @afieweger ?

Currently this is controlled in the backend by Domo and isn't exposed to users to remove the padding on it. If you're wanting that level of control then you'd need to either use a Domo Brick or a custom app to do your visualization,

There isn't a simple way to do this as a week of the year can straddle two different months so you wouldn't be precise with the months when you calculate it this way. How would you want the monthly amounts to be calculated? Based on the start of the week or the end of the week? You wouldn't be able to get precise monthly…

If the data in the Drillable and Sort Order columns are always the same then you could utilize a Rank and Window tile to calculate the MAX value of those two columns to get your two new columns with the values filled. Then you can just drop the old columns and rename the original questions. Alternatively if you're looking…

Variables don't currently support adding values automatically. A pviot table will take all of the same values and combine them together. What you'd likely need to do is utilize a unique identifier for each advertiser but mask out the actual advertiser name. You could utilize something like a row number or the MD5 function…

Currently this isn't possible but I'd recommend adding it to the Ideas Exchange to allow getting the logged in user's information.

Have have you looked into doing a rank and window tile to calculate your number? That would then put it on each row

Domo currently doesn't support filtering with window functions, so you're getting the error. They did previously but recently stopped supporting it without any reasoning or documentation.

It appears that you're somehow multiplying your original number by 10 as your result of 12,676 is equal to 1344*10 - 764 Are you doing any aggregation with your beast mode? Can you paste your exact beast mode you're using?

Try something like this: CASE WHEN `Track Split` LIKE CONCAT(CONCAT('%', `Library`), '%') THEN 'AZ' END

COUNT(`Room/Row Id`) gives you the number of rows with that column populated so if you have multiple rows with that same ID it will count all of them. If you want to count the IDs just one time you'll need to do a COUNT(DISTINCT `Room/Row Id`) 

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.

Partitioning in Magic ETL: Magic ETL documentation:

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 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…