jaeW_at_Onyx Coach

thanks for the shoutout @mhouston Strong agree to the UNION approach instead of JOIN. @utkarsh it looks like your dataset 2 needs some sort of date column. if each month everyone has the same budget, then duplicate the rows of Input 2 once for each month and add the end_of_month_date column as @GrantSmith describes before…

@swagner why didn't you @ mention me? sorry so late to the party! sum(sum(1)) over ( partition by branch, item order by receipt date desc) shoudl work i believe.

Product Feedback / IDEA added here -- https://dojo.domo.com/main/discussion/55706/join-on-like-and-between-in-magic-2-0/p1?new=1

Product Feedback / IDEA added here -- https://dojo.domo.com/main/discussion/55706/join-on-like-and-between-in-magic-2-0/p1?new=1

@jmmc @GrantSmith is spot on with his advice with one small addendum. If you can perform your JOIN in a Dataset View (which is basically Fusions 2.0 so ... ignore fusions) then, assuming your VIEW can return a result within 1 minute (processing requirement imposed on VIEWS / Adrenaline) then you should see significant…

In DP22 Domo released the ability to schedule Jupyter Notebooks just like any other dataflow. Definitely worth checking out! https://domohelp.domo.com/hc/en-us/articles/360047400753-Jupyter-Workspaces#4.4.

UPDATE -- @user09644 this feature was released at DP22. It's now possible (and frankly IMHO there's no reason to use Python or R tiles in Magic Dataflows anymore! https://domohelp.domo.com/hc/en-us/articles/360047400753-Jupyter-Workspaces#4.4.

@Jmoreno I'm going to create product feedback for this here: https://dojo.domo.com/main/discussion/55701/domo-certification-progress-and-community-engagement-datasets/p1?new=1 feel freet o upvote. I know my org needs it.

@JunkDoom have a close look at Partitioning. Many Domo connectors are starting to support partition schemes based on Date. If your data is not partitioned by Date you can use the CLI to create your own partition tags as you upload data. the in-Domo ETL version of "Partitioning" can be recreated with Recursive Dataflows.…

Rumor has it that Workflows will have the ability to implement FOR WHILE loops ; however, workflows are not intended to be substitutes for ETL, so again, ideal state would be to be able to implement loop structures into ETL With CTEs I can't see the need in SQL dataflows yet; but then we all know that CURSORs are not great…

Oleksi framed the issue as: "Currently there's a 1 minute maximum to query run time in Adrenaline. If the datasetview runs more it fails, that's why we need to ask to increase that limit. AS for example group by on 500M rows View is failing" I believe this issue is resolved by SQL engineers optimizing the dataset for…

@RobSomers unfortunately, "The Magic ETL is just a visual representation of SQl" this is not an accurate statement and is potentially misleading. Although Magic ETL transforms borrow heavily from transforms we are accustomed to performing in SQL and even the Formula Tile allows you to write functions borrowed from MySQL,…

looks like someone was asking about this back in 2018.

@Jmoreno if you are using the full auth snippet I provided, you have to use your Domo password (not your identity provider password) AND you have to have direct sign on enabled. If you are not able to use that approach, @GrantSmith 's response was correct, you have to authenticate using x-domo-developer-token…

see my post at the bottom. you can't write the CASE statement AFTER aggregation and expect a result. COUNT(DISTINCT CASE when `Revenue Amount (Global)` > 100000 then `Contact ID` END) this might work if your revenue is a column on the dataset

you can write formulas in the GROUP BY tile too. but as @GrantSmith pointed out, a Formula tile cannot have any aggregations (MAX, SUM, COUNT)

usually if the dataflow isn't bugged (as @GrantSmith suggested), if the dataflow won't run it's b/c it's already running.

@BrianRowe / @GrantSmith Neither of you are 'wrong' but it is inaccurate to say "it doesn't do average of an average" i'd agree "it's misleading to take the average of an average" but it can be done. this distinction is important because in many situations, new developers get tripped up about logic that's applied before or…

it depends on how your data is shaped but either you'll define a series as the secondary axis or i believe you can pass a measure as the secondary axis.

Adrenaline is a homegrown sql database. It doesn't have a 'version' per se. Syntax will most closely resemble the syntax you're accustomed to using in BeastModes and the formula tile in Magic 2.0 What problem are you trying to solve?

https://domohelp.domo.com/hc/en-us/articles/360043436773-Microsoft-Sharepoint-Online-REST-Connector

@anthdell Magic 2 JOINs are case sensitive ... which can be annoying if you're coming from a SQL impelmentation that had different collation rules. another gotcha can be hidden spaces (make sure to trim and lowercase before the join.)

it might be a bug, but also, simplify your process. if the criteria for a pdp policy is based on an amalgamation of 18 columns, consider creating a column that represents the output of considering those 18 columns and key the policy off of a simplified column. this will allow you to separate 'bugs with pdp utility' versus…

@thwartted if you can't transform the data take a look at period over period charts or flexline charts

@MarkSnodgrass i love that! but it'd only work if you kept customer_id on the axis. so you'd see each customer and then be able to filter or see if they have the count = 3. but if you just wanted one number it wouldn't work. at this point it may be easiest to make a summary dataset with the granularity of one row per user…

@hello_data if you're getting into scripting outside of Domo I'd take a look at the Java CLI in addition to rdomo or pydomo. this might be a clean low code way to push data into Domo https://www.youtube.com/watch?v=kHSeSbSFS1Q I don't recall if the UPSERT example worked in the end but it does give you an idea of how you…

@EWold what's the problem you're trying to solve? It doesn't make sense to me (yet) to combine a lecture and lab (without adding columns) it seems like you'd be assuming that a student cannot attend a lecture and NOT a lab or vice versa. or perhaps get registered for different sections that usually aren't paired together,…

@Airwon48, no your description made sense. you currently can't have a filter enabled (which excludes data) and then filter on excluded data. That's why you'd use the default page filter, sorry forgot to link the KB, https://domohelp.domo.com/hc/en-us/articles/360042923914-Applying-Page-Level-Filters-with-Filter-Views users…

In a word, it's not possible. Domo does not support filtering across rows for "or" What you could do is create a pipe delimited list for all the datapoints per user eg. AllPoints = 'green|circle' then when you filter you can search for "green" and then search for "circle" and choose the one that overlaps. if you have too…

When you configure a card, if you're displaying multiple dates on the axis, you can choose which column you filter on based on the Date Range Field. Typically the field will default to the first field you show on the card.