9th Jul, 2013

Tips using NAV Excel Migration tool

The Excel Migration tool certainly is valuable future, if you know of some of its abilities and quirks.

Here’s my list of things to know and to wish for. When you import data that reference information in another source table, that data has to be imported first.

I have several tables I want to export from. NAV adds all table in separate sheets which is annoying since I want to export one table only; and exporting all data makes things slow. Well that is simple - select (highlight) only the table you want to export and then export.

Why is the above handy? You will want to import tables in a particular sequence as indicated. For one reason because you first need to populate records in a source table before importing data into another that depends in the first.

So I want to import 2 tables. Both tables reference each other (or references are contained to other records in the same table).  What now? Also simple. Create a copy of the spreadsheet you are going to import. In the original copy delete the column that depends on the data that does not exist yet. Import the data. Then import the copied spreadsheet.

 I have data that links to another table based on two fields, forming a compound key pointing to data in a source table. I get errors if I try to import. Do the two excel file copies trick, delete the second column in the first Excel file and import them one after another.

 I added a few records in a table and I want to export only that. Is there a way? Well, I could not find a way yet, but export and import everything. Drill down on the No. of Migration Records. Now mark only the records you want to migrate and Apply the migration data.  It is time consuming to setup the fields for a table I want import. You don’t have to do that. If you have no tables defined for migration and you import, NAV will create the migration table records and migration fields from the spreadsheet.

 I have a couple of migration errors and I want to massage the data and try again. Easy enough. Drill down on the No. of  Migration Errors. Change the data that you want. Run the “Migration Record” table and remove the check marks in the “Invalid” column. Now it will be visible in the No. of Migration Records column instead. You can apply the migrations once again.

What I would wish for?

  1. The system should not prevent you from reapplying invalid records. If you try to apply an invalid record, you surely must have a reason, like having had the data massaged.
  2. When adding fields for export migration, additional information so that we know which are flow fields and whether and what relations exist with other tables for each field. This knowledge can save a lot of time during migration efforts.

Leave a response

Your response:

To prove you're a person (not a spam script), type the security text shown in the picture. Click here to regenerate some new text.
Click to hear an audio file of the anti-spam word