Hi everyone,
I'm currently migrating data from NAV to Business Central using RapidStart configuration packages, and I'm facing a strange issue with the Customer table (T18).
After applying my package, some customer records are created in BC (the customer number exists) but most of their fields are empty — even though the data is correctly filled in my Excel file and visible in the package records.
For example, customer 6966 (SARL VABEMA CM 243) is created in BC but fields like Payment Terms Code, Payment Method Code, Bank Account Code, SIRET, contact, etc. are all blank.
A few fields did come through correctly (e.g. Gen. Bus. Posting Group, VAT Bus. Posting Group, Customer Posting Group = FRANCE, and a couple of toggles), so the import is partial, not fully failed.
**My package setup:**
- "Validate Field" is checked on most fields
- "Contact" field has Validate unchecked intentionally (contacts not yet imported)
- "Delete Table Records Before Processing" was not checked
**My questions:**
1. When "Validate Field" is checked and the referenced value doesn't exist in BC yet, does BC silently skip that field (leaving it blank) rather than throwing an error?
2. Is there a log somewhere that shows which fields were rejected during the apply, and why?
3. What is the recommended approach to handle circular dependencies (customers referencing contacts, ship-to addresses, bank accounts that don't exist yet at import time)?
My current plan is to:
- Re-import customers without dependent fields (contact, default ship-to, default bank account)
- Import dependent tables separately (T222, T287, T5050)
- Run a second smaller update package on T18 with only those 3-4 fields to populate
Is this the correct approach? Any advice welcome.
Thank you!
32
Share
Report
All responses (
Answers (
