Stone Edge Order Manager - import older order#'s

[Adam - FMM]

I am working with someone who uses order manager. Recently their store was redeveloped to 4.14+ on a test server while the regular store 4.13 continued to operate in parallel.

What's happened is, when the test store went live the order numbers in there were lower than what the last order in the now offline 4.13 store had.

Example, the old store left off with order number 5000, but the new store started with order number 4000.

Problem is, that now that Order Manager has been updated to grab orders form this new store, it is unable to import orders 4000 to 5000 because as far as it is concerned it alread has those orders in it now. The new store had its starting order number pushed forward so at least from now on new orders will be pulled no problem.

Does anyone know if there's a way to get these 1000 mis-synched orders into OM somehow?

[Vic - WolfPaw Computers]

Edit the storekeys.dbf and adjust the order number to higher than the current number plus the "old" order numbers.

Manually renumber all the mis-synched order to fall within the now missing range.

You'll likely need to update some other db's too, like order options and payment database depending on what module is used.

See the MIVA 4.x DB reference manual for what other db's are dependent on the order number field. You'll have to be sure they are all updated before you try to sync.

I'm only suggesting this because I know you know your way around MIVA and the DB's fairly well.

I definitely would not suggest this approach to a novice or anyone NOT thoroughly familiar with the dbf format, and specifically MIVA dbfs.

[Random Confusion]

For the existing orders I'd suggest you export your orders to a file, download the file locally, then edit the order numbers to the right range. Import orders from file and point to this file.

For the web & new orders, change the numbering to be one higher than the last order that was processed - plus one. That way there will be a gap and hopefully no overlap. This way the new orders should be in the range that SEOM expects.

RC

[Adam - FMM]

This is the method I was hoping to avoid. :(

Edit the storekeys.dbf and adjust the order number to higher than the current number plus the "old" order numbers.

Manually renumber all the mis-synched order to fall within the now missing range.

You'll likely need to update some other db's too, like order options and payment database depending on what module is used.

See the MIVA 4.x DB reference manual for what other db's are dependent on the order number field. You'll have to be sure they are all updated before you try to sync.

I'm only suggesting this because I know you know your way around MIVA and the DB's fairly well.

I definitely would not suggest this approach to a novice or anyone NOT thoroughly familiar with the dbf format, and specifically MIVA dbfs.

[Adam - FMM]

I may be wrong, but I was under the impression that OM needs orders in a special proprietary format or something which you can only see if you tell it to export orders first so you can see how they are mapped. Then new orders must be put in said format to be imported? Or is that wrong and you can just use the standard Miva export flat file format?

For the existing orders I'd suggest you export your orders to a file, download the file locally, then edit the order numbers to the right range. Import orders from file and point to this file.

For the web & new orders, change the numbering to be one higher than the last order that was processed - plus one. That way there will be a gap and hopefully no overlap. This way the new orders should be in the range that SEOM expects.

RC

[Vic - WolfPaw Computers]

Might want to write to Barney or Kevin on that one...

There may be another way to do it...but I'm not aware of one.

[Random Confusion]

I really haven't tried it in a year and a half so I can't say.

I do know that if you don't have a LOT of orders, you can take the export information and manually enter the orders into SEOM and they'll be there.

Don't tell anyone I told you this, but if you know Access you can modify the database to add the Miva order number into the order as well - and change it from MO (manual order) to MV (miva order) but definitely play with a copy of the database before you do it for real. I don't recall all of the places that the databases tie together to say how easy it'll be. But manual entry is better than nothing, too.

RC

I may be wrong, but I was under the impression that OM needs orders in a special proprietary format or something which you can only see if you tell it to export orders first so you can see how they are mapped. Then new orders must be put in said format to be imported? Or is that wrong and you can just use the standard Miva export flat file format?

[Adam - FMM]

The problem is that I have to help do this remotely (client is in another state) for someone who is very non technical. I can see a big SNAFU happening if they have to do much more than click a button or two.

[Barney Stone]

Create a new shopping cart in the Order Manager, pointing it to the same Miva store. Give it a name like "Just use this cart once" or something like that, because you will not be able to delete it. Import the problem batches using the new shopping cart. That will import the orders.

[Random Confusion]

<cheer> I knew Barney would come up with something more simple.

RC