We’ve had a bit of a gremlin in our sales order line costs since we moved to Kinetic this year, but have only put it down to one user and an updateable dashboard.
The user in question is updating some UD fields on the SO release, and as a result the unit costs on the line are being rounded down (or up) at the time the UD field is saved.
It’s a bit of a mystery, as the BAQ behind that dashboard app isn’t set to update anything other that the SO release UD fields…
Before I put in a ticket to Epicor, just wanted to see if anyone else had noticed, as it may have been patched in a later update.
For context below, we changed it back the same day as it was picked up at invoicing when the invoice line cost didn’t match our internal job UD field cost tracking system.
I’ve never had that happen in our environment that I’m aware of. It sounds like you are saying it doesn’t happen in the Sales Order Entry app, but it does in your updatable dashboard. You might need to share screenshots of how the BAQ update is set up.
I don’t know how this could even be related, but I’ll mention it just in case it somehow is the culprit.
After we upgraded to 2025.1.13, we had a buyer who noticed that whenever he created a PO, entered information, and then saved it that the PO Terms were being cleared out. We traced the root cause to Field Security on the Terms that since all buyers were set to the default Read Only security it behaved that way. (We were already aware of the Field Security bug in Kinetic UI that the field doesn’t actually take on the security properties, like Read Only.)
I’ll see what I can post up, but the BAQ is pretty much the same as our E10 environment, I just re-created the dashboard in Kinetic with a few other publish/subscribe BAQs for job progress and comment data.
Hi Adam
Did you ever determine if the BAQ was the culprit? We just discovered that we have the same problem with unit costs rounding tied to 3 specific users when we had a uBAQ update different fields on the Sales Order.
I created a change log dashboard for checking those entries so we could at least spot them a bit earlier.
I have also since re-created the affected dashboard that may have been causing it as App studio decided to lock any repositioning of panel card grids/stacks.
Just an FYI on this. Epicors version of the BOs (when you just use the check box to use their BO to update something) will update everything in the grid whether or not you have updateable checked or not. Normally this doesn’t matter as what you pulled is the same value. However if your value is stale (someone else changed it) or of it’s rounded in this case, Epicor makes the change, as the OP is seeing. That’s one of the reasons I pretty much never use Epicors out of the box BO like that and roll my own code, still using their BOs but explicitly setting the fields that I want to change to make sure I don’t get any fun surprises like that.
