Beast Mode Calculation with Data from another Dashboard

DeborahAnderson

I have two questions:

High level - survey data from one Dashboard 1 includes email addresses and a calculated NPS Score from all respondents. Dashboard 2 survey data may include some of the same respondents, identified by the email address. I'd like a Beast Mode Calculation that recognizes all email addresses in Dashboard 1 that are also in Dashboard 2. The Card includes the Full_Question and Survey_Title from Dashboard 1 and the NPS Score as the Value.

In the first attempt, a Beast Mode Calculation was written with a Case Statement that if these respondent emails appear in Dashboard 2 data 'Y' ELSE 'N' but this statement is good for that one instance and there have been more responses since then.

What's is the most efficient way to write a Beast Mode Calculation to compare Dashboard 1 data to Dashboard 2 data and, if the email address appears in both, return the NPS scores in the new card?

Also — What is the best reference book to learn DOMO syntax? I understand the Beast Mode Editor is SQL (I'm not a programmer so I'm trying to learn as I build.). Thank you!

ColemenWilson

The best way to do this would be in an ETL. Because the cards/dashboards have different filtering, it makes the most sense to have two paths from the input dataset in MagicETL: 1. with the filtering/logic from dashboard 1 and 2. with the filtering/logic from dashboard 2. Then you can do an inner join on email which will only keep rows of data where the email is in both subsets of data. Then you can build a card to show NPS scores for emails that are in both subsets.

GrantSmith

Do you have the same dataset powering both Dashboard 1 and Dashboard 2? Domo Dashboard's don't communicate with each other so unless you have the same dataset powering both dashboards you won't be able to do this.

DeborahAnderson

Yes, the same dataset powers both dashboards. Sorry for the oversight.

ColemenWilson

The best way to do this would be in an ETL. Because the cards/dashboards have different filtering, it makes the most sense to have two paths from the input dataset in MagicETL: 1. with the filtering/logic from dashboard 1 and 2. with the filtering/logic from dashboard 2. Then you can do an inner join on email which will only keep rows of data where the email is in both subsets of data. Then you can build a card to show NPS scores for emails that are in both subsets.