We have had numerous instances where the load count or quantity shipped amount was not calculated correctly and displayed in the dispatch order screen.
We have instructed the users to monitor their shipping via the Ticket Inquiry as a backup.
I would like to suggest functionality be added (menu item, button, or both) to the dispatch order screen so a user can click/select it and Apex will scan the tickets for the combination of the date, location ID, dispatch order, customer, order, destination, product, and update the load count and quantity shipped in the dispatch order screen.
This would keep us from providing misinformation to customers as well as over shipping a job.
Ray,
Not exactly. Before, TIS would do SOME work, fail, and retry.
Going forward, TIS will not do ANY work. If the error is a fluke, retry will work and all will be fine. If the error is not a fluke, nothing is done. This prevents a ticket from doing the SOME work listed above again and again if the error keeps occurring on retry.
So, I would say that your original request is normal Apex functionality (and support can help if this isn't happening). Justin's request will be accommodated as we move to future Apex versions. Your last comment would be a failure that needs to be fixed. I wouldn't want a button for people to rely on - I would want it to work right in the first place.
So Chris, if I understand, if an update fails and the transaction is cleared, doesn't that still create the same result.
Let's say there were 4 out of 6 loads shipped. Load 5 fails to update for some reason so the dispatch accumulator isn't updated. Load 6 ships, and it's record updates successfully.
Don't you have the same problem?
It not necessarily a TIS issue because I've seen this at the point of sale a few times as well.
TIS (or Apex Data Import Service) does do this in 4, 5, and 6 if we encounter an error. In our next major version (not yet available) of Apex, we have wrapped these updates (such as the Dispatch) in a transaction. This means if the update fails, the entire transaction is cleared.
Yep, sometimes Ticket Import Service manages to update the dispatch order and then fails to insert the ticket. Subsequent tries the ticket goes in but it updates the dispatch order again getting counts off. We've seen this in Apex 5.0, 5.1, and 6.0 but could never recreate it on our own. Ideally the update to dispatch order wouldn't commit if the ticket insert doesn't happen but at least a nice work around would be to recalculate the dispatch order totals based on the tickets in the back office.
Ray - If a ticket is generated against a dispatch order, the dispatch order should be updated with the quantity and loads shipped automatically (either instant if centrally installed, or if using Data Replication, then whenever the ticket reaches the office).
If this is not occurring, please log a case with our support team to assist.
Agreed