Hi, wondering if you anybody ot this behaviour after updating Kinetic.
We are testing to migrate to Kinetic 2025.1 and we that some BAQs were returning no records along with errors on some customizations.
After a little digging we see that some fields are missing in the tables. So far they are CustID and CustName from table JobHead.
These are base fields from Epicor, no UD. We weren’t expecting Epicor to delete columns from their tables with the obvious implication of breaking BAQs and customizations.
Did we found a bug? Or is this “normal” after updates?
I have seen something similar on CSF, but that is specific code that changes a lot, so it might be understandable, but base tables like JobHead?
CustID and CustName, as far as i am aware, have never been part of the Job Head table (I have checked both E9 and various versions of Kinetic we have). Are you sure that you have not had any customisations done in your current system, either by EPICOR or internally, that would have added these to your current system?
2 Likes
Those fields were removed in 2024.1: Epicor update Broke BAQ - #7 by Jeff22
1 Like
I was about to say @Daniel_White, they indeed were at one point.
When were they added then? Certainly not in EPICOR 9 and we had to create our own custom fields when we moved to 2023.1 to deal with some customisations we had in E9.
I feel like I had someone using it as well and it surprised me at the time, but that thread above details it.
I’m with you- surprised to see it somewhere out there. We have a custom field too.
They were there in 10.1.500 when we implemented, back on 2018,I already reported to Epicor to see if this was a bug(which it seems it wasn’t) so breaking code and BAQs can be expected in further updates.
Still waiting the confirmation from support. But at least, I now know it wasn’t a bug on our upgrade.
1 Like
Ah that could be why i missed it. I was only using 10 briefly in my previous company and in my current we have migrated from 9 to 2024.
1 Like