Hi all,
I have a dashboard that relies on a couple of external BAQs and many calculated fields to populate some data in a dashboard customization. This was working fine since it’s inception about a year ago, but when I went to run it today, I am unable to get the External BAQ to run. I click “Test connection” and it works fine. Additionally, the view from which I am pulling will run in SSMS.
Granted this BAQ is slow due to all of the calculated fields it’s performing, but I would think that it should still be able to run as it did in the past.
Below is my error message:
Any help would be appreciated, otherwise I’ll probably have to rebuild this thing from the ground up.
In the “Distribution” tab for your External Datasource, there is a Query Execution Timeout setting. The value of “0” should mean no timeout, but it doesn’t work. If you change the setting to 999999999, your external BAQ should complete.
Hmm, well it didn’t time up, but it still did not return any data, it just sat there forever!
This will sound really stupid, but if it works for you, I’ll at least feel less crazy. I had a similar issue where an sp_who2 on SQL would show the query running for hours, even though it should finish in like 30 seconds if run from SSMS.
Try changing the BAQ to select Top 100 Percent instead of “All Records”. For some reason, that prevented Epicor from hanging forever on the dashboard query.
I’m curious if you see the same thing. I haven’t called Epicor about this one because it sounds so ludicrous 
I’ll try this tomorrow, thanks for the responses! Much appreciated
Hey Aron,
The default ConnectionTimeOut property of external BAQ is 30 seconds. You cannot modify it on the fly. So if want to work it bfore 30 seconds, you should have to minimize the execution time in SSMS view. You can do that by reducing the criteria (conditions), joins while selecting the records from SSMS tables.
If you succeed to do that, you do can any thing in BAQ designer, no matter if there are so many Calculated fields.
In your case,BAQ is taking 30.106 seconds,means little modification can change the picture.
Hope it will help you.
Thanks Prakash. The view is locked as it was developed by another person, but I will look into that.
Interestingly, this morning I was able to run the query without issue. I wonder if because more users are active later in the day on the SQL server, it would slow down the query I was trying to run.
