Wappler Version: 5.8.2
Operating System : Windows 11
Server Model: node
Database Type: postgres
Hosting Type: N/A
Clicking OK should save the changes
Nothing happens. The OK button does not appear to do anything and there’s no indication of an error.
Hey @kfawcett,
Can you please try:
1)Define an alias name for your join table
2)Add one by one the columns you need instead of Contact_Email.*
Thanks @famousmag! Ultimately my issue was trying to use ‘contains’ instead of ‘equal’ in my condition, but I came across this bug/defect before fixing the Simple query condition.
If the Alias is required, then I would hope the modal would validate that and throw a warning that it’s needed.
No, I don’t think that join modal is validating and throughing an error… You will just find it out on the way when getting no results or error when it runs.
Anyway, 1) I don’t know if you had to use an alias because I didn’t know you had any column names with same name and 2) I have seen a few issues when using . * instead of adding the columns individually.
So, you managed to click the ok and save your query after changing ‘contains’ to ‘equal to’ in your condition?
No, I canceled out of the modal and switched back from Custom to Simple query builder, then changed the condition from “contains” to “equal”.
This was the final setup.
Now you lost me hahaha
Your video was on a simple query…
Anyway, glad you found where the mistake was in your setup
Cheers 
Doh! Indeed it was. I was switching between the two types to see if I was encountering it on both and forgot what I recorded. 
Hey @kfawcett,
Thank God I had paid attention to what you said here, otherwise I would be banging my head on the wall with this one.
I just came across that case and I can confirm for sure that it is a bug…
When working on the database query builder IF A CONDITION IS ALREADY SET and you just switch from simple to custom builder then no other join can be set (even if you switch back to simple without saving the custom query).
Cannot click OK on TABLE OPTIONS JOIN popup panel and save the JOIN).
The only workaround is to just delete any condition you have set, only then new joins can be set properly.
This bug apperas ONLY IF WE SWITCH FROM SIMPLE TO CUSTOM BUILDER and back again to simple.
Maybe @Teodor can confirm that also and try to fix that
