We did careful testing of our critical dashboard in the Pilot environment prior to the leap to Kinetic this past weekend. This dashboard has about 10 subqueries and has been running on the cloud for about six years. What could go wrong?
The dashboard is important because we run it to determine critical shipment information that is passed back to a supplier of ours. The information is required to be submitted by the 9th of the month for the prior month’s shipments.
We tried on June 4th in our Production Cloud environment and the dashboard/BAQ would not run. Thinking it was an issue with pre-cutover activities, we checked in Pilot and it ran just fine.
Monday morning went in to run the BAQ and no results except for an error code.
Copied the BAQ from Pilot into Production - still no luck.
Ran into @timshuwy at the NW EUG meeting - he gave me some really good advice.
Applied his steps…
Spend some time tuning the BAQ thinking maybe it was a speed issue. - no luck.
Sent in a ticket to support - EpicCare was right on it, logged into our systems and got the same results. BAQ runs in Pilot not in Production.
Recommended this knowledge link.
Knowledge Article KB0049808 - BAQ slow performance
Following the steps I put in “QueryOldCompanySecurity” in the execution parameters.
Another workaround if the issue started happening since a new upgrade is to revert back to the previous BAQ execution method for older versions. To do this, click on Actions > Execution Settings and then add a new line in this window and select any option here, then select it and manually edit it to say “QueryOldCompanySecurity” and set the value to “true” and enable the Persist on Query checkbox, then click OK.
This worked and we were able to get the report out (one day late)
Still curious why it would run in Pilot and not Production. I thought that these are identical environments if that is what we just spent the last six weeks testing Kinetics in?
Right now I am just happy that the fix works.