If this has already been figured out, I missed the memo. I’m sure many of us have been plagued by the random, but consequential, _UD table that sometimes comes into the classic BAQs. Just yesterday I created a very simple BAQ as part of an automated report; just saved it and went on my way. Today I…

Is it this? [image] _UD tables split off in BAQ Kinetic ERP In Kinetic, I have had quite a few baqs break and do this: [image] The only way to fix it is to delete the query and start over. Any idea what causes it to randomly do this? The original had only Erp.PartLot…

It’s the same issue, but I didn’t see how to replicate it in there either. Mostly just people having similar issues and discussing how to work around the issue when it came up or what they thought could have been causing it. The queries are both newly generated in my example, so nothing relating to…

It’s almost like the BAQ you deleted hadn’t completely been cleared out yet so caused an issue when you created a new one with the same name, table, and field name. If you waited a minute or two would it do the same? Does closing the BAQ designer and reopening give the same result? Have you enabl…

That’s fair, I should have closed the screen and used a different name in my posted example. I just booted Epicor fresh today with a new BAQ name and was able to successfully replicate the _UD table on the first try. I hadn’t traced it yet, which is a failure on my part as an Epicor user. I just tr…

Interesting. I have not been able to replicate this in kinetic BAQ designer in 25.2.16 but I only just tried it just now.

I feel the way the BAQ is first created in Kinetic lends itself to avoiding this issue. I also couldn’t replicate it in Kinetic, so hopefully this specific scenario will be a thing of the past.

Always wondered about this, it’s so annoying when it happens and I have rework that table in the BAQ.

Classic Epicor BAQ - Black Magic _UD Table

Off Topic

JasonMcD (Jason McDermott) April 23, 2026, 6:49pm 2

Is it this?