Any clues on how I could get duplicate itemlookupcodes?? I found a few of them recently. No SQL queries have been run to generate them and if I try to create a duplicate itemLookupCodes I am stopped with a message telling me to use a unique name. How could they have gotten in the database? Any clues, boos or comments appreciated. Thanks for all the help! Jamie W
I've had this happen a couple times. The employee typically put a space in front (or after) the lookup code in a search then built the item after not finding it. There is a complicated process of fixing the DB or in my case I pushed the wrong items out to the vender (move offline first) and built a PO to bring back the same QTY on a PO. Merging this stuff in an HQ enviroment is complicated because of the multiple tables that are impacted.
Seems like there should be some type of validation allowing only numbers-letters in the first and last positions of lookup codes to avoid this, but I understand it's tough to predict every mistake someone could possibly make and your employees will no doubt find them.
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.