Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

Categories

Is it possible to identify any/all ERROR items in a BATCH 'Discovery of Trackables'?

+1 vote
522 views
Before the recent changes by Project-GC to its 'Discover Trackables' tool, it was possible to identify the tracking number(s) on any item(s) that failed to go through due to an incorrect tracking number being used - in other words all ERROR items could be individually identified.

With the letter 'I' often being confused with the number '1', 'O' being confused with '0',  'S' being confused with '5', 'B' being confused for '8', etc... incorrect tracking numbers can easily be included in a 'Discover Trackables' batch run.

Previously, when it was possible to identify the ERROR items, a second or third attempt could be made by trying 'alternative combinations' of suspect characters, which often corrected the problem and enabled the trackable to be successfully logged as 'Discovered'.

Now, all that you know is the number of ERRORs in a batch but NOT which ones in the batch actually failed to go through.

Can this feature please be re-introduced? It was very helpful in the past! Thanks.
in Feature requests by Halywid Hunters (210 points)
edited by Halywid Hunters
Is it actually possible for tracking numbers to have those letters in (gccodes can't)? If not perhaps project-gc should autoconvert them ie I is automatically converted to 1.
by mole125 (Expert) (21.1k points)
Yes it is!

Even worse, I have at least two tracking numbers with 'mixed' characters. One contains both the letter 'O' and the number '0', the other contains both the letter 'I' and the number '1' !
by Halywid Hunters (210 points)
edited by Halywid Hunters
Oh well, guess that won't be possible then :-(
by mole125 (Expert) (21.1k points)
And I have never understand why this is the case. TB codes must be more recent then GC codes and they don't use 1 and l etc
by Target. (Expert) (104k points)

1 Answer

0 votes
http://project-gc.com/Tools/DiscoverTrackables#history

Expand the relevant row in the grid using the plus sign on the left side and you will get a full history, including the trackingnumbers for the rows with issues.
by magma1447 (Admin) (243k points)
ganja1447

Thank you! Sorry for missing this. Your help is much appreciated. HH
by Halywid Hunters (210 points)
 | PGC Theme, based on Snow Theme by Q2A Market
Powered by Question2Answer
...