If you need that criteria of Customer1.CreditHold = 1, you can take it off the Customer1 table, and add it as a SubQuery Criteria. That should move it down into the WHERE clause.
When you upgrade some of the datalink become unlinked in the BAQ. The quick and simple solution is to open the BAQ and resave it. This has worked for me each time we upgrade.
I’m running into this situation for the first time and am stumped…
BAQ runs in ~3 seconds for some users and times out after 30 seconds for others. Maybe 10 people have tried it and half of them time out, other half are fine. Single Company, on prem, v10.2.700, sql server 2019. BAQ is not updateable, Cross-company is not checked, All Companies is checked.
I looked at Territories, WorkForce, Buyer, User, Employee setup and can’t find any rhyme or reason to explain who is slow and who is fast. We’re pretty sure we’ve ruled out client-side variables; it’s gotta be something inside Epicor.
BAQ has 3 tables in the upper level (Part, PartPlant, Vendor) and there are 3 subqueries left joined to PartPlant. Sub1 has PartWhse and Warehse, Sub2 has PODetail and PORel, Sub3 has TFOrdDtl. There is criteria for plant = currentPlant on several tables, both upper level tables and subquery tables.
Any ideas?
anybody tried running field permission reports on the display or join fields with this kind of issue? I had one that didn’t display the usual warning in BAQ analyse, but the report (can’t remember its real name) on field-specific security turned up an obscure deny permission. Nobody admits to having changed it, but when we went live a dozen persons could have.