Afternoon Everyone,
My colleague has a Repair Database, items are booked in by serial, booked out by serial.
Sometimes multiple items (normally non OEM) have generic duplicate serial numbers. For receiving the items this is ok, but when sending the devices back out
they need to have genuine unique serials. (serial in > serial out)
My colleague asked me if there is a way of stopping someone from entering one of these "Bad" serials when shipping the units.
A user will populate a "Serial Out" field, either individually or by pasting multiple serials into a datasheet form.
One challenge is that we do not know these "bad" serials until we come across them and the serials received can my any number of lengths. formats and characters etc.
My first thought is to build a "bad serial table" something that is manually populated when the bad serials are found, maybe some query to review weekly to try and highlight the potentially bad serials. (something like looking for multiple repair id's from the same day sharing the same serial) for example.
Then I would try and use this table as a reference to stop any updates in these fields if they appear in this "Bad Serial Table"
My Questions are:
Does this seem like a plausible idea?
Is there possible a better direction i could tackle this from?
If it seems plausible does anyone have any advice for a datasheet friendly approach that would almost use a "in list" event as opposed to a "not in list"?
As always any feedback or thoughts are appreciated
My colleague has a Repair Database, items are booked in by serial, booked out by serial.
Sometimes multiple items (normally non OEM) have generic duplicate serial numbers. For receiving the items this is ok, but when sending the devices back out
they need to have genuine unique serials. (serial in > serial out)
My colleague asked me if there is a way of stopping someone from entering one of these "Bad" serials when shipping the units.
A user will populate a "Serial Out" field, either individually or by pasting multiple serials into a datasheet form.
One challenge is that we do not know these "bad" serials until we come across them and the serials received can my any number of lengths. formats and characters etc.
My first thought is to build a "bad serial table" something that is manually populated when the bad serials are found, maybe some query to review weekly to try and highlight the potentially bad serials. (something like looking for multiple repair id's from the same day sharing the same serial) for example.
Then I would try and use this table as a reference to stop any updates in these fields if they appear in this "Bad Serial Table"
My Questions are:
Does this seem like a plausible idea?
Is there possible a better direction i could tackle this from?
If it seems plausible does anyone have any advice for a datasheet friendly approach that would almost use a "in list" event as opposed to a "not in list"?
As always any feedback or thoughts are appreciated