This is a shot in the dark, but here we go.
On 1/23/18 I finished up an updatedable dashboard for our field service team that allows them to update a slew of UD fields on the OrderDtl table. They don’t have access to Order Entry otherwise.
This team deals with shipping the final line of our sales orders called “Installation”.
Starting 1/24, they’ve been having we’re anomalies happen in the sales orders like line dates being changed with their name tagged to it and lines being reopened after shipping with their names tagged (change log). I’ve asked them what they are doing and none have any idea. I just found one where the line was reopened 15 minutes ago and the guy claimed he wasn’t using any updateable part of Epicor at that time.
Whether or not that’s truthful, there’s a strong correlation between that new dashboard and these events, but I haven’t ANY idea how or why. I’ve gone though the dashboard myself and updated every field with no affect on the order. Any ideas on how to debug/troubleshoot this that doesn’t involve turning off BPMs/Customizations in our production environment? Turning them off in test would be fine, but I can’t replicate this issue…
Here’s the BAQ showing the lines opening. The first two are project managers, so that’s fine, but the rest are the install guys and you can see it just started happening the day after deploying the new dashboard.
What fields are they updating? I’ve had issues with something similar when
the warehouse on the bin is changed…a couple other fields too that I
don’t recall…
Also, are you allowing them to update lines or releases that are already
closed?
I solves this issue in the upgradable dashboard by adding the release
closed and line closed fields. Sending those with the update fixed that
piece.
The only fields they have access to update are the UD fields I added on the order line.
I’ll try adding the line/rel status to the dashboard to see if that helps.
Adding those fields didn’t seem to help.
In addition, I confirmed that it was coming from that dashboard. I set a BPM to throw up a warning message if the OpenLine field went from FALSE to TRUE and to contact me with what they were doing.
Now I guess the question is why? Why would updating a field like OrderDtl.BluePrint_c cause the line to reopen?
Does any update to a closed line cause this to happen?
Edit: I just tested updating a closed order line in our test environment and it does not reopen it…
I figured out the issue.
The users that use the dashboard leave it open all day, so with that in mind, here’s the scenario:
User1 opens the dashboard in the morning and order number 123456, line 1 is shown as OPEN
Sometime during the day, User2 ships complete 123456, line 1 and the line gets closed
User1, without refreshing the dashboard (so the line still shows OPEN), updates a UD field with some text, or whatever
Upon saving, the UBAQ sees that the dashboard has an open line and the order has a closed line, so it thinks it is an update and pushes it back to the order.
I was finally able to reproduce it myself (10.1.500.16).
Now, this is clearly a bug, but if I were to find a way to allow them to leave their dashboard open all day, could I write my own update routine that updates only the fields I allow? Would that solve the issue in the interim?
A quick test confirms that I can write my own update method and it seems to leave the line closed, so I guess that’s the method I will go until I hear from support.
