When the customer list gets loaded, the Import Manager auto-creates (part 1) a ship-to record which contains a copy of the bill-to information and is set to the default ship to (part 2) a contact which contains a copy of the bill-to information and is set to the default contact.
PART 1:
If you don't have a ship to file to load, then you are happy because you don't need to load a ship to also. However, if you have a ship to file to load, you have a mess that needs to be cleaned up.
What CB staff have been doing is importing the primary ship-to row into a SQL work table using Management Studio Task>Import data, then using direct SQL update statements to overwrite the auto-generated default ship to with the proper data. Then using the Import Manager to only import the non-primary ship to rows.
When the customer list gets loaded, the Import Manager auto-creates (part 1) a ship-to record which contains a copy of the bill-to information and is set to the default ship to (part 2) a contact which contains a copy of the bill-to information and is set to the default contact.
PART 1: If you don't have a ship to file to load, then you are happy because you don't need to load a ship to also. However, if you have a ship to file to load, you have a mess that needs to be cleaned up.
What CB staff have been doing is importing the primary ship-to row into a SQL work table using Management Studio Task>Import data, then using direct SQL update statements to overwrite the auto-generated default ship to with the proper data. Then using the Import Manager to only import the non-primary ship to rows.
See also the sister issue: https://github.com/DynEntTech/CBKnownIssues/issues/26
PART 2: (need to work out the workaround for this)