Can confirm that the wrong columns still show up in 2024.2 I’ll check if that PRB is suposed to be included and raise as an issue there too.
5 Likes
They took away the 
and the 
.
1 Like
1 Like
We could probably use 
1 Like
I’m sorry to re-open this can of worms, but I’ve read through everything in this post and I’m struggling to get my BAQ deployed in a Kinetic Dashboard. My BAQ is returning JobOps with a column for the Next Operation. I used examples from another post to create the BAQ. And have used this example a number of times for various needs. https://www.epiusers.help/t/baq-to-find-next-operation/104607/13
I can use the Classic Dashboard tool to add the BAQ and view it in classic, but the grid will not load when i preview kinetic App. I tried creating the app using the wizard and as this post suggested made sure the subquery field (that gets the next op) is not selected as one of the columns.
I can run/test the BAQ successfully in both classic and kinetic.
My last attempt at getting something pushed out for the operations team to use this tool was to add the BAQ Grid to the kinetic home page. That won’t load either. Why would it load as test from the BAQ (both classic and kinetic BAQ Designer) but not in the BAQ grid?
Is there anyway to publish this as a classic Dashboard so they can use it? I no longer have the option in menu maintenance to publish as a classic dashboard. So I finally resorted to adding the BAQ to an already existing Classic DB. This is not the best answer so i’d really like to understand how I can deploy this BAQ/Dashboard as a Kinetic AP. Any and all help is appreciated!
FYI we are Pub/Gov Cloud and had production update 2024.1.15 applied over the weekend. I’ve not seen this behavior previous to this and I’ve deployed a bunch of Kinetic Dashboards with Inner Sub/CTE and Union Queries in the last months.