jaeW_at_Onyx Coach

I know this issue is already resolved but you should try building this in Magic. It will be SIGNIFICANTLY faster and be much easier to maintain because what you descibed can be done with two tiles. RANK (rownumber) and Filter where Rank = 1 1) from the end user perspective, one of the nice things about Domo is that it…

@user19019 , any chance you could leave a little writeup in the Dojo on what the resolution was? it'll be great for future visitors to the Dojo.

I stand by my previous recommendation @user048760 instead of having one row per site with KPIs in columns i would recommend the schema Site, Date, KPI Name, KPI value This will be a much more flexible model that won't force you to pre-aggregate your data and allow you to build more extensible models at different…

Here's a link to Grant's entire presentation!

@MarkSnodgrass is correct there is no referential way to refer to pre-defined beast modes. @JustinB you generally should not nest aggregations inside a CASE statement. case when (sum(`Clicks`) / sum(`Impressions`)) < x then 0 when (sum(`Clicks`) / sum(`Impressions`)) < y then 1 when (sum(`Clicks`) / sum(`Impressions`)) < z…

@imelendez Nihar did a whole session about this at the recent conference. https://www.youtube.com/watch?v=kmC-0ncu9PA Let's unpack a few things. 1) why do you care if it takes 15 minutes to run a dataflow? how often are you trying to update the data? you can't use a recursive dataflow AND have low latency run times. the…

you probably shouldn't delete the dataflow. if you ever want to update that output dataset again, it will be a non-trivial challenge to push new data into it. if it were me i'd leave all the content there. if you MUST get rid of input datasets to save on row count then just delete the inputs. there's no cost to having…

given how new and novel the connector is, i would recommend opening a ticket with support. are you able to work around it by sending data via postman or Zapier?

@user048760 , why do you need to aggregate rows in ETL? If you just put SiteID on an axis in a card and then take the sum of those columns it would do the same thing without the extra step. Is there more to your use case? (where i'm going with this is generally you want to avoid aggregating your data in ETL).

@SeanPT thaaaaats gonna get expensive. do you want to post a screenshot of what you've currently got and describe the JOIN?

I believe Domo broke this functionality back in Feb of this year and never fixed it. you can't do math on the PARTITION BY clause on Dates and then aggregate to the week using the Date filter grouping functionality. Instead, calculate YearWeek as a materialized column on your dataset and change your Partition By Clause to…

@daniellecroft contact your CSM or support@domo.com. the feature you're asking for is "filter on aggregates in analyzer"

what's your business requirement. i think most people would say you can't take the average of an average. you can take the max of an average. If i had to guess you have a bunch of transactions. you want the daily average. so you put date on the X Axis and then Avg(amount) That works fine. now you want the max of the daily…

@mattAnonomatic ... is it fair to assume that you can connect to a domo instance? also are you able to use an older (not beta) version of Workbench successfully? does workbench crash with other job types? (odbc)

it sounds like you have two questions 1) how do i identify data that was created in the previous quarter. create a date dimension with columns Date. And Start of Quarter. Then you can JOIN to your fact table and identify if the data was made before the Start of Quarter. 2) how to just show data of the current quarter.…

it sounds like you have two questions 1) how do i identify data that was created in the previous quarter. create a date dimension with columns Date. And Start of Quarter. Then you can JOIN to your fact table and identify if the data was made before the Start of Quarter. 2) how to just show data of the current quarter.…

@AndreF you're describing a couple different things. 1) security should be handled with PDP. full stop. Use PDP. 2) you want to embed inline editor. What's the problem with SSO login? is that not desired behavior? How would you like the experience to be different?

Slight correction. Percent is the same as a * wild card. So to accommodate the newline char add % CASE WHEN 'Note' LIKE '%Bankruptcy Record%Dismissal%' THEN 'Dismissal' ELSE 'Other' END' Domo Formula tiles do support REGEX expressions so just google "regex remove numeric" something like…

@faisalnjit 1) i would recommend a different visualization. consider the Bullet Chart which was designed to show target vs. actuals. by having data spread across two axis you force users to compare something in a way that may not be intuitive. By stacking Actuals and Plan into the same column of your data you've made it…

You mean other than "remove duplicates?" Really not trying to be snide, it sounds like there's a disconnect between what you expect to happen after "remove duplicates" and what is actually happening... If you don't want to lose rows, can you just remove the "remove duplicates" tile?

There is a beta for filtering on aggregates. it has been in early beta for two years and works well enough. @MarkSnodgrass the feature at DP21 is an update to the UI. no idea where we are in beta on that.

it looks like the data wasn't imported properly. if the actual data contains "List" then you need to revisit your connector. Had the dataset imported properly, i would expect to see a lonnnnnnnnng string. P.S. may need to confirm with domo that you can store wide text string datasets.

@mberkeley then split your data upstream into the two separate columns / sets of data. create a stream of data that includes excludes / dedupes category info add a constant "Activity Type" = "page_stats". create a second stream that includes category info but doesn't include the metrics for "time in seconds"…

@mberkeley if i had to guess you have times duplicated because you JOIN'ed two datasets together. If that's the case, instead of JOINing them APPEND them. That way your times don't Duplicate and you don't have to do avg(DISTINCT) https://www.youtube.com/watch?v=PVbOeLSae9o&t=250s

@MartinB when you say you can't console log, what IS it logging? if you just try logging plain text i.e. console.log('hello world') inside the .the() do you get a result?

@Ashleigh is the resident expert on Coursebuilder

@user079817 it sounds like it might be a bug. have you tried sending a message to support? Also, you can sniff network traffic in the browser, try watching traffic when you create a PDP policy in the UI. Maybe it structures the request slightly differently.

@user095063 @MarkSnodgrass is spot on in his SQL. The key difference between JOIN + ON versus subquery + WHERE is that if there was additional data of interest from the subquery, you wouldn't be able to include it in the SELECT clause. But what's your use case? solving SQL syntax is easy... but I have questions about what…

I blogged about it in YouTube / on my blog. Side note, you can do the same thing in Magic 2.0

@User_32236 , Are you hitting a Domo internal API or an external API? Domo has restrictions on which internal APIs can be hit. For more details on the error you can email support@domo.com and they'll forward your issue to the connectors team. Alternatively there is a Connector Support email <supportconnectors@domo.com>