VERSION COMPATIBILITY CHECK Migrate Code to any higher release of Tally.ERP 9 TDLByte #14 Dear Developers, In our previous TDLBytes, we had explained various steps involved in migrating the TDL code from any lower release of Tally.ERP 9 to Release 5.0 using Version Compatibility Checkfeature. Apart from migrating the code to Release 5.0, this feature is also capable of migrating the TDL code from any lower release to any higher release. For instance, you have a customization compatible up to Tally.ERP 9 Release 4.8 and you want to migrate it to Tally.ERP 9 Release 4.91. Here, let us consider Release 4.8 as Base Release and Release 4.91 as Target Release. To perform Version Compatibility check, we know that tdlserver.ddif file has to be present for both base and target release. Following similar steps mentioned in previous TDLBytes, let us see how the compatibility check can be performed for this instance. Step 1 Load default code of Base Release (Release 4.8) and generate Compatibility Metadata [Read more...] Step 2 Load Default code of Target Release (Release 4.91) and generate Compatibility Metadata [Read more...] Note: From Tally.Developer 9 Release 5.0 onwards, the tdlserver.ddif file will be available by default for the default source code. Therefore, we did not generate the compatibility metadata for Release 5.0 as illustrated in TDLBytes #11. Step 3 Load the Customization Project and Perform Version Compatibility Check [Read more...] We hope you must now have a clear understanding of Version Compatibility Check feature and how you can easily migrate all your customizations to your desired target release. In our next TDLByte, we will introduce you to a new enhanced feature of Tally.Developer 9. Stay tuned!