I am trying to export Daybook as XML File using TDL similar to how it works from the Export button at the top. The exported XML contains the following - Code: <ENVELOPE> <DSPVCHDATE>5-Apr-22</DSPVCHDATE> <DSPVCHITEMACCOUNT></DSPVCHITEMACCOUNT> <DSPVCHTYPE>Ctra</DSPVCHTYPE> <DSPINBLOCK> <DSPVCHINQTY></DSPVCHINQTY> <DSPVCHINRATE></DSPVCHINRATE> <DSPVCHINAMT></DSPVCHINAMT> </DSPINBLOCK> <DSPOUTBLOCK> <DSPVCHOUTQTY></DSPVCHOUTQTY> <DSPVCHOUTRATE></DSPVCHOUTRATE> <DSPVCHNETTOUTAMT></DSPVCHNETTOUTAMT> </DSPOUTBLOCK> <DSPCLBLOCK> <DSPVCHCLQTY></DSPVCHCLQTY> <DSPVCHCLRATE></DSPVCHCLRATE> <DSPVCHCLAMT></DSPVCHCLAMT> </DSPCLBLOCK> <DSPVCHDATE>5-Apr-22</DSPVCHDATE> ... If exported using the Export button, the XML is correct as following - Code: <ENVELOPE> <HEADER> <TALLYREQUEST>Import Data</TALLYREQUEST> </HEADER> <BODY> <IMPORTDATA> <REQUESTDESC> <REPORTNAME>All Masters</REPORTNAME> <STATICVARIABLES> <SVCURRENTCOMPANY>Demo Company</SVCURRENTCOMPANY> </STATICVARIABLES> </REQUESTDESC> <REQUESTDATA> <TALLYMESSAGE xmlns:UDF="TallyUDF"> <CURRENCY NAME="?" RESERVEDNAME=""> <GUID>c335f8b2-a74d-422f-8e0f-21ca29feb637-0000001d</GUID> <MAILINGNAME>INR</MAILINGNAME> <EXPANDEDSYMBOL>INR</EXPANDEDSYMBOL> <DECIMALSYMBOL>paise</DECIMALSYMBOL> <ISUPDATINGTARGETID>No</ISUPDATINGTARGETID> <ISDELETED>No</ISDELETED> <ISSECURITYONWHENENTERED>No</ISSECURITYONWHENENTERED> <ASORIGINAL>No</ASORIGINAL> <ISSUFFIX>No</ISSUFFIX> <HASSPACE>Yes</HASSPACE> <INMILLIONS>No</INMILLIONS> <ALTERID> 386</ALTERID> <DECIMALPLACES> 2</DECIMALPLACES> <DECIMALPLACESFORPRINTING> 2</DECIMALPLACESFORPRINTING> <DAILYSTDRATES.LIST> </DAILYSTDRATES.LIST> <DAILYBUYINGRATES.LIST> </DAILYBUYINGRATES.LIST> <DAILYSELLINGRATES.LIST> </DAILYSELLINGRATES.LIST> </CURRENCY> ... I am not able to figure out why there is difference in the XML Schema. The TDL I created for exporting the Daybook - Code: [Report: DemoExportTransactions] Use: Day Book Print Set: DBIncludeFamily: Yes Print Set: SVFromDate: ##MetabookFromDate Print Set: SVToDate: ##MetabookToDate [Function: DemoExportTransactions] 10: SET : SVExportFormat : $$SysName:AnsiXML 20: Set : SVPrintFileName : "D:\Transactions.xml" 30: EXPORT REPORT : DemoExportTransactions : TRUE The same TDL was working earlier and exported the correct schema, but after installing latest version of Tally, the schema of XML has changed. I have tried reinstaling the earlier version but the schema is still different. Any insights for this problem is appreciated.
Code: [Report: DemoExportTransactions] Use: Day Book Print Set: DBIncludeFamily: Yes Print Set: SVFromDate: ##MetabookFromDate Print Set: SVToDate: ##MetabookToDate [Function: DemoExportTransactions] 10: SET : SVExportFormat : $$SysName:AnsiXML 20: Set : SVPrintFileName : "D:\Transactions.xml" 30: EXPORT REPORT : DemoExportTransactions : TRUE The same TDL was working earlier and exported the correct schema, but after installing latest version of Tally, the schema of XML has changed. I have tried reinstaling the earlier version but the schema is still different. Any insights for this problem is appreciated.[/QUOTE] [Report: DemoExport] Use : Day Book Form : DemoExport Export : Yes [Form: DemoExport] Use : Day Book [Function:Export Voucher] Local Formula : fileavbl : @@DefaultLoc + "DemoExport.xml" Local Formula : Isfileavbl : $$IsFileExistsfileavbl -01 : Do If : (@Isfileavbl) : Delete File: @fileavbl ;00 : Set : CurrentVCh : $$SPrintf@VchMasterID:$MasterID ;00 : SET : SVExportLocation : "." 01 : SET : SVOpenFileAfterExport: No 10 : SET : SVExportFormat : $$SysName:XML 20 : SET : SVPrintFileName : @@DefaultLoc + "DemoExport.xml" 30 : SET : SVPrintFileName : $$MakeExportName:##SVPrintFileName:##SVExportFormat 40 : Export : DemoExport : TRUE 41 : Msg Box:OK:Exported 50 : Return [System: Formula] DefaultLoc : $$SysInfo:ApplicationPath + "\"[/CODE]
