web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

package configuration

(9) ShareShare
ReportReport
Posted on by 58
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!
I have the same question (0)
  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    2,743 Super User 2026 Season 1 on at
    Hi, your record created but fields empty - often that mean there ARE errors you not seeing, but not always, so confirm first. Open the configuration package card, look at No. of Package Errors on the line for table 18 and click the number, it open Config. Package Errors and show which field and why. Payment Terms Code, Payment Method etc probably failed because the referenced record not exist yet. But blank can also be a field not in the package, wrong mapping, empty Excel cell, or validate disabled - so check the log before you assume.

    Your plan is good direction. Import the parent tables first - Payment Terms, Payment Method, Ship-to 222, Cust. Bank Account 287 - then customers, then a small second package for the linking fields. On contacts, only importing Contact 5050 does not wire the customer link, BC use Contact Business Relation 5054 from Marketing Setup. Often easier to let BC create contacts from the customers. Which version you go to?

    Hope this help.
     Tick the checkbox below to mark the answer as verified, if it helped resolve your question.
     
    Regards
    Gregory Mavrogeorgis
     
  • Suggested answer
    Valentin Castravet Profile Picture
    32,800 Super User 2026 Season 1 on at
    It sounds like you imported a configuration package that has several errors. You’ll need to fix the errors, then apply the data in the package again.
     
    1. BC imports the record, but if there is an error, it can leave the other fields blank. That’s why you are seeing customers created, but their data is missing.
     
    2. Yes, you can view the errors from the Configuration Packages page.
     
    3. Import the customers first, then import the other related records. After that, apply the customer package again.
     
    I wrote a guide on configuration packages and have a section on handling errors in there - How to Import Data Using Configuration Packages in Dynamics 365 Business Central - Dynamics 365 Business Central Insights
     
  • Suggested answer
    YUN ZHU Profile Picture
    102,417 Super User 2026 Season 1 on at
    Hi, hope the following helps as well.
    Dynamics 365 Business Central: How to show all error messages in Configuration Package
    How to Export and Import Data (Using Configuration Packages)
     
    Thanks.
    ZHU
  • Suggested answer
    OussamaSabbouh Profile Picture
    18,299 Super User 2026 Season 1 on at
    Hello Federico,
    Yes, your approach is the right one: with RapidStart, if Validate Field is enabled, BC runs the normal field validation logic, so missing setup/dependent records can prevent some values from being applied, and you should review the package/migration errors because Microsoft documents Error Text and Field Caption as the places to see why a record/field failed. For circular dependencies, I usually import in layers: first core customer fields only, then dependent tables like ship-to addresses, bank accounts, contacts, etc., then run a second small update package on Customer to fill fields like Contact, Default Ship-to, Bank Account, Payment Method/Terms if needed. Also, for serious production migrations, Microsoft recommends considering XMLports instead of relying only on configuration packages.
    Regards,
    Oussama Sabbouh
  • Suggested answer
    Mansi Soni Profile Picture
    10,224 Super User 2026 Season 1 on at
    Hello,

    In Business Central RapidStart, when importing customers, missing or invalid related values (like payment terms, contacts, or bank accounts) may result in those fields being left blank without always showing a clear error, as there is no detailed field-level rejection log. This is expected behavior when dependencies are not yet available. The correct and recommended approach is to handle migration in stages: first import the core customer master data without dependent fields, then import related tables (contacts, ship-to addresses, bank accounts) separately, and finally run a second update package on the Customer table to populate the remaining dependent fields.

    Hope this answer helps you!

    If this answer helps you, kindly mark it as a verified answer

    Regards,
    Mansi Soni

  • Suggested answer
    Khushbu Rajvi. Profile Picture
    23,132 Super User 2026 Season 1 on at
  • Suggested answer
    Kamal Khakhkhar Profile Picture
    3,562 on at
    Hii there ,
    you can migrate old database with new version with upgrade tool kit , and upgrade code units. you can use this approach also .
    you can refer some of below links .
    https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-nav
    https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrading-to-business-central-on-premises
    https://youtu.be/OSkNmGuShQk?si=XS37q89Vekk_vxIH

    if you found answer mark this verified.
     
    Thank You.
    Kamal KhaKhkhar.
     
  • Gerardo Rentería García Profile Picture
    27,507 Most Valuable Professional on at

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 695 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 422 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 328 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans