Client Org row limit on Advanced Subqueries when using Data Source Substitution
This is an addendum to https://community.yellowfinbi.com/ticket/15717, where row limits were being applied across subqueries.
We've now applied the patch (and more), and it's worked for simple sub-queries, however the issue is still occurring on advanced subqueries using a nominally 'different' source, even though - importantly - that different source is actually using the same database as the master query. (It's a source in the parent org, querying back into the client org's database.)
The row limit on the master is applied to the subquery, even if both the master source and subquery source have no row limits on them (and it is only set in the master query).
I've ensured the client org and parent org sources both use the same type of connection (Microsoft SQL server) and driver.
Is this expected, because it is querying via a different source to the same database, or is this a defect?