NAV 2013 R2 Synchronization Paradigm.
Dear All,
Below are some extracts of the article published in Microsoft Team Blog about
It start's explaining the History, how it used to happen in NAV 2009 / NAV 2013-
Microsoft Dynamics NAV 2009 / Microsoft Dynamics NAV 2013
When we import/compile an object in C/SIDE, system checks the object Metadata Version and Compare with Current Version. If the Current Version is New it updates the Object Metadata in Navision and Schema changes are directly applied to SQL Server.
So before NAV 2013 R2, everything used to get updated directly from Classic Client and at the time when we used to process.
At most the only issue we used to have was “The Object Metadata does not exist. Identification and values … “ when running the Microsoft Dynamics NAV Windows client.
Which used to be resolved just by recompiling the Objects specified in error or all the objects or deleting the metadata of that object and re-creating it.
Read Complete Article »
Below are some extracts of the article published in Microsoft Team Blog about
"The New Table Synchronization Paradigm in Microsoft Dynamics NAV 2013 R2".
It start's explaining the History, how it used to happen in NAV 2009 / NAV 2013-
Microsoft Dynamics NAV 2009 / Microsoft Dynamics NAV 2013
When we import/compile an object in C/SIDE, system checks the object Metadata Version and Compare with Current Version. If the Current Version is New it updates the Object Metadata in Navision and Schema changes are directly applied to SQL Server.
So before NAV 2013 R2, everything used to get updated directly from Classic Client and at the time when we used to process.
At most the only issue we used to have was “The Object Metadata does not exist. Identification and values … “ when running the Microsoft Dynamics NAV Windows client.
Which used to be resolved just by recompiling the Objects specified in error or all the objects or deleting the metadata of that object and re-creating it.
