In the E10 BAQ designer, the query only wants to return 10,000 rows. So, it does this and then it says “Query has no more records to return.” (screenshot 1) I know there are more than 10,000 rows and why does it say this, erroneously?
So then I try another run to get more data rows, typing in “Rows to Return” to bring in 25,000 (screenshot 2). Then it says this:
“Query returned 10000 row(s).
Query output was limited by top 25000 record(s).”
WTH?
This is exceptionally annoying! Am I doing something wrong? Is there an override that I am missing on this? How is everyone dealing with this?
Honestly, the key to dealing with query building has everything to do with getting row counts and comparing. Epicor has made this much more difficult in E10 IMO.
The limit works in baq designer itself only, not when query is executed. In case that such many rows were produced by mistake. If you need to see more than 10000 rows in baq designer, there is special execution flag to remove this limitation.
Thanks for tips on removing the row limit. However, I cannot seem to find a way to make this stick. I remove the row limit, set it to true, run query and then get all of my rows. I save the query. I close out of Epicor and come back in and the row limit is there again.
Am I missing something? I sure hope that there is someway to save that when I run a particular query I do not want any row limit on it without having to go and change the query test execution settings each time!
I don’t know about other companies, but our company keeps baq designer under fairly tight security with only developers allowed to create and run BAQs. General users need to use dashboards to get the data. Therefore, the people developing BAQs generally don’t try and return 400,000 rows unless they want them.
This row limitation is used inside BAQ designer only.
It is done for protection, in case something went wrong during query design, like JOIN was not defined, or defined incorrectly, and unreasonable number of rows is returned by mistake.
But when you save this query and run it from dashborad for example, no such limit will be used, you will get all your 400,000 rows if your query returns them, whether you want them or not.
So nothing special need to be done.
When I tried using the special execution flag to remove this limitation (RemoveTestRowLimit), it still limits it to 50,000 returned row results. Is this a BAQ design limitation of 50,000 returned row results or can this be modified?
In regard to getting RemoveTestRowLimit setting to stick after saving, have you checked ‘Persist in Query’ checkbox? This is how I remove the limitation in my BAQs. Once, you have done this there should be no more limitations on your data. I have BAQs that return several hundred thousands of records.
There is an appserver level setting that limits the BAQ results. This server setting overrides the BAQ’s settings unless you do not have a max result setting at the server setting level.
Typically I would do this in a dashboard but the BAQ is being used in a BAQ Quick Search where it limits the returned search results in the quick search base on the BAQ settings.
