What if the accounting software you use could be adapted to the way your business actually works? A business may need a different report, an additional field, a customised workflow, or a way to connect TallyPrime with another application. This is where TDL comes in. Tally Definition Language (TDL) is Tally's development language, designed to extend the capabilities of TallyPrime, customise its behaviour, and support integration with external applications.
What is TDL?
TDL, or Tally Definition Language, is the development language of TallyPrime. It allows programmers to extend the product's capabilities, customise it, and build integrations with external applications. At its core, TDL provides a development platform for working with TallyPrime. It provides capabilities for rapid development, rendering, data management, and integration.
TDL is closely connected to the Tally platform and can be used to shape how the product works for specific business requirements. It is an action-driven language based on definitions, with a strong emphasis on reusability. The concepts include interface and data objects, which serve different purposes within the application.
Why does TDL matter in TallyPrime?
TDL matters because businesses do not always work in exactly the same way, and developers can use it to extend TallyPrime for specific requirements. A standard accounting application needs to serve a wide range of businesses. But an individual organisation may have its own reporting requirements, fields, processes, or integration needs.
Tally's official TallyPrime Developer page highlights TDL's role in customisability and solution development, including the ability to modify reports, add fields, and create custom functionalities. This creates several possibilities for developers working with TallyPrime:
- Customisation: Adapt aspects of TallyPrime to specific business requirements.
- Reports: Develop or modify reports according to the required information or presentation.
- Additional fields: Add fields where a business needs information beyond the standard setup.
- Business functionality: Create customised functionality for specific requirements.
- Integration: Connect TallyPrime with external applications using supported integration capabilities.
The important point is that TDL provides a way to build on the existing TallyPrime platform rather than treating the product as a fixed, one-size-fits-all system.
How does TDL work?
TDL is based on definitions, attributes, modifiers, actions, data types, operators, symbols, prefixes, and functions, which work together to describe and control different aspects of a Tally solution. The language follows a different approach from conventional procedural programming. Tally's documentation describes TDL as a non-procedural programming language based on definitions.
Definitions are named and reusable, and they can also form part of other definitions. The language is also action-driven. When a user performs an action, a corresponding segment of code can be executed. Tally's documentation explains that actions are associated with elements such as menus, keys, and buttons and can perform predefined actions such as displaying, printing, creating, or altering information.
This definition-based and action-driven structure is central to understanding TDL. Instead of thinking of it simply as a general-purpose programming language, it is more useful to see TDL as a language designed around the Tally platform.
What are definitions in TDL?
Definitions are one of the central building blocks of TDL. They describe different elements of the Tally application and can be reused across solutions. Tally's documentation categorises definitions into several groups, including:
|
Definition category |
Examples or purpose |
|
Interface definitions |
Menu, Report, Form, Part, Line, Field, Button and Table |
|
Data definitions |
Object, Variable and Collection |
|
Formatting definitions |
Border, Style and Colour |
|
Integration definitions |
Import Object and Import File |
|
Action definitions |
Key |
|
System definitions |
System-level definitions |
Interface definitions are particularly important because they determine elements of the user interface. For example, Tally's documentation explains that a Report is a fundamental definition, while Forms, Parts, Lines, and Fields form a hierarchy within the interface.
The reusable nature of definitions is one of TDL's important characteristics. Developers can create definitions that can be used independently or become part of other definitions, helping support faster development and customisation.
What are attributes and modifiers?
Attributes describe the properties or behaviour of definitions, while modifiers allow developers to alter definitions or their corresponding attributes. A definition can have multiple attributes associated with it, and the attributes available depend on the definition being used. Tally's documentation describes attributes as the properties of definitions that determine their behaviour.
Modifiers provide another layer of flexibility. They can be used to alter existing definitions or attributes rather than requiring every customised element to be built independently. This distinction is useful when understanding how TDL can extend TallyPrime. Definitions provide the structure, attributes describe how those definitions behave, and modifiers provide ways to change or extend them.
What are actions in TDL?
Actions are instructions that activate specific functions in TDL, making them an important part of the language's action-driven approach.
Actions are performed primarily in the context of Report and Menu definitions. They are associated with an originator, requestor, and object, and can be initiated through menus, keys, or buttons. Examples documented by Tally include actions such as:
- Display
- Menu
- Create
- Alter
This gives TDL a direct relationship with user interactions inside the Tally environment. An action can determine what happens when a user selects a menu option, presses a key, or interacts with a button.
What data types does TDL support?
TDL supports data types designed for both general programming requirements and business information, including business-oriented types such as amount, quantity, and rate. Tally classifies its data types into simple and compound data types. Simple types include String, Number, Date, and Logical. Compound types include Amount, Quantity, Rate, Rate of Exchange, and Aggregate.
This business-oriented approach is significant because TDL works within an accounting and business application. The language needs to represent information that is common in business transactions, rather than dealing only with basic programming values.
What can TDL be used for?
TDL can be used to customise TallyPrime, create or modify reports and fields, develop business-specific functionality, and support integration with external applications. There are several areas where TDL fits within TallyPrime development:
- Customising the user experience
TDL can be used for custom user interfaces, reports, and validations within TallyPrime.
- Building business-specific functionality
Developers can create customised functionality to meet requirements that aren't addressed by the standard product setup.
- Supporting data handling
Tally identifies data management as one of TDL's core capabilities.
- Integrating with external applications
TDL can be used for integration with external applications, while TallyPrime also provides other integration methods depending on the requirement.
This makes TDL relevant not only when a business wants something to look different, but also when it needs TallyPrime to work differently within a broader business process.
TDL and TallyPrime Developer: What's the difference?
TDL is the development language, while TallyPrime Developer is the development environment designed for programmers working with TDL.
This distinction is important because the two terms are closely connected but refer to different things.
TDL is the language used to develop and customise solutions for TallyPrime.
TallyPrime Developer is the development suite that provides tools for TDL programmers to develop and deploy those solutions. Tally describes it as a comprehensive development suite for TDL and highlights capabilities such as programming support, debugging, project management, compilation, validation, and execution. In simple terms, TDL is the language, while TallyPrime Developer provides the development environment around it.
How does TDL support integration?
TDL can play a role in connecting TallyPrime with external applications, making it useful when accounting information needs to work alongside other business systems. TDL is TallyPrime's native language for customising the user interface, reports, and business logic. It also identifies TDL as one of the methods available for integration, particularly for in-product customisation and data handling.
TallyPrime also provides other integration methods and technologies. Therefore, the appropriate approach depends on what the business or developer is trying to achieve. The key takeaway is that TDL is not limited to changing screens or reports. It can form part of a broader solution where TallyPrime needs to interact with other applications or business processes.
Who uses TDL?
TDL is primarily relevant to developers and programmers who build, customise, or integrate solutions on the Tally platform. A business user does not necessarily need to understand TDL programming to use a TallyPrime solution customised through TDL. The language works behind the scenes to provide the required functionality.
For developers, however, understanding TDL opens up possibilities for creating solutions around TallyPrime. Tally provides a dedicated Developer Reference covering areas such as TDL, customisation, integration, definitions, functions, actions, and other development concepts. Tally also maintains release notes for TDL, covering enhancements and changes across TallyPrime releases. This is useful for developers who need to keep customisations aligned with newer versions of the platform.
Why is TDL important for TallyPrime customisation?
TDL gives the Tally platform a development layer through which programmers can extend standard capabilities and build solutions around specific business requirements. The value of TDL lies in its connection to the Tally platform. Instead of building an entirely separate accounting environment whenever a business needs a different report, field, workflow, or integration, developers can use TDL to extend the existing platform.
That makes TDL particularly relevant for businesses with specialised requirements and developers building solutions for the Tally ecosystem. It also explains why TallyPrime Developer and TDL sit at the centre of Tally's development platform: together, they provide the language and environment required to develop, customise, and deploy solutions for TallyPrime.
