Confirmed this happened with a regular BAQ in the Classic screen.
After seeing the tables split in the Classic screen, I closed (without saving) and opened it in the Kinetic screen - and it looks correct, no table split.
Iâve had this a few times. The BAQ seems fine until you open it back up in the BAQ Editor. I have not observed this in 2023.1 but it definitely happened in 10.2.700.
If you close the BAQ without saving, the BAQ still works fine. Itâs as if the editor itself is splitting the UD Table out.
I have noticed that it seems to be related to calculated fields. If you donât use calculated fields referencing _c fields, the tables never get split up (that Iâve seen). However, they donât always get split when you do have UD Fields.
Maybe only every time that you reference a UD field?
The test I just ran had no calculated fields, and the tables split.
Damn, there goes that theory.
As far as the question as to when they broke, the other person was using a customization which referenced the BAQ and pulled info into it. They were never in the actual BAQ designer.
I reference UD fields on nearly all of our BAQs as our version is highly customized.
They were never in the actual BAQ designer.
Then they donât save BAQ and it wonât be broken after that