GrantSmith Coach

It appears you're using the Last_Production_Date as the date field in your date picker but you're filtering in your ETL based on Order_Completion_Date. Do these end up being the same data or are they different? If they're different you can try and drag the Order_Completion_Date field into your analyzer to force the date…

It's attempting to connect to the database but running into connection issues. Are you able to get a response from the server that's hosting the data source? Are you behind a firewall that would restrict access?

Do you have some sample data to see what your dataset looks like?

When you're evaluating this beast mode it's going record by record so one part of your equation will always be null, you'd need to calculate the max BatchTimestamp date. Are you keying based off a specific identifier field in your chart? Something along the lines of may work depending on how you're displaying your data:…

Create a beast mode which returns YEAR(`CreatedOn`) to return the year and save it to the dataset. Alternatively you can calculate this within a dataflow. Then use this new field in your slicer filter to allow users to filter for a specific year.

Perhaps it may be an issue. I'd recommend reaching out to Domo Support to engage them as they own the connector code.

Domo has released a Domo Brick "Searchable Filter App (Multiple Columns)" which may be helpful for your user case. I'd recommend searching for it in your app store.

Are you using a date field in the graph? Does your data have different date values or are they all the same date? Can you post a redacted screenshot of your analyzer with the date picker expanded?

There's a 30 second timeout for adrenaline dataflows. You'll need to either improve your query performance by rewriting it or attempt to process less data so that the execution time is less than the 30 seconds.

Have you tried using the limit and offset parameters in your GET request to extract the data from Domo paginated?

Not with the out of the box HTML table. You can leverage a Domo Brick and some javascript to perhaps display the pie chart within the graph itself.

It's a permissions based issue. You need to make sure the user is part of the Windows group "Domo Workbench Users" on the actual windows machine where workbench is hosted.

@jgRugby_123098 Since your invoice number field is a string you need to use strings in your IN clause. You can do this by putting them in single quotes SELECT * FROM CHARGE_DETAIL WHERE INVOICE_NUMBER IN ('217653436', '217668183', '819802440', '820092602')

Currently no but I'd recommend adding this to the Idea Exchange

because you’re filtering on price differences and valid and invalid it’s filtering out all downstream data which is why you get what you’re seeing. If you’re wanting to filter on the top level then you’d need to calculate the top level value and included that on all you records so you can filter on that value instead

Seems like an error with your id and secret. Can you create a new pair and try with those?

When you created your Client ID and Secret at developer.domo.com did you select any of the boxes to define the roles?

Have you created a Client ID and Client Secret from developer.domo.com and are you passing those value into your Domo constructor?

Hi @pauljames Are your campaigns going across iOS and non-iOS devices? Facebook recently changed how their aggregate inline-conversion metrics are done across both platforms. Essentially conversions are missing if going across platforms. From their documentation: Facebook will no longer be able to aggregate non-inline…

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.

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.