I can now see that this is created as a result of having this related table in the filter. Is there a way to just have it look at the related table?  And not create something like below. Would a select from the related table with perhaps an exist in context table be more performant? 

SELECT t1.1natureza_juridica], t1.1lookup_955552244]
FROM 
(
SELECT t1.1natureza_juridica], t1.1lookup_955552244]
FROM 
(
SELECT t1.1ativo], t1.1natureza_juridica], t2.2descricao] AS Slookup_955552244]
FROM Mempresa_view] t1
LEFT OUTER JOIN Nnatureza_juridica] t2
 ON t1.1natureza_juridica] = t2.2natureza_juridica]
) t1
WHERE t1.1ativo] = @p0
GROUP BY t1.1natureza_juridica], t1.1lookup_955552244]
) t1
ORDER BY t1.1lookup_955552244] ASC

Hi Freddy,

It seems like we missed the question, is this still a relevant challenge or have you solved it? I do feel like, if this doesn’t function the way you have set it up, it's either a bug (if it worked before but not anymore) or an idea.

Still relevant.. And don't think you can set this up. Apparently it's the way it's engineered by Thinkwise. But it should be an option to use the combo/REF or to only show the values in the result-set (what it is now)…  

If you start the screen with empty filter, you have no options to choose from at the moment. So it's a bug from one side, and an idea from the other :)

I think this is an idea to create