Best Of

Re: Add dynamic columns in variable dashboards

Would love to have this feature or a workaround. Having variable has been great and make charts dynamic, and would only make sense if the column title is aligned.

lzhang

1

Re: Add dynamic columns in variable dashboards

This would be extremely helpful for us. Many use cases for this.

MattGo

1

Re: Add dynamic columns in variable dashboards

Great feedback Anna! This is a request we've heard from several customers and we do have a potential solution for this in mind, however, I don't have a specific timeline on when we'll be able to release this yet. Thanks for helping us improve Variables!

Matt Tannyhill

4

Re: Creating in app studio, posting in IOS/Google Play App store

@ColinHaze we are working on that final mile of distribution. A lot of the bones are done but still some final elements to sort out.

BenSchein

2

Re: Dynamic (Contextual) Annotations

This is an awesome idea, sort of like visible alerts providing context!

JasonAltenburg

1

Re: Google Slide Integration

For anyone that can't wait, here's a workaround:

Used the Domo - Excel Integration to access the data in cards
Use Zapier to copy the Excel spreadsheet and convert it to Google Sheets
Use the IMPORTRANGE() formula in a different sheet to copy the information, chart it and then copy those charts or tables into your Google Slide…

After it's set up - Update your Google Slides: 1) Update all the data in your Excel workbook. 2) Hit refresh on the Google Slides (each viz/table, unfortunately)

elicohen

1

Re: Ability to remove unnecessary columns directly in the input DataSet before loading all its rows

Hi! Just wanted to follow up here. I spoke with our engineering team about this idea, and I learned something new about Magic ETL. Apparently, the reason that the feature does not exist is because it's not needed in Magic ETL. Magic already optimizes which columns are loaded into the DataFlow based on whether or not the columns are used throughout the DataFlow. I'm keeping this idea on my list as something to consider making more apparent in the UI, but for now this is already being solved behind the scenes by our DataFlow optimizer for Magic ETL. Let me know if you have any follow-up questions.

AndreaHenderson

2

Re: Show only 2024 costs

@PJG You should be able to replace YEAR(Month,2024) with YEAR(Month) = 2024 to get the results you need since the YEAR function returns the year of the date field in parenthesis and you only want to consider rows where the year is 2024.

MichelleH

1

Re: Count Distinct with Or Case Statement in Beast Mode

Sorry, I tried to mask the data a little at first, but I did update your formula with the correct fields.

I tweaked the formula a bit and I got the result I expected:

IFNULL(COUNT(CASE WHEN Product Name = 'Washington Summit - Guest/Spouse Registration' THEN Registration ID END),0)
+
IFNULL(COUNT(distinct Registration Id),0)

Thank you so much for your help!

Cfunk

1

Re: Multiple case statements

@NFerna For the beast mode part of your question, it would be something like this:

CASE WHEN 'Achieved Value' >= 'Benchmark Value' THEN 'PASS' ELSE 'FAIL' END

Assuming your data is set up so that it's Fruit, Achieved Value, Benchmark Value, this will go through and for each fruit/row and compare Achieved Value and Benchmark Value.

For your color coding question, to color individual cells, you would need to use an HTML table and some HTML code, but if you were fine highlighting the entire row red or green, you can use the beast mode above and add it to your table, then hide it. Then set up your color properties so that if the value is 'Pass' then it highlights the row green and if it's 'Fail', then highlight the row red.

RobSomers

1