DE-B
 
But you have to be tricky. I just updated about 10,000 items this way.
 
From our internal help site (basic plan from Lynn, slightly modified for our own use):
 
This can also be used to update any other elements of the existing data files.
 
Create a comma delimited file with the Item Number and base price (and/or anything else you want, but you always need Item Number)
 
Make a backup and get everybody out of DBA.
 
Make sure you have a good backup.
 
Rename the following files:
    BKICEMTR to BKICEMTR.EMPTY
    BKICELOC to BKICELOC.EMPTY
    MTICEMTR to MTICEMTR.EMPTY
 
Rename the following files:
    BKICMSTR to BKICEMTR
    BKICLOC to BKICELOC
    MTICMSTR to MTICEMTR
 
Run the DE Inventory Error report to confirm all copied properly
 
Import the file indicating Replace
 
Run the DE Inventory Error report to confirm you haven't introduced errors
 
Rename the following files:
    BKICEMTR to BKICMSTR
    BKICELOC to BKICLOC
    MTICEMTR to MTICMSTR
 
Rename the following files
    BKICEMTR.EMPTY to BKICEMTR
    BKICELOC.EMPTY to BKICELOC
    MTICEMTR.EMPTY to MTICEMTR
 
How this works.
 
The first set of files are the empty temporary data import file.
 
The second set of files are the live inventory files. By renaming them, it puts all your existing data into the data import location.
 
Importing the new data then modifies only the part that is changed.
 
And the third set makes the temporary data import files the live ones.
 
The .EMPTY files are temporary holding places for the import files (you could also restore originals, or copy them somewhere else - this is just the easiest way I've found). If you don't replace the import files when done, you will have a problem if you Copy that company to a new one.

While it may be (relatively) safe to import new base prices to the master tables, the procedure of importing to the temporary tables and run the error report is to ensure you haven't introduced errors by importing invalid field values if you are importing other things such as Class or Type.   I am sure we could develop a program to automate the process, automatically backing up the master files, importing the desired information directly to the master tables, running hte error report and restoring the backup files if errors were introduced but that would cost programming time and $$ and thus far, everybody needing to do it has been willing to use the free (and admittedly awkward) approach.

Unacceptable in that I would not find it acceptable for a commercial program to think it's OK to make you manually copy files around in order to safely update the database. Transactions and triggers and such would prevent any need for such a thing. Or, all import functions could by default import to a temporary table first (or have the option) and then have a program that copies the temporary over to permanent. Or, take a page from Google. We use Google Base to upload our product catalog so that people can search it. It takes an XML file as input. If your input file has errors it tells you and you correct it. It does not try anyway and toast your data.
 
One may think that I'm a bit too anal about this but I find a lack of data integrity to be the worst of sins in this type of program. Either you can trust your ERP software or you can't. Maybe is not a comforting answer. If you can't trust the program to not trash your data on import without manually copying files behind the software's back then what good is it?
 
-Grumpy Gus
 
 
Quote from David Waldmann on 07/03/07 at 11:51:14:

Yes, it's good that the workaround exists and that they've taken the time to explain it. But, it's still not acceptable to say, basically 'our program can toast your data but heres a way to fix it that involves logging everyone out and manually copying files around' At least, it'd be nice if the solution didn't involve a total shutdown of the system.  
 
And my point is that without that work around the program could very well totally screw the pooch. That's not a nice state of affairs. It means that you have to be aware of a work around in order to actually have reasonable assurance that your data will be intact. Granted, shame on the company without current backups!
 
Happy 4th to you as well. Hopefully we all get back on Thursday with all 10 fingers!

Quote from Lynn_Pantic on 07/05/07 at 07:08:53:

 
Ahh... I see... I was judging my comments from when you said:
 
Quote:

 
Which makes it sound like you could easily toast your data if you don't use the work around.
 
Despite my best efforts I still have all 10 fingers too.