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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

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

Configuration Packages - Limiting Fields

(8) ShareShare
ReportReport
Posted on by 19
Has anyone experienced an issue where they create a Configuration Package to import a subset of fields (25 out of 118 fields on the table). This seems to work but periodically the config package setup appears reset to include all fields.
I have the same question (0)
  • Suggested answer
    Gregory Mavrogeorgis Profile Picture
    992 Super User 2026 Season 1 on at

    Yes — I’ve seen this happen. It usually occurs after a table schema change (extension update, app upgrade, or adding/removing fields). When the table metadata refreshes, Business Central can re-expand the config package to all fields instead of preserving the subset. Re-selecting fields after extensions or updates is often necessary.

     
    Please mart it as verified if has help you
  • Suggested answer
    Teagen Boll Profile Picture
    1,777 Super User 2026 Season 1 on at
    I have seen it happen after updates especially if they change fields or add new ones. I recommend exporting the rapidstart package itself so you can maintain a backup copy. This way you can re-import the rapidstart package with the configuration package settings itself if anything happens to go wrong with it.
  • Suggested answer
    OussamaSabbouh Profile Picture
    13,756 Super User 2026 Season 1 on at
    Hello,
     
    This usually isn’t random — Configuration Packages reset to include all fields when someone re-runs Get Tables / Get Fields, refreshes the package after a table schema change (like an extension update adding fields), reimports the package, or copies it, which causes BC to repopulate all table fields. Best practice is: once you select your 25 fields, avoid refreshing the table in that package and export the package as a backup so you can quickly restore it if the field list gets regenerated.
     
    Regards,
    Oussama Sabbouh
  • Suggested answer
    Nour_K Profile Picture
    67 on at
    hello,
    This usually happens after a schema update, you need to update fields before using the table in a configuration package.
     
     

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,028 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,121 Super User 2026 Season 1

#3
Teagen Boll Profile Picture

Teagen Boll 669 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans