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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Are Fields removed from Page after Upgrade, is this true?

(0) ShareShare
ReportReport
Posted on by

Hi everyone,

I have a question when it comes to Dynamics NAV and after upgrade or update our Supplier says that this will remove Fields, Properties etc from Pages that are changed with additional fields, etc. Is this true?

Because we want to keep as much as we can to the Default? But I never saw this with other products from Microsoft?

Can somebody explain this to me if this happens after an update or upgrade?

Thanks in advance,

André

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Mohana Yadav Profile Picture
    61,005 Super User 2025 Season 2 on at

    it depends upon how they are doing.

    but it is not true that they will be deleted always.

  • Suggested answer
    Nareshwar Raju Vaneshwar Profile Picture
    5,596 on at

    Hi,

    I partially agree with the statement. Meaning, I do not agree with that you cannot carry forward your customizations, yet upgrading with the customizations is a big challenge.  But with the correct precautions, you can upgrade, even your customized codebase.

    Check these following links which explains how you can proceed with upgrades with customizations.

    [1] dynamicsuser.net/.../how-to-do-an-application-upgrade-of-navision

    [2] www.dynamics101.com/dynamics-nav-code-upgrade-challenges

    Hope it helps.

  • Suggested answer
    RockwithNav Profile Picture
    8,637 Super User 2025 Season 2 on at

    Hey Mystic,

    There are two things I believe - 

    1. The one which is customized is something which you have asked your supplier to develop additionally. So if it's something totally new that means you have to carry forward all your customizations to the newer version and there's no limitation on this provided you have the required license  .

    2. Now as far as the Fields, Properties of the pages are concerned of the Standard NAV then Yes there you will feel many standard changes between the two versions. You may find some extra field added or additional properties introduced in the newer version. But it's all about standard NAV and if there is a change there must be some enhancement, so there's nothing which may hamper your existing functionality.

  • Suggested answer
    Alexander Ermakov Profile Picture
    28,096 on at

    There are two parts of the story, I suppose.

    One part is that the user interface is customizable, and users may setup their page the way they like it (e.g., hide some fields or reveal the other fields, change size and order of the fields and factboxes). This is stored as their own settings and next time they open NAV, they see their unique setup. However when you have to modify a page or table behind the page, in some cases you need to re-compile it and it would lead to the fact that all the settings on the user interface would be lost (e.g., revealed fields will disappear and other will appear back). Users would need to perform setup once more.

    The other part is that rolling up an update would not usually modify additional customized functionality, as the range of the objects of customized functionality is usually different from those used in standard updates (e.g., you have added a field in a table, and most likely it will not be affected by the update). However, if you had modified the objects of standard functionality, or your additional objects are referred to standard objects that are changed by the update, you indeed might have a risk of loosing the information, as a conflict within the update would appear.

    If your partner will take care of the conflicts properly, it should not be harmful or should not lead to disappearing of the objects or data. But, if they will not take care properly of the conflicts, some damage might happen.

  • Community Member Profile Picture
    on at

    So if I understand it well, when we add some fields, for example: DropDownLists to other Custom Lists they won't be deleted, but most likely they are not displayed anymore? Those customizations are not gone?

    From my understanding I just want to add some fields with values out of the DropDownLists and save them with the contact? The table wouldn't be harmed after an update/upgrade?

  • Verified answer
    Alexander Ermakov Profile Picture
    28,096 on at

    In this case, yes, it is safe. If you add a new filed in a table with a DropDown selection, and this will be in the additional objects range (e.g., starting from 50000), it should not be affected by the standard update.

    It might disappear from the page after the update, but you can easily reveal it back on the page without any issues.

  • Suggested answer
    Community Member Profile Picture
    on at

    Ideally any customization like Custom Fields or DropDownLists etc. should be migrated during upgrade process.

    If at all is not available, You can easily add any fields without any issue.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans