Edgar, Yes Excel imports are slow for so many records. You might investigate removing rows and columns that are not to be imported; resaving the Excel file as delimited text. Then create a Definition Group - Custom - and load the delimited text that way.
Another option is to get a developer to help who can use the AX<table> classes in a custom job for the load - combining create of all tables for each item at one time. One thing that increases speed of import is to commit for each item so that there is sufficient fast memory and no swapping. Also, with a custom job, you can load using multiple parallel sessions for greater throughput. Mary Ann On Sun, Nov 30, 2008 at 3:29 AM, edgarcck <[EMAIL PROTECTED]> wrote: > Hi all > > I am writing to ask for the best practice and benchmark about > uploading item master. > > When I try to import 50000(inventory records to InventTableModule > (actually is 150,000(invent/sales/purchase), but i was planning to > separate them into three times), the AX program can't finish the > import process even after 6 HOURS!! > > So i would like to ask does anyone have similar experience and > normally how long should it take for 50,000 records, and is there any > better way to import item master rather then import to those three > tables manually? > > Regards > Edgar > > P.S. > My problem is actually about "time". Actually i need to upload 200,000 > item into the item master. I separate the item in four excel file and > try to import using "excel import" from AX. > > Moreover, I have no program in the upload process and i understand > that we need to upload all of these three tables. > 1 Item's record in InventTable > 2 Three records in InventTableModule Table (for sales, purch and invent) > 3 Record in InventItemLocation table and inventDimId field of this table > >
