keeeirs10

I've reached out to Domo several times, and they are not able to assist because of the nature of the connector (Amazon Athena). They say to reach out to Amazon for assistance, but we have no business connections to Amazon on this particular team. Any other ideas? I appreciate the brainstorming!

Hi @amehdad, Thanks for your response! It seems for your link, I would need access to the old ownership credentials. Because the analyst is no longer with us, there is no way for me to do that.

Thanks for the input Grant! See above for the solution lol.

UPDATE: I am in fact a Dummy because I was selecting the wrong transformed dataset in my output. All is well, and the column is now appearing!

I updated my output dataset query to make it simple! Now I have the Dummy variable pulled in, but the logic built out in the LEFT JOIN is applying to some rows, but not all in the final output dataset. Any ideas?

Updated Query (also not working properly): SELECT A.`Posting Title`, A.`Weekly Reporting Date`, A.`Weekly Report Stage`, A.`Funnel Stage`, A.`Candidate Link`, A.`Origin`, A.`Department`, A.`Days in Stage`, A.`Days to Hire`, A.`Days to Archive`, A.`Offer Acceptance Date`, A.`Candidate Journey Start Date`, A.`Event Date`,…

No worries! The Dummy column does not show up when I run the ETL and view the dataset output. When I am transforming and previewing the output when editing my dataflow with MySQL, the column is there.

It is returning every column except for the Dummy column! The single ticks did not work sadly. Even weirder, The logic built out in the LEFT JOIN is applying to some candidates but not all, even though their names appear on the lever_inactive_report table. Any thoughts??