Today we will discuss an Common Issue which we face during upgrade to NAV 2013 and Later from NAV 2009 or Previous Versions.
After Data Migration All Data come as-is but Due to some Reason the Migration Process did not process Record Links To New Version.
Bron : Saurav Dhyani
For my first blog publication, here is a (very) small script to catch all your Office 365 users and bring them to Dynamics NAV.
Bron : Xavier Garonnat
Despite not being awfully fast, the ability to transfer a file with NAV Web Services comes handy at times. Imagine you had a requirement to present a customer logo in bespoke .NET application or you had to expose some data as a barcode image generated in service tier. Below example shows how to expose a generated PDF report to Web Services consumer, without using any external components but plain .NET Interop instead.
Bron : Candyworm.com
Guess what, more companies are moving to NAV 2013 R2.
I am about to start a data upgrade for a medium-sized Icelandic company. Doing a data transfer means that you need to compare the tables of the old version and the new version and where you have mismatch you have to take some action. The data transfer is build on the upgrade from 2009 to 2013 R2 released by Microsoft.
Bron : Gunnar’s Blog
This video demonstrates how to use the Transfer Customs Fields Pattern in Microsoft Dynamics NAV 2013 R2.
Bron : Microsoft Dynamics NAV
In November 2010 I blogged about Transferring small amount of data between databases. There I had a Form that can read and write a XML file with table data. This Form was used frequently in my company to move data between companies and databases.
The good thing about this method is that I can move data between database versions.
Bron : Gunnar’s Blog
Transfer orders are also a source of supply when working at the SKU level. When using multiple locations (warehouses), the SKU replenishment system can be set to Transfer, implying that the location is replenished by transferring goods from another location.
Bron : MSDN