TDL Selective Data & Balances
Budget: ₹3,000 – ₹5,000 INR
I already have a working TDL that exports every transaction from Tally into my desktop application. I now need the code trimmed and fine-tuned so it does only what the business actually uses:
• Data scope has to narrow to customer-related information—specifically the Sundry Debtors master—and just three transaction types: sales invoices, debit notes and credit notes. All other masters and vouchers (receipts, payments, purchases, suppliers, etc.) must be ignored in the new export routine.
• For each sales invoice, the script must also return the remaining balance after all receipts or adjustments have been applied. In other words, along with the usual invoice amount and date, I need the outstanding amount field calculated inside Tally and sent through the interface so my application can display up-to-date ageing.
All existing field names, object structures and XML/ODBC calls can stay unchanged where they still apply; I only want the filtering logic and the extra balance element added. Please deliver the updated .tdl file plus a brief note explaining any tags or collections you introduced so I can patch future builds without guesswork.
Once the modified script imports cleanly into Tally, pulls the three voucher types plus the Sundry Debtors master, and my application shows an accurate outstanding amount on every sales invoice, the job is done.
• Data scope has to narrow to customer-related information—specifically the Sundry Debtors master—and just three transaction types: sales invoices, debit notes and credit notes. All other masters and vouchers (receipts, payments, purchases, suppliers, etc.) must be ignored in the new export routine.
• For each sales invoice, the script must also return the remaining balance after all receipts or adjustments have been applied. In other words, along with the usual invoice amount and date, I need the outstanding amount field calculated inside Tally and sent through the interface so my application can display up-to-date ageing.
All existing field names, object structures and XML/ODBC calls can stay unchanged where they still apply; I only want the filtering logic and the extra balance element added. Please deliver the updated .tdl file plus a brief note explaining any tags or collections you introduced so I can patch future builds without guesswork.
Once the modified script imports cleanly into Tally, pulls the three voucher types plus the Sundry Debtors master, and my application shows an accurate outstanding amount on every sales invoice, the job is done.