Browse Forum Posts by Tags: NAV 4.0 SP3, NAV 4.0, Navision 2.60

Do you think Microsoft should change the names again?

The change from Navision, Axapta and Great Plains og Dynamics NAV, AX and GP etc. is making less and less people ask for the products. Do you think that Microsoft is killing the Dynamics products?

Should Microsoft change the names back?

  • Yes - change the names back now (54.5%)
  • No - the names are good (45.5%)
  • Total Votes: 235

Latest Dynamics Documentation

  • There has not been recent media activity

Latest Dynamics Downloads

  • There has not been recent media activity

Get our Free Newletter

Don't you have the time to be online here at DUG every day? So how do you follow what is going on in the Dynamics industry and community?
If you subscribe to the DUG Newsletter then you can relax! We will make sure that you don't miss the big news!

Name:
E-mail:



You can also check our
Newsletter Subscription Center
page for our other newsletters.
Showing related tags and posts for the Forums application. See all tags in the site
  • Data Validation during Implementation - Upgrade

    As part of any implementation, or upgrade, I'm sure that everyone performs some data validation. Verification that Begining balances in you G/L Accounts in the new software matched the ending Balance in you old software and the Likes. Does anyone have a List of the things that they tested to verify...
    Posted to Dynamics NAV / Navision - End User Forum (Forum) by Alan A. Lyczkowski on Apr 6, 2010
    Filed under: NAV 4.0 SP1, NAV 4.0 SP3, NAV 5.0, Navision 3.60, opening balances, Data Migration, NAV 4.0, Navision 3.70, NAV 4.0 SP2, Navision 2.60, Navision 2.60 W1, Upgrade, NAV 5.0 SP1, NAV 2009, Navision, Navision 4.0, Navision 2009, NAV 2009 SP1, data conversion, opening balance, /L entries, Navision Attain, NAV 2.60c, navision 4.1, Navision 4.0 SP3, Navision 4.0 SP2, NAV
  • Re: List of the Undocumented Features of Dynamics NAV

    Another nice trick: If you know the field numbers of the table but not surely the field names, you can write your code based on the field numbers: SalesLine.SETRANGE(Field1,SalesHeader.Field1); SalesLine.SETRANGE(Field3,SalesHeader.Field3); If you save and close this code and open the object in Design...
    Posted to Dynamics NAV / Navision - Developers Forum (Forum) by Timo Lässer on Aug 22, 2008
    Filed under: NAV 5.0, NAV 4.0 SP3, NAV 4.0, Navision 3.01, Navision 3.70, Navision 2.60, NAV 4.0 SP2, Navision 3.60, navision, Dynamics NAV, undocumented feature, Tips & Tricks
Page 1 of 1 (2 items)