jaeW_at_Onyx Coach

Oh, noticing that the series maintains their color across the X axis (mobiles, tablets) etc. that's an interesting feature.

you would have to unpivot your metrics into rows instead of multiple metrics in columns. then you could apply a case statement based on the metric label for how they group.

use @MarkSnodgrass recommendation plus partitioning in Magic

@SlickVic i'm pretty sure this is what the PDP utility in the Governance Toolkit or Java PDP Utility do.

it is possible. you'll notice that in your screenshot the name of the dataset is aliasedfrom EmploymentCycleUpgraded to employmentcycleupgraded. if you wanted to swap in a new dataset to your ETL, just add it in and then change the alias.

@ST_-Superman-_ i don't want to work through converting pseudo code to real code but i wonder if you could do math along the lines of do the datetime diff. between start_date and close_date. test if the day of week for CLOSE_DATE is < START_DATE (if it is we know there was a weekend in between and we have to subtract 48…

@swagner take a look at FIXED Functions

i could be mistaken, but i believe the env object should include all dashboard filter settings.

@SlickVic check out this article: "Pulling Parameters from the Environment"

I know for a fact they are working on a project in that space. But TBF the query API DOES work and hasn't changed.

The webinar recording is live! We put a ton of Learnings and Resources here. Video Tutorial https://www.youtube.com/watch?v=15nXTopnRcI

@JenniferGibson , @MichelleH used Redshift not Magic to get the job done. Beast Modes run on Adrenaline (Domo's database layer), Magic runs in a different environment. Even though many of the functions use similar syntax there is not always 1:1 parity in implemented functions, AND they are not processed in the same space.…

@NoahFinberg I LOVE THIS!!!

@andersson_morales19 i think you need CASE and aggregation. so something like CASE WHEN count(column) + count(other_colum) <= 3 AND count(column_3) + count(column_7) <= 3 THEN ... WHEN count(column) + count(other_colum) <= 3 AND count(column_3) + count(column_7) <= 3 THEN ... END

@FXM32 Domo does retain dataset history in Vault, but that's supposed to be a recovery tool not dataset snapshots that end users can flip between. Given that your "freezing mechanism" should tightly align with business logic, it makes sense that you should apply that business logic as an artificat in your dataset that you…

@andersson_morales19 post a sample of your dataset please.

@SaloniShah post a picture of what you're currently doing / strugglign with.

for the original use case using a formula tile and COALESCE() will be a much cleaner (and recycle-able) design pattern in other parts of the platform. I particularly enjoy the fact that COALESCE is a SQL standard and not bespoke to MAGIC ETL. My challenge with setting data types in the INPUT dataset is last time i looked…

@SaloniShah is the data actually duplicated in your dataset? If so that's probably something to be concerned about if it's not intentional. Take a look at the connector that's bringing in the data, is it set to APPEND or REPLACE? Is the data actually duplicated or are just a few rows duplicates? If you run the connector…

@damen to be more specific, you should (probably) impelment the metric @RobSomers is describing as a Beast Mode in Analyzer. Typically we recommend against preaggregating datasets in ETL if we don't have to.

@trafalger I do wonder if you add the index in the UI if the data is indexed as it's being loaded into the table, or if if the index is added after CREATE TABLE AS SELECT ... So i i guess if you wanted to be REALLY fancy you would CREATE TABLE, ALTER TABLE and then load data... but then the table doesn't appear in the UI.