Obsolete and duplicate actions still visible after Data upgrade from Nav 2013 R2 to Nav 2018 CU2

Hi..We have a customer database which is upgraded from Nav 2013 R2 to Nav 2018 Cu2. After upgrading the database,we where still able to see some obsolete actions in Nav 2018 CU2 as well as duplicate actions for Statistics,Release etc in some page among which only one action performs operations when selected.

For Example:Credit Cards Action is present in Nav 2013 R2 which is obsolete in 2018 CU2

This happens only in the customer environment.
1)Customer environment has Nav2018 CU2 installed.
2)Same database is restored in an other server.Still the problem exists.
3)We imported all upgraded objects set in an other server on top of Cronus database.This problem doesn't occur.

However since its an upgrade customer data needs to be there.

Could you guys let us know valuable inputs.Thanks in advance


  • Slawek_GuzekSlawek_Guzek Posts: 1,454Member
    edited 2018-04-16
    It looks like errors in merging. Did you do merge manualy (by comparing the text files), or did you just run the pages through some sort of tool, and put results back into the database, without validating them?
    Slawek Guzek
    Poszukuje programistow znajacych Microsoft Dynamics NAV
  • krishna1235krishna1235 Posts: 3Member
    edited 2018-04-16
    Hi Slawek_Guzek,
    Thanks for your reply.
    We have merged the customizations manually to Standard 2018 objects excluding obsolete actions.
    However same set of objects when imported in a fresh Cronus database in different server works fine.
    Not sure may be any registry kind of thing which is pointing to the earlier Nav version?

  • Slawek_GuzekSlawek_Guzek Posts: 1,454Member
    I would double check the code. Things like this one do not appear automagically out of thin air, there must be someting left - most likely in the source code.

    I would also try to delete all user personalisations.
    Slawek Guzek
    Poszukuje programistow znajacych Microsoft Dynamics NAV
  • JuhlJuhl Posts: 523Member
    Its metadata problem AS Slawek surgests.
    Clean out the tables.
    Follow me on my blog juhl.blog
  • krishna1235krishna1235 Posts: 3Member
    Hi Juhl,thanks for the suggestion.
    Cleaning Profile metadata table(2000000074) helped in resolving this.
Sign In or Register to comment.