Tally Customization

Field Level Attribute — Unique This attribute takes a logical value. If it is set to Yes, then the values keyed in the field have to be unique. If the entries are duplicated, an error message Duplicate Entry pops up. This attribute is useful when a Line is repeated over UDF/Collection, in order to avoid a repetition of values. Syntax Unique: [Yes / No] Example [!Field: VCHPHYSStockItem] Table : Unique Stock Item : $$Line = 1 Table : Unique Stock Item, EndofList Unique: Yes In this code snippet, the field VCHPHYSStockItem is an optional field in DefTDL, which is used in a Physical Stock Voucher. The attribute Unique avoids the repetition of Stock Item names. Field Level Attribute — Notify It is similar to attribute ‘Validate’. The only difference is that it flashes a warning message and the cursor moves to the subsequent field. A system formula is added to display the warning message. Syntax Notify : System Formula : Logical Condition Example [!Field: VCH NrmlB...

Data validation and controls in Tally can be done at two levels, either at the Platform level or at the TDL level. TDL Programmers do not have control over any of the Platform level validations. TDL Programmers can only add validation and controls at the TDL Level. Let us understand some of the TDL Level validation and control mechanisms. Field Level Attribute — Validate This attribute checks if the given condition is satisfied. Unless the given condition for ‘Validate’ is satisfied, the user cannot move further, i.e., the cursor remains placed on the current field without moving to the subsequent field. It does not display any error message. Syntax Validate : Logical Formula Example [Field: CMP Name] Use : Name Field Validate : NOT $$IsEmpty:$$Value Storage : Name Style : Large Bold In this example: The field CMP Name is a field in Default TDL which is used to create/ alter a Company.       Attribute ‘Validate’ stops the cursor from moving forward,...

A Page Break is the point at which one page ends and another begins. Handling Page Breaks is important, as the current page should indicate continuation to the next page, while the next page must indicate that the current page is continued from the previous page. So, there must be a closing identifier, i.e., closing page break information and an opening identifier, i.e., opening page break information. In other words, Page Breaks specify the headers and footers for every page, and are printed across multiple pages. Closing Page Break starts printing from the first page and prints on every page except the last page, e.g., Continued... to be printed at the bottom of each page. Opening Page Break starts printing from the second page till the last page. Closing Page Break is specified before Opening Page Break, since in any circumstance, closing page break is encountered first. In TDL, Page Breaks can be handled vertically as well as horizontally. Types of Page Breaks Vertical P...