Hi, We have a HQ and several stores connecting to it. All items are created from HQ and sent to store for receiving. In some instances when a 250 is sent twice to the store the item is duplicated at the store level. All information is exactly the same. On the flip side, when you create an item at the store level with the same sku it gives an error "Itemlookup code already exists". Why doesnt this happen with the polling and prevent the duplicate sku.
250 worksheet does not (should not) duplicate your Item Data, unless same item had been created manually at the store before transfer. Have a look and see if the duplicated items at store have HQID entries.
I first thought the same thing and looked at the HQID for the duplicates. THey are the same. Obvisouly the id at the item table are different and HQID is same. One thing that we did is that this HQID was updated few months ago at the store level from HQ using sql script.
Mano
"Afsh> 250 worksheet does not (should not) duplicate your Item Data, unless same
WRONG way to do. Anytime you can run the 101 worksheet and his will ensure that all records n Store have correct HQID. Run this first. Then look at the store to see if you have items with blank HQID. Doing it through SQL Scrip could be dangerous if there is typo or mis entry.
Afshin, Thanks for your reply. The reason I used SQL to update HQID is because I was told that 101 worksheet should be used only when the store is setup at first. Since our stores have been operating for a while, I thought that using
101 would wipe out my data. Are you saying that it is sage to use 101 without loosing any data at the store level.
Mano
"Afsh> WRONG way to do. Anytime you can run the 101 worksheet and his will ensure
I'm experiencing the same problem, but I'm 100% sure that Items were not created on the Store level as I'm the only one with access to this in SO. Others can create it only trough HQ. Especially items from one supplier are duplicating. I have one product 3 times in SO (about 30 items duplicated) Everything except "Date Created" and ID is the same.
I'm experiencing the same problem, but I'm 100% sure that Items were not created on the Store level as I'm the only one with access to this in SO. Others can create it only trough HQ. Especially items from one supplier are duplicating. I have one product 3 times in SO (about 30 items duplicated) Everything except "Date Created" and ID is the same.
Did the 101 worksheet helped to you ?
Thanks, Arthur
Mano wrote: > Afshin, > Thanks for your reply. The reason I used SQL to update HQID is because I > was told that 101 worksheet should be used only when the store is setup at > first. Since our stores have been operating for a while, I thought that using > 101 would wipe out my data. Are you saying that it is sage to use 101 without > loosing any data at the store level. > > Mano > > > "Afshin" wrote: > >> WRONG way to do. Anytime you can run the 101 worksheet and his will ensure >> that all records n Store have correct HQID. Run this first. Then look at >> the store to see if you have items with blank HQID. Doing it through SQL >> Scrip could be dangerous if there is typo or mis entry. >>
I'm experiencing the same problem, but I'm 100% sure that Items were not created on the Store level as I'm the only one with access to this in SO. Others can create it only trough HQ. Especially items from one supplier are duplicating. I have one product 3 times in SO (about 30 items duplicated) Everything except "Date Created" and ID is the same.
Did the 101 worksheet helped to you ?
Thanks, Arthur
Mano wrote: > Afshin, > Thanks for your reply. The reason I used SQL to update HQID is because I > was told that 101 worksheet should be used only when the store is setup at > first. Since our stores have been operating for a while, I thought that using > 101 would wipe out my data. Are you saying that it is sage to use 101 without > loosing any data at the store level. > > Mano > > > "Afshin" wrote: > >> WRONG way to do. Anytime you can run the 101 worksheet and his will ensure >> that all records n Store have correct HQID. Run this first. Then look at >> the store to see if you have items with blank HQID. Doing it through SQL >> Scrip could be dangerous if there is typo or mis entry. >>
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.