Navision Go-Live Tool

Comments

• sun4ben Member Posts: 1

  2006-04-12

  I don't think that this tool is usefull. Imagine you've forgotten to delete 1 table... I wish you good luck!

  0
• Roger Member Posts: 57

  2006-04-25

  I think, the problem is, that all tables are listed in the tool (Contacts, Customers, ...) instead only tables like 36, 37, 110, 111, and so on

  Many thanks, Roger

  0
• Miklos_Hollender Member Posts: 1,598

  2006-06-05

  I think this would be impractical, because localization, add-ons and custom development can introduce more transactional tables. Also, sometimes people want to delete some master data too, or sometimes keep some transactional data, f.e. typically Fixed Asset Ledger Entries of book value.
  
  You can go through all the tables when you have some spare time, tick the ones you think should be deleted, and save it with a simple DataPort for later reuse. I think I will add that DataPort in the next version to save you the work.
  
  If you are not very familiar with the table structure of Navision, here are a few hints:
  
  - delete everything called "Entry", i.e. filter for *Entry*
  - delete documents and journals - everything called "Header" or "Line"
  - delete Document Dimension, Posted Document Dimension, Ledger Entry Dimension, Journal Line Dimension, although they are of course included in the aforementioned filters
  
  Hope this helps,
  
  Miklos

  0
• song Member Posts: 16

  2006-08-08

  Maybe you can incorporate this specs, you can add a column in the object designer "Existing Records". With this we can easily identity whether a table has records in it already.

  0
• rdebath Member Posts: 383

  2008-05-09

  The problem I see with this is that you're deleting data [-X
  
  It's certain that the users will discover that they wanted some of that data after all :roll:
  
  What you should do is copy the data you want to keep to a new company let them do some little checks in the new company, change thier minds and mess things up.
  So the final go live copy is right. That way we're all happy =D> =D> =D>
  
  Of course a month after golive there will be yet another problem ](*,)
  
  PS: Company.INSERT works just fine :shock:
  
  PPS: Smiley overload \:D/

  Robert de Bath
  TVision Technology Ltd

  0
• Alex_Chow Member Posts: 5,063

  2008-05-09

  This tool can be used as a start. But not necessarily run it out of the box.

  Confessions of a Dynamics NAV Consultant = my blog
  AP Commerce, Inc. = where I work
  
  Getting Started with Dynamics NAV 2013 Application Development = my book
  Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book

  0
• Miklos_Hollender Member Posts: 1,598

  2016-04-25

  Holy cow... I just realized I made it 10 years ago. Time is going fast. And almost 4000 downloads... I see now it is not the ideal solution to the problem but neither is the opposite i.e. just copying setup tables. But there wasn't one ideal solution in 2016. In 2016 the ideal solution is the copy company too. Set up everything in an empty database, copy it and make test postings in the copy. Change settings in the original, copy again, test it in that etc.

  0