I’ve just stumbled upon this error, after aliasing a fair amount of columns in a denormalized table. Any suggestions in this regard?
Did you find a solution for the issue?
I am facing the same problem with a view in MB version 0.30.3.
Oh… It has been so long, I don’t really remember how did I get away from it, really sorry, should have posted the solution here. As far as I remeber, though, it has to do with column names. It is worth trying scan both table and database again, it might help.