I have two individual datasets (SPICE), one from Athena and other from Postgres already imported. They do have a joining criteria field , but I do not see the ‘Join Datasets’ option anywhere. Could anyone please help with this.
Hi @mercynithya.jothiraj and welcome to the Quick Suite Community!
Quick Suite recently rolled out a new data preparation tool that has a different path to joining datasets; since I’m unaware if you’re utilizing the new view or the ‘legacy’ view, I’ll include directions to both below:
New Data Preparation View:
You’ll see various options in the menu on the left side of the screen; select the ‘Join’ option:
In the old ‘Legacy’ Version:
From within the ‘Edit Dataset’ option, you’ll see a button in the top right to ‘Add Data’, add the second dataset that you’d like to join with the original. Once completed, you’ll now see both datasets present with circles in between them:
Next, click on the 2 circles in the middle and you’ll see a prompt pop up on the bottom of the page that asks how you’d like to configure the join.
Let me know if you have any additional questions
1 Like
Thank you Brett, I don’t have the new version yet. With old, I’m facing this issue - the Add data option shows all of the datasets but am unable to choose the ‘Postgres’ option as it’s disabled, PFA the screenshot. Any idea why is it so or what can be done to select it.
Thanks.
I checked in the new version as well, it shows all of the source datasets inactive (unable to select any):
@mercynithya.jothiraj In the new experience, we currently do not support referencing datasets created in the legacy experience. This is because the new experience offers net new features (like the ability to use dataset as source up to 10 levels in new vs 3 levels in legacy) so we currently expect the lineage to be in the same experience. Now if you want to reference parent datasets from the legacy experience, you can Switch back to legacy experience by creating a new dataset and clicking this button on the top right of the data prep page.
Going forward, we plan to support this use case of referencing parent datasets from the legacy experience.