I've been using SQL to do some joins, however I've found it to be rather inconsistent at dashboard level after I save the table. Either 1* it will allow me to filter the table by any of the columns. Or 2* which is currently happening without fail in recent attempts, it will only allow me to filter by columns based on 'name' or 'id'. Even with these 'name' and 'id' filters, they do not work consistently and the drop down options on the filters don't come up, whereas they are still there for the original table.
This is causing issues as the dashboard is designed to be interactive for users.
I cannot use the standard join method for all of my joins as they are not all as simple.
However in looking for the error, I've now found that turning any standard table I have into an SQL and back has the same effect.
2* has been the only outcome since updates on Tuesday.
Are there any alternative methods to achieve what I want? As I've read through the linked post and there appears to be no solution. I've also previously had it working but inconsistently.
@Matt1
Post "Diagnostic Info" from Admin > Troubleshooting.
Which version did you upgrade from?
We're working on a lot of filter fixes for the upcoming 0.42, it's still a little too soon to say what will be fixed by this yet. But no, there's currently no workaround.
on the first post