Got a Ghost table in my BAQ UD table seperated from main table

[Hogardy (Pierre Hogue)]

it is a simple BAQ. Because of it my Dashboard takes soooo long it never ends and it affected all the users. Had to kill my Epicor.

Why does it do this ? I redid twice and got the same issue…

Thanks.
Pierre

[jwphillips (Jonathan Phillips)]

There is discussion on this issue here:

_UD tables split off in BAQ

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 decided to add the separate table like this and not link it. (If I do link it and save, it simply deletes the link) This causes what should have a single result return to return thousands (one line for every line in PartLot_UD) I had two separate queries do it on me currently on…

The way I work around it is to use the Kinetic version of the BAQ designer.
If it’s already been saved with this defect - you might have to re-create the BAQ from zero. I haven’t heard of anyone re-joining these linked tables.

[MLamkin (Marjorie Lamkin)]

I’ve seen that happen without Kinetic a few times (we’re not on Kinetic yet), when that happens, I have to delete the table (and the ghost _UD table) from the BAQ and re-add it. Usually that fixes it.

[Hogardy (Pierre Hogue)]

Yeah I did this once and it came back. I followed the use of the Kinetic (on the web) to redo my BAQ and that worked. for now…