1. CLICK HERE TO JOIN WHATSAPP CHANNEL FOR TDL PROGRAMS

Tally Export XML not working in Prime

Discussion in 'Tally Integration' started by RRqweqwe, Dec 21, 2021.

    
Tags:
  1. RRqweqwe

    RRqweqwe New Member


    The below XML REQUEST is not working on Prime. I am trying to import sales vouchers in the current financial year. The request used to work before the latest Tally prime update.

    <ENVELOPE>
    <HEADER>
    <TALLYREQUEST>Export Data</TALLYREQUEST>
    </HEADER>
    <BODY>
    <EXPORTDATA>
    <REQUESTDESC>
    <STATICVARIABLES>
    <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>
    <VoucherTypeName> Sales </VoucherTypeName>
    <!--Specify the Period here-->
    <SVFROMDATE>01-04-2021</SVFROMDATE>
    <SVTODATE>31-03-2022</SVTODATE>
    </STATICVARIABLES>
    <!--Specify the Report Name here-->
    <REPORTNAME>Voucher Register</REPORTNAME>
    </REQUESTDESC>
    </EXPORTDATA>
    </BODY>
    </ENVELOPE>
     
    RRqweqwe, Dec 21, 2021
    #1


  2. Sai Vineeth

    Sai Vineeth Active Member


    You can use any of the below xmls to get all sales vouchers
    Code:
    <ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <TALLYREQUEST>Export</TALLYREQUEST>
        <TYPE>Collection</TYPE>
        <ID>Vouchers</ID>
    </HEADER>
    <BODY>
        <DESC>
            <STATICVARIABLES>
                <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT> <!-- * Supports only xml format -->
              <SVViewName>Accounting Voucher View</SVViewName>
                <SVFROMDATE>{{Fromdate}}</SVFROMDATE>
                <SVTODATE TYPE="Date">{{ToDate}}</SVTODATE>
            </STATICVARIABLES>
            <TDL>
                <TDLMESSAGE>
                    <COLLECTION ISMODIFY="No" ISFIXED="No" ISINITIALIZE="No" ISOPTION="No" ISINTERNAL="No" NAME="Vouchers">
                        <TYPE> Vouchers : Group</TYPE>
                            <!--Replace Sales Accounts with GroupName you want to search -->
                        <Childof>Sales Accounts</Childof>
          <!--includes low level  child's -->
                       <BELONGSTO>Yes</BELONGSTO>
                        <NATIVEMETHOD>*</NATIVEMETHOD>
                  
                    </COLLECTION>

                </TDLMESSAGE>
            </TDL>
        </DESC>
    </BODY>
</ENVELOPE>

    or

    Code:
    <ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <TALLYREQUEST>Export</TALLYREQUEST>
        <TYPE>Collection</TYPE>
        <ID>Vouchers</ID>
    </HEADER>
    <BODY>
        <DESC>
            <STATICVARIABLES>
                <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT> <!-- * Supports only xml format -->
              <SVViewName>Accounting Voucher View</SVViewName>
                <SVFROMDATE>{{Fromdate}}</SVFROMDATE>
                <SVTODATE TYPE="Date">{{ToDate}}</SVTODATE>
            </STATICVARIABLES>
            <TDL>
                <TDLMESSAGE>
                    <COLLECTION ISMODIFY="No" ISFIXED="No" ISINITIALIZE="No" ISOPTION="No" ISINTERNAL="No" NAME="Vouchers">
                        <TYPE> Vouchers : Vouchertype</TYPE>
                        <Childof>$$VchTypeSales</Childof>
                        <BELONGSTO>Yes</BELONGSTO>
                        <NATIVEMETHOD>*</NATIVEMETHOD>
                  
                    </COLLECTION>

                </TDLMESSAGE>
            </TDL>
        </DESC>
    </BODY>
</ENVELOPE>
     
    Sai Vineeth, Dec 22, 2021
    #2


  3. Sridharan S

    Sridharan S Member


    Check for the line <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>
    In some Xml exports it is not accepted (in Prime 2.0.1). What is more if you had used it first, that will cause some subsequent reports to fail. But that report will work separately. This is is a (confusing) Prime 2.0.1 bug.
     
    Sridharan S, Jan 5, 2022
    #3


Share This Page