This is an old post, so I'm not sure if @christoff_brand has been able to resolve this.
@ninja
Do you really need User-Input type (Query) to display you more than 10,000 results? Its improbable that you would look through all those 20,000 for 30,000 rows one by one and chose the right one, would you?
Mostly you'll start typing in the User-input to match the desired row. So lets do that in our query itself.
Have an additional where clause in your query which will do this filtering for you
Example:
My original query
===
SELECT
wfa_server.hostName, wfa_server.ipv4Address
FROM
wfa_servers.wfa_server
====
Assume this returns 20,000 rows. My desired row is with hostName is : wfa_sinhaa
WFA won't display those 20,000 rows, and neither will I read through all those rows to find wfa_sinhaa and select it. It just won't happen.
So I just modify my query giving anadditional where clause and get another User Input. See how
====
SELECT
wfa_server.hostName, wfa_server.ipv4Address
FROM
wfa_servers.wfa_server
WHERE wfa_server.hostName LIKE '%${wfa_name}%'
====
Now my workflow will have another string User-Input wfa_name. Now During execution my Query will only get executed based on what I provide in wfa_name. So this allows me to easily filter the unwanted rows. And most likely the result is going to be within 10K.
Even if its not, I can narrow down query with additional clauses. See below.
====
SELECT
wfa_server.hostName, wfa_server.ipv4Address FROM
wfa_servers.wfa_server
Where wfa_server.hostName LIKE '%${wfa_name}%'
AND
wfa_server.ipv4Address LIKE '%${wfa_ip}%'
===
So there is no need to have 30,000 rows to select from.
sinhaa
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.