Upgrade tricks from swp-group.com

swpoloswpolo Member Posts: 80
Hi,
A lot of upgrade projects go through our company and sometimes we found interesting technical things, tricks, bugs which stops normal data-migration process. Depending on database size developers spends a lot of time to find solution. And finally this process can take a lot of time for investigation.

Some things I will put here, maybe it helps somebody.
Nav Upgrades and DEV outsourcing
Reports transformation to RDLC
List -1h , Complex List -3h, Document -4h (dev hours)
navisionupgrade.com

Comments

  • swpoloswpolo Member Posts: 80
    Posted Assembly Line is empty after migration from 2009 to 2015 NA.
    The problem was in function order in standard Upgrade601800.US.fob.

    UpdateAsm function sould be placed after UpdateTempItemLedgerEntry.

    UpdateTempItemLedgerEntry function fills Order No. and Order Type fields in Item Ledged Entry table which required in UpdateAsm;

    Nav Upgrades and DEV outsourcing
    Reports transformation to RDLC
    List -1h , Complex List -3h, Document -4h (dev hours)
    navisionupgrade.com
  • swpoloswpolo Member Posts: 80
    Strange standard bug in NAV 2009 - 2017.

    Create object Codeunit with any ID and name '1' (one digit without quotes).

    If you try to import any object via txt file which contains line for example:
    RunObject=Codeunit 1003
    

    you will have an error:
    You cannot enter ' RunObject=Codeunit 1003;' in ObjectID.

    If you rename codeunit to any name - import works well.

    :)
    Nav Upgrades and DEV outsourcing
    Reports transformation to RDLC
    List -1h , Complex List -3h, Document -4h (dev hours)
    navisionupgrade.com
Sign In or Register to comment.