When trying to test my dashboard I get the following error, “Some BAQs (FreightTrack) missing from current Company. Please contact system administrator.” My BAQ is using a UD table, however I’ve been able to deploy other UD table related BAQs in the past. The dashboard is a simple table output of the BAQ. The BAQ runs without any issues in the BAQ designer. I can provide screenshots if anyone has any suggestions.
Interesting… I only had this happen when I created a BAQ as a user I later deactivated… Then I had to do a “Change Author” on those BAQs - even after I re-activated the User. Other than that, I wouldnt know.
I’m guessing it has something to do with the particular UD table I made, however it was working in an updatable dashboard that I built to update the table. I’ve tried remaking the BAQ from scratch now, as well as export and import, and copy it. So the only thing left must be the table itself, I’m assuming.
It looks like this has to do with us trying to match the InvcDtl.PackNum with the APInvcHead.InvoiceComment fields. For some reason the BAQ will run without an issue in the BAQ designer, and even in the BAQ report designer, but not as a dashboard. We’re doing this to track our actual freight payments with the invoices. I’m guessing we’ll have to find an alternative method for this.
Two things:
-If you create a new global BAQ, is it accessible from other companies?
-Can you check the QueryHdr table? You want to see that there is only one query with that QueryID that is global, shared, and CompanyVisibility set to 10. I’ve seen some funkiness in various versions where something will be mis-toggled here in the table and I need to delete / recreate using the BAQ designer.
The multicompany processes are running and no there are no other QueryIDs with this name, I’ve built most of our queries. The solution ended up being to just make another subquery to use ISNUMERIC within a calculated field instead of using a regular expression in the criteria. I can’t explain why using a regular expression in the criteria caused this error. I’m pretty sure I’ve used that method on other BAQs. Maybe it’s a bug, maybe its Maybelline.
I created 6 dashboards which were a replica of the original with a minor change and I received this error message from 2 of the 6 dashboards. I recreated one of the BAQ’S and it fixed the issue and before redoing the 2nd, I tried refreshing the cache and that corrected the second Dashboard.