jaeW_at_Onyx Coach

@Chris_Wolman send your issue to support@domo.com they'll be the most suited for helping debug this issue.

you can convert your card into a table from the Card Details pane and you can export your data from the UI. if you monitor network traffic you can see the API request that's being sent by the browser. https://www.onyxreporting.com/blog/domo-python-tutorial-execute-datasets-and-dataflows-via-api-and-pydomo

I believe there's a feature switch (might be beta, contact your CSM) that can hide the filter icon. buuuut, i wouldn't recommend that b/c the filter icon lets you know that a card is being filtered by the dashboard.

did you mean developer token as in developer.domo.com or access token as in domo -- admin -- access token? i think you'd want both and to be able to differentiate between both so users could track API usage

the cleanest method would be to think of your numerator and denominator as two different sets of fact tables which you then UNION together. your first set of facts are just employee call transactions. (i would add a callCount = 1 so you can do a clean sum instead of a count) then your denominator should be EITHER 1 row per…

if it were me, I would implement the DS pipeline and the recursive dataflow as two separate dataflows. separate interests. if you alter your DS pipeline for whatever reason, or need to test something, you don't necessarily want to commit that the your recursive dataflow. and if you need to add new columns or calculations…

@DataUp , your beast mode will not behave as expected UNLESS you have the day of the week (Sun, Mon Tues) on the axis. At which point your CASE statement is superfluous and you could just do a count(distinct on dates). Even that aside, conceptually you're mixing up two things. In your solution, you've combined what should…

@user052647 You should probably stop using Fusions and switch over to using Data Set Views as soon as reasonable. Fusions and DSVs use the same technical underpinnings, so I like to frame DataSet Views as an improved UI for Fusions. With DSVs you can JOIN Fusions on Fusions. Keep in mind a Fusion is the same as a VIEW in a…

i'll just leave this here.

I would not get into the habit of JOINING fact tables this will lead to heartache and row growth. if you continue down this path you tend to end up with a ton of single use datasets that only work for the card they power. instead UNION the two tables together (usually I like to differentiate with an Activity Type column.…

@MattLynn and @GrantSmith be careful about that Partition by seller and state. i think you just want to partition by state. check the boundaries between when you switch sellers, you may have unexpected results with that LAG.

@GrantSmith it feels like you're overcomplicating this. if it were me, i'd try writing CASE statements CASE WHEN numerator is not null and denominator is not null then numertor / denominator When denominator is not null then 100 else null END

have you confirmed that your credentials are still valid ?

amendment i would make to @GrantSmith 's ETL. if the employee has not been terminated, then sent the termination date to 1 year from today's date. that way you have a clean FILTER instead of filter on Term Date is NULL. also by setting a rule, you can include it in the data dictionary for how your dataflow / data set…

looooong video about recursive dataflows. in any event. you'll want to have a data column. maybe =today() or whatever the equivalent is in your google sheet. then you have something you can run your comparison against when you build your dataflow. the docs have you do a JOIN. I think I'd recommend doing an APPEND and then…

if you want to calculate livetime value. In ETL you can GROUP BY Client ID and sum(Amount) then JOIN that back onto the transactions. OR you can use a RANK & WINDOW function to calculate cumulative Sum (so you know lifetime value at the time the transaction took place). Or do the same thing in DataSet Views using window…

@GrantSmith , you'd use the CLI to start the execution of the dataset in Domo. presumably, the trigger would be the completion of the Glue job.

if you don't want to use python you can use the Java CLI, https://domohelp.domo.com/hc/en-us/articles/360043437733-Command-Line-Interface-CLI-Tool#scripting or build an app by sniffing API traffic.

Your CSM will be able to ask internally if a custom connector has been built by Domo before. But @MarkSnodgrass is right, he's listed a bunch of options that'll help you get started now.

what question are you trying to answer in your card? there's no reason to group your data in ETL if in analyzer all you want to do is show sales grouped by client, just toss the client on the X-axis and sum(sale total) on the y-axis.

It's a feature switch. Talk to your CSM or email support@domo.com

the problem with window functions in analyzer in this context is that you MUST show date on the axis in order for the lag function to work. I assume you'd only want to show rows if there were 3 consecutive days of xyz status. if my assumption is correct, you'd want to implement your lag calc in ETL so that you have a…

@Ashwin_SG if you use a recursive dataflow to datestamp your ETL based on when you run the ETL, it can be done... but comes with risks you need to consider. If you assume that you ONLY run your recursive once a day then you kind of defeat the purpose of a recursive (which should allow you to run your dataflow as often as…

you could calculate the metric in a dataset view or magicETL before you get into analyzer but then your beast mode won't respond to page filters. alternatively restructure your data. set up your data such that you have one row per user per rubric. this way you can take the SUM of the denoinator instead of trying to do a…

you can't run count(distinct) in a window function and get the 'correct' results. if you imagine it as a sql query. SELECT rubric, count (distinct user_id) FROM Table GROUP BY rubric this would give you expected results. and this is what a beast mode set up with just count(distinct) without the over clause. when you add…

Many Bar charts in Domo support Trellis (search for trellis, https://domohelp.domo.com/hc/en-us/articles/360043439893-March-2019-Release-1) But, Domo doesn't really support an X axis with two metrics. Or at least. I haven't gotten it to work. I feel like it should be possible though.

@fearlessOwl , Domo is a data lake just like S3 or any other flat file storage system. Domo has a database layer, Adrenaline, similar to most massive distributed parallel (jargon-soup :P ) SQL database databases. It does not support no-sql super well. The question isn't 'can Domo work for a use case' it boils down to how…

@ramoshe if you want categorical values on the X and Y axis you'd need a different chart type. Consider a heat map. or pivot table

It sounds like "if there is text then 1. Cleanest logic will be case when text is not null then 1 else 0 end.

oof... this looks like heartache waiting to happen. i usually recommend that you have one dataset per dashboard. so basically take all your datasets and UNION / APPEND them into one dataset called DASH_.. conform your column names as appropriate, and then you know you're applying filters to the right thing. the way you're…