Answer
Since Data Source Designer only supports a single view/query shape and can't express a raw INTERSECT directly, restructure the logic as a pair of EXISTS subqueries against separately-aliased copies of the same underlying view instead, joined back to your main query on the shared key columns — each EXISTS subquery checks one of your two independent condition sets, and requiring both EXISTS clauses to be true reproduces the same filtering effect an INTERSECT would give you, but in a form Data Source Designer's single-view-plus-conditions structure can actually accept. Alternatively, if you'd rather keep the raw INTERSECT SQL as-is, building it into a proper database view or an IAL first and then referencing that single view/IAL from the Lobby Data Source sidesteps the limitation entirely.