jaeW_at_Onyx Coach

@pl_Luke Domo are working on a beta feature that will give you this idea of a 'baseline group' that is unaffected by a specific (set of) filters. In your case the Reason Code. this feature is in beta and I'm completely unsure when it's going to release for GA or how stable the implementation is, but definitely check in…

@MarkSnodgrass is correct. if you check version you're on MySQL 5.6 doesn't support window functions. Magic 2.0 is amazing, get it enabled (talk to your CSM) if you don't already. It will be more performant. That said, If it were me, 1) I'd convert Year and quarter into a date type column (probably the last day of the…

When data gets loaded into Domo it's assumed data is being sent in UTC. Then when Domo displays the data to you, it is translated into the timezone of your "Company Settings." so if the your company was in EST the data should be 'automatically converted'. places where people fall over is in not transmitting the data in UTC…

You don't have to specify where the email is coming from, as long as you send an email to a specific inbox, by default it will get added to that dataset. specifying email addresses to accept data from is a security feature to limit the risk of spam. but you could define "email must have a specific subject" instead of…

Use a dataflow to convert your text column into a date column. In Magic 2.0 you can convert date types using the INPUT tile, or you can use the equivalent in STRING_TO_DATE using date tiles. This extra effort will allow you to use date functions in Beast Modes.

? can you be more specific about the error? Window Functions require feature enablement, contact your CSM and ask them for "Window functions in Beast Modes"

There's a bunch going on here ... 1) why are you building a CASE statement that returns text when your ELSE clause will return a number? 2) if I had to guess you have Date on the axis hence why you're seeing repeated dates. swap it with the math in your order by clause, DATE_FORMAT(`last_activity_at`,'%Y-%m-%d') 3) if you…

you could use the domo_governance dataset or the DomoStats_DataflowHistory (i believe) dataset to see how long it's taking dataflows to execute, but they would have to be updated periodically ... usually Domo prefers the governance datasets to only update daily. are you running this ETL multiple times a day? you could…

https://pypi.org/project/pydomo/ https://developer.domo.com/docs/dataset-api-reference/dataset @imelendez you have a couple options. 1) use pydomo + request commands in a python library to develop a script that executes periodically (controlled locally on a VM or your desktop) that then pushes the data into domo via Domo's…

Strong agree. @Shumilex in this context you really don't want to JOIN two fact tables together it will always lead to unexpected row duplication and create more challenges when trying to visualize the data. APPEND ing the data together will make viz much easier as well as give you a much simpler ETL.

@PacoTaco this problem has been solved before but ... i think it's usually an add-on app or tool that clients pay for. ask your CSM, but also check in with the Domo User Group b/c this can be done with Python Scripts and the like. I think Andrew at CrystalBallers may have a custom app. Are you in the global slack…

@Khan_Naziya ? i feel like i've suggested to you multiple times to build a date dimension table... you're not gonna love this answer ? build a date dimension table. What you need is a YearMonth_Lag column that calculates the number of month's lag (0,1,2,3,4,5) from the current date. You calculate that with a Row_Num() Over…

What you're asking for is not possible without pre-aggregating your data in ETL or a dataset view. What you described is wanting your ratio calculated at one row per customer SUM(...) / SUM(...) To do that you had to put Customer on the Axis. But you don't want one row per customer you want groups of the ratio (hence the…

... so you want a chart that shows change over time. AFAIK no. you'd have to build a custom app. https://www.domo.com/covid19/geographics/global/ in the middle of this page they have an example of what can be done... but basically you'd have to code your own app / viz and upload it to your Domo dashboard.

https://stackoverflow.com/questions/41330789/convert-seconds-to-days-hours-minutes-seconds-mysql

format it.

flick through this video. might get you there more easily. https://www.youtube.com/watch?v=oYcpYE7DiV4 in a nutshell, count the number of commas in your string. duplicate the data for 1+n commas for the nth copy of the row, keep the data after the nth comma.

there is a census bureau connector. take a look at the reports avaialble in the Dimensions connector (I don't know the answer to your question outright, but these are places i would look)

this could be ... 'normal' behavior. if i were a betting man, i'd look at when your datasets finish updating (indexing) versus when you see these 'errors'. two possible issues. if your dataflows are updating mid day ... your users are getting confused about timings (this can be particularly challenging if your one…

... what didn't work? where did it break? i guarantee you the ROUND() function works and UNIX_TIMESTAMP() works. so why doesn't it work with your beast mode? peel away the layers. remove ROUND() function. does it work? Remove the math. you probably have a parenthesis in the wrong place.

Angela, we can't tell you how Domo works, but you can maybe be more specific about what you want the ROUND functionality to do. mathematically 2.273 SHOULD round up to 2.3. if you always want to round down take a look at the FLOOR() versus the CEILING() implementations for ROUND.

also ... this is redshift, it maybe faster to SELECT * FROM WHERE ... is null than executing a DELETE statement.

... there are two transform types. one will CREATE TABLE the other will allow you to execute a SQL statement. Choose the right one.

this is a tough project. I've seen it done poorly ... a lot. you'll need to start with what I call an 'account schedule' but it'll need to be granular. you'll need a minimum of two columns (row_name, and join_account) in the dataset you'll need one row for each account in the calculated row. income , 4001 income, 4002,…

You can't gracefully add X and Y target lines AFAIK. but what you could do is create a beastmode case when x >= 50 and y >= 30 then 'q1' when x < 50 and y >= 30 then 'q2' when x >=50 and y>= 30 then 'q3 else 'q4' end

you can do this with the "Document Card" but i'm not sure I'd recommend this workflow. https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/Doc_Cards/01Adding_a_Doc_Card_to_Domo if it were me, I would try to recreate the macros in Domo via ETL or DSV or analyzer so that the data doesn't need to leave Domo. Document…

the window function isn't super great for these percent of total type calcs. the design pattern @GrantSmith is recommending is calculate your categegory totals with a group by, rank the subtotal, then JOIN the results back to your main dataset. This is potentially unweildy so you could implement this design in a dataset…

@GrantSmith has a great writeup somewhere (grant, can you link it?) wherein he recommends converting your dateTime collumns using unix_timestamp, which should convert the dateTime into a number of seconds (which you can absolutely add or subtract). Then you just divide it by 60 or 3600 etc. to get number of minutes ,hours…

it is unclear to me why you need rank for percent of total. assuming you have Domains on the axis you could get each domain's percent of total with sum(video_plays) / sum(sum(video_plays))

sum(case when date ... then amount) / sum(amount)