jaeW_at_Onyx Coach

@kstaufferTek , what problem are you having? This is probably a question best directed at support@domo.com

@msharma be specific about WHERE you are conducting your ETL. It's imprecise to call anything "Domo SQL" and no one will know exactly where you are in the product. @MarkSnodgrass is correct MySQL dataflows do not support Window functions. It's not because it's a 'Domo flavor of SQL'. MySQL dataflows are running in MySQL…

is the entire row duplicated, or is there a slight change in one column value?

What you're describing is a window function. If you abstract your problem and google "percent of total" SQL, you'll find loads of solutions. You'll have to ask your CSM or support to enable "Window functions in Analyzer" but after that sum(sum(hours_worked)) over () will give you the 56…

I assume this is data where you took a payment table and JOINed it to a Employee Timesheet table. Don't JOIN the data. Append, UNION, the two sets of data together. I know it sounds like work to understand why UNION is a better solution than JOIN. But trust me. As you JOIN transaction tables together, you are going to try…

@AJ2020 , to phrase, your question in plain English, is the problem you're trying to solve "if the activity finished after 3pm THEN assign it to the next business day?" if so then you can break the question into 2x parts 1) does the activity occur after 3pm? CASE WHEN <activityOccursAfter3PM> Then <nextBusinessDay> ELSE…

@Stefano true. send a fetch or any other async method of querying APIs in JS.

... i didn't write domo.js :P why don't you just send curl requests?

@StefanoG who is sending the 400 error? Domo or AWS? are you saying you're unable to capture the response from domo.post? b/c it seems to me you would just async / await and console.log the response.

@user17774 have you looked at the other reports you can generate in Domo Stats (People)? or Domo Governance (Users and Groups)?

@msharma think of analyzer as an engine for writing a SQL query. When you add filters, you're adding a WHERE clause. Your Beast Modes are part of the SELECT clause. in SQL your execution order is FROM - WHERE - GROUP BY - SELECT - ORDER BY. Same applies in Analyzer.

what happens when you don't use SELECT * and actually select column names?

@nicangelica this one is a brain teaser. assume we are trying to capture the last time 'cost changed' 1) window function calculate the previous cost (lag, 1) 2) create a binary (isCostChanged) using a CASE statement. 3) take the cumulative sum of isCostChange using window function (sum). at this point you should basically…

@user030156 , change your aggregate in analyzer from the default of SUM to AVG.

I don't think this is possible without preaggregating the data. to apply conditional formatting, you'd have to be able to wrap the aggregate in a CASE statement CASE WHEN sum(amount) 10 .... END But Domo broke that functionality a few weeks ago. I don't know if it's been restored.

i wouldn't do this in MySQL anymore, I'd do it in Magic 2.0, but this will get you the results you want. Basically your initial dataset A1:b3 Duplicate each row by the number of commas (antigens) order_id 1 has 3 antigens, therefore duplicate the row 3 times. then keep the nth antigen. your granularity should be one row…

this is the reason why i try to avoid using period over period cards and instead always recommend building your own date dimension that handles period comparisons for you. https://www.youtube.com/watch?v=CDKNOmKClms

@Sam1 , @GrantSmith is correct insofar as the access token you generate (or client_id & secret combo) will have the same permissions as the user with which the token was generated. to control which rows of data a user has access to, use PDP policies. to control which APIs a user can use (what actions they can take in Domo)…

just build your own week-based date dimension. then construct an offset calendar.

@Fatias MySQL 5.65 is several years old. I'm pretty sure it's safe to say it's not a priority to upgrade the version of MySQL to something more modern. you don't have to implemen using parent_id < id. you can implement where you accumulate the path concat(path '+', id) as path and just filter WHERE path not like '%id%'

@Kumar619 it's a feature that needs to be enabled on the instance, contact your CSM or support and ask them to enable "window functions in beast modes"

I assume you checked the obvious culprits like making sure the card renders and removing any erroneous beast modes that error out? Have you tried sharing the card with the user first? If the obvious things fail, send a support ticket, they have the right tools for debugging bugs.

APPEND your data instead of JOINing it. https://www.youtube.com/watch?v=PVbOeLSae9o

@serendipity if it were my requirement, I would have two separate cards for two different audiences. (AND still apply PDP as necessary). Also, check in with your CSM, I believe Domo were working on column based PDP but I don't know how far they got on that.

Data in Domo doesn't reside in a RDBMS system. So you can't create an ERD like you would in other SQL environments. THere is a Governance dataset that will give you schemas,…

@swagner , you can't finish your requirement just using window functions in analyzer. @GrantSmith is hinting you in the right direction. You're trying to functinally filter on an aggregated value (if the sum of activity in 2019 and 2018 is greater than x then .... ) If you've got 30M rows you can still get away with…

uh... it sounds like you're describing interactive filters, but you'r use case is pretty... vague. in Domo it is possible to set up a filter that applies across multiple datasets. so if i have two different datasets with a column called Color... i can filter on "color = red" and then filter both datasets...

@swagner this would be a 'usual suspects' type question if you asked a TAM. Can Vertex automate emailing to you? (email connector) can Vertex set up an automated file drop? (FTP, Amazon S3 or similar storage)? I didn't look closlely at the documentation, but it sounds like Vertex provide a CLI (a cli presumably would allow…

Sorry @GrantSmith and @MarkSnodgrass hard disagree. Don't JOIN the data. APPEND them. If you get to the point where you have multiple rows per week OR if dataset 1 is at a different granularity than dataset2 then you end up with row growth (because you're JOINING) and you have to crazy math to 'SUM DISTINCT). 1) add a…

@banderson use UPSERT + Domo CLI https://knowledge.domo.com/Administer/Other_Administrative_Tools/Command_Line_Interface_(CLI)_Tool#section_34 https://www.youtube.com/watch?v=kHSeSbSFS1Q (sorry less polished video, but gets the job done).