text
stringlengths 0
5.42k
| source
stringclasses 1
value |
|---|---|
What's New in Release 2. 0 49 1 Figure 2. The Configuration Report Once the details are entered, a confirmation message is display ed to start the import process. If the user has selected the option to display the error report after successful import, the report is shown with imported stock items and status as “Imported success fully”, as seen in the figure: | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 492 Figure 3. Success Report If the user has selected the option to display the Log file, th en after the import, the log file is displayed as follows: Figure 4. Log File | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 49 3 The imported items are now available in the Stock Item list as follows: Figure 5. List of Stock Items | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 494 In case the import is unsuccessful, the error report, with the reason of failure, is displayed as follows: Figure 6. Error Report Solution Development The import from the excel file is simplified, as the user can s pecify the import details. The file I/O capabilities are used to develop the solution. The steps follow ed to achieve the requirement are: 1. A report is designed to display the configuration report. The value entered by the user is stored in a system variable. Local : Field : Name Field : Modifies : SIC Source : Yes Local : Field : Name Field : Variable : SIC Source | | Local : Field : Name Field : Modifies : SIC Dir Path : Yes Local : Field : Name Field : Variable : SIC Dir Path [System : Variable] SIC Source : “Excel” | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 49 5 SIC Dir Path : “C:\Tally. ERP9” 2. On form accept, the function to import the stock item is call ed. On : Form Accept : Yes : Form Accept On : Form Accept : Yes : Call : Smp Import Stock Items 3. A function “Smp Import Stock Items” is defined. a. n this function, first of all, the format of the source file is checked, and then, the action 'Open File' is used to open the file in 'Read' mode accordingly. 20 : IF : ##SICSource = “Excel” 30 : OPEN FILE : @@TSPLSMPTot File Path : Excel : READ40 : ELSE : 50 : OPEN FILE : @@TSPLSMPTot File Path : Text : READ 60 : ENDIF b. The data from the Excel cells are read and added as items in the list variable. 120 : WHILE : NOT $$Is Empty:($$File Read Cell : ##Row : + ##Item Columns. Item Name)130 : LIST ADD EX : Item Details 140 : SET : Item Details[$$Loop Index]. Item Name : $$File Read Cell : + ##Row : ##Item Columns. Item Name150 : SET : Item Details[$$Loop Index]. Item Grp : $$File Read Cell : + ##Row : ##Item Columns. Item Grp 160 : SET : Item Details[$$Loop Index]. Item UOM : $$File Read Cell : + ##Row : ##Item Columns. Item UOM170 : INCREMENT: Row 180 : END WHILE c. If source format is 'T ext', the text file is read line by li ne and added as items to the list variable. 210 : WHILE : NOT $$File Is EOF 220 : SET : Temp Var : $$File Read 230 : IF : NOT $$Is Empty:##Temp Var AND (NOT ##SICInc Header OR + (##SICInc Header AND $$Loop Index > 1)) 240 : LIST ADD EX : Item Details250 : SET : Item Details[##Counter]. Item Name : $$SICExtract Det: + | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 496 ##Temp Var : ##Item Columns. Item Name 260 : SET : Item Details[##Counter]. Item Grp : $$SICExtract Det : + ##Temp Var : ##Item Columns. Item Grp 270 : SET : Item Details[##Counter]. Item UOM : $$SICExtract Det: + ##Temp Var : ##Item Columns. Item UOM 280 : INCREMENT : Counter 290 : ENDIF300 : END WHILE d. A collection is populated using the List variable as data so urce. [Collection : TSPL SMP Imp Stock Item] Data Source : Variable : Item Details [Collection : TSPL SMP Imp Stock Item Summ] Source Collection : TSPL SMP Imp Stock Item By : SICStock Item : $Item Name By : SICStock Group : $Item Grp By : SICStock UOM : $Item UOM Filter : TSPL SMP Non Empty Item e. Now, the Stock Item objects are created. If the item can't be imported, then the item details are written in the error file or compound variable, based on the fo rmat selected for displaying, i. e., 'Report' or 'Log'. 380 : WALK COLLECTION : TSPL SMP Imp Stock Item Summ 390 : SET : Last Status : “” 400 : IF : $$Is Empty : $Name : Stock Item : $SICStock Item 410 : NEW OBJECT: Stock Item 420 : SET VALUE : Name : $SICStock Item430 : IF : NOT $$Is Empty : $Name : Stock Group : $SICStock Group 440 : SET VALUE : Parent : $SICStock Group450 : ELSE :460 : SET : Last Status : “Group” + $SICStock Group + “does not exist” | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 49 7 470 : ENDIF 480 : IF : NOT $$Is Empty:$Symbol:Unit:$SICStock UOM 490 : SET VALUE : Base Units : $SICStock UOM500 : ELSE :510 : SET : Last Status : “Unit” + $SICStock UOM + “does not exist” 520 : ENDIF530 : IF : $$Is Empty : ##Last Status 540 : SAVE TARGET 550 : SET : Last Status : “Imported Successfully” 560 : ENDIF 570 : ENDIF ;; Writing Import Status to the LOG File, if LOG File is to be displayed at the end 580 : IF : ##SICOpen Log File 590 : WRITE FILE LINE : $SICStock Item + ##SICText Sep + ##Last Status 600 : ENDIF ;; Updating List of Compound Variables is the Status is to be displayed in a Report 610 : IF : ##SICDisplay Report 620 : LIST ADD EX : Item Import Status 630 : SET : Item Import Status[##Counter]. Item Name : $SICStock Item 640 : SET : Item Import Status[##Counter]. Status : ##Last Status 650 : INCREMENT : Counter 660 : ENDIF 670 : END WALK f. If the format selected is 'Report', then the stock item name and the status is updated in a compound variable; whereas, if the format selected is Log file, then the action 'Write File' is used to write in the file. WRITE FILE LINE : $SICStock Item + ##SICText Sep + ##Last Status g. After import, if the user wants to display error report, a f unction is called to display the same. 690 : IF : ##SICDisplay Report 700 : DISPLAY : TSPL Smp SIC Error Report | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 498 710 : ENDIF h. After the import, if the user has selected to display the lo g file, then the log file is displayed. 720 : IF : ##SICOpen Log File 730 : EXEC COMMAND : @@TSPLSmp Error File Path 740 : ENDIF 4. The Error Report displays the reason of failure, if the Stock Item cannot be imported. In error report, the line is repeated over the collection populated, usi ng list variable as the data source. 1. 2 Function Parameter Changes-Optional Parameters Prior to this Release, while invoking a user defined function, it was mandatory to pass values to all the parameters declared within the function. Now, the capability has been introduced to have optional parameters. The function will execute smoothly even if the caller of the function does not pass the values to these optional parameters. However, the caller of the function must pass all the mandatory parameters. Only the rightmost parameters can be opti onal, i. e., any parameter from the left or middle cannot be optional. If the Parameter value is supplied by the calling Function, the n the same is used, else the default Parameter value provided within the 'Parameter' Attribute is us ed as the Parameter value. For this enhancement, the Function attribute ' Parameter ' has been modified to accept parameter value. Syntax [Function : <Function Name>] Parameter : <Parameter Name1> : <Data Type> Parameter : <Parameter Name2> : <Data Type>Parameter : <Parameter Name3> : <Data Type> [: Parameter Value] Parameter : <Parameter Name4> : <Data Type> [: Parameter Value] Where, <Parameter Name1> and <Parameter Name2> are mandatory parameters for which, values must be passed while calling the function. <Parameter Name3> and <Parameter Name4> are optional parameters for which, values may or may not be passed while calling the function. If values for these parameters are passed, the parameter value specified within the 'Parameter' Attribute is i gnored. In absence of these values, the specified parameter value is taken into consideration. Parameter Value indicates Optional Parameters, and all the Optional Parameters should be the rightmost elements of the function. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 49 9 Example: [Function : Split Vch No] ;; this Function returns the number pa rt of voucher number from a string ;; For e. g., Voucher Number is Pymt/1 10/2010-1 1. This F unction will return only '1 10'. Parameter : p Vch No : String Parameter : p Split Char : String : “/” ;; usual separator 00 : FOR TOKEN : Token Var : ##p Vch No : ##p Split Char 10 : IF : $$Loop Index = 220 : RETURN : ##Token Var 30 : ENDIF40 : END FOR While invoking the function $$Split Vch No, only the Voucher No is passed. The 2nd Parameter is optional and the default value is “/”. It is passed only if the separator character is other than “/”. Optional Parameters can be very useful where the Parameter valu es remain constant in most of the cases; and rarely require some change. 2. Variable Framework Enhancements In the prior releases, we have experienced major changes to the V ariable Framework in the form of introduction of Compound V ariables and List V ariables. Conti nuous enhancements and changes are being made to ensure consistency and uniformity acr oss the TDL framework. The following enhancements have taken place in variable framework r ecently. 2. 1 Variable Persistence at 'Report' Scope V ariables at 'report' scope can now be persisted into a user sp ecified file. This is stored in a standard variable format and also allows reloading the report s cope variables from the specified file. The Actions SA VE V ARIABLE and LOAD V ARIABLE have been int roduced for this purpose. Action-SAVE VARIABLE The action SA VE V ARIABLE is used to persist the Report Scope V a riables in a user specified file. Syntax SAVE VARIABLE : <File Name> [:<Variable List>]A small change has been done in the way function parameters are tokenized. The last parameter passed to the function is not broken up into sub-parts now. This is particularly useful in cases where we require the result of one function to be treated as a parameter to another function. In other words, if a function requires 4 parame-ters, it tokenizes only till 3 parameters and all the subsequent values are considered as the 4th parameter (last parameter). | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 500 Where, <File Name> is the name of the file in which the report scope variables are persisted. The extension. PVF will be taken by default, if the file extension is not specified. <Variable List> is the list of comma-separated variables that need to be persis ted in the file. Specifying the variable list is optional. Example: Let us assume that the variables Emp Name Var and Emp IDVar are declared at the Report Scope, and the same need to be persisted in a user specified fi le. We can achieve this using the newly introduced actions SA VE V ARIABLE and LOAD V ARIABLE. The buttons SA VEV AR and LOADV AR are added at the Form Level for the same. [Button : Save Var] Key : Alt + S Action : Save Variable : Smp Var. pvf : Emp Name Var, Emp IDVar The action SA VE V ARIABLE will persist the values of the variabl es Emp Name V ar and Emp IDV ar in the file Smp Var. pvf Action-LOAD V ARIABLE The action LOAD V ARIABLE is used to reload the report scope var iables from the specified file. Syntax LOAD VARIABLE : <File Name> [:<Variable List>] Where, <File Name> is the name of file in which the 'report' scope variables are p ersisted. The extension. PVF will be taken by default, if the file extension is not spe cified. <Variable List> is the comma-separated list of variables that need to be loaded from the file. It is optional. In case it is not specified, all the variables saved in the file will be loaded. Example: In the previous example, we have persisted values of the Report Scope V ariables Emp Name Var and Emp IDVar in the file Smp Var. pvf. N o w, let us see how to re-load these 'report' scope variables from the file. [Button : Load Var] Key : Alt + L Action : LOAD VARIABLE : Smp Var. pvf : Emp Name Var, Emp IDVar If the Variable List is not specified, all the variables at the 'Report' scope, which have 'Persist' attribute set to YES, will be persisted in the specified file. We need not declare the variable at System level unless it is required to persist the same in the default configuration file tallycfg. tsf. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 50 1 The action LOAD V ARIABLE will load the report scope variables Emp Name Var and Emp IDVar from the file Smp Var. pvf. 2. 2 Variable Copy The contents of a variable can now be entirely copied from one instance to another instance. Action-COPY V ARIABLE The action COPY V ARIABLE is used to copy the content from one v ariable (Source) to another variable (Destination). This action is supported for all types of variables (Simple/Compound/List V ariables). Syntax COPY VARIABLE : <Destination Variable> : <Source Variable> Where, <Destination Variable> is the name of the Simple/Compound/List V ariable. <Source Variable> is the name of the Simple/Compound/List V ariable, from which th e content has to be copied. Example: Copying from Simple Variable to Simple Variable [Function : Simple Var Copy Function] VARIABLE : Simple Var1 : String : “Employee1” VARIABLE : Simple Var2 : String 10 : COPY VARIABLE : Simple Var2 : Simple Var120 : LOG : “Source” + ##Simple Var1 30 : LOG : “Destination” + ##Simple Var2 In this example, the variables Simple Var1 and Simple Var2 are declared at the Function level. After execution of the action COPY V ARIABLE, the content of the variable is copied from Simple Var1 to Simple Var2. Example: Copying from Compound Variable to Compound Variable Let us suppose that the following compound variables are define d: [Variable : Employee1] Variable : Emp Name : String : “Praveen” Variable : Designation : String : “Manager”Member Variable Specification or Dotted Notation Specification is not allowed for specifying Variable list for both the ac tions SAVE VARIABLE and LOAD VARIABLE. It has to be a variable name identifier at the current report scope. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 502 [Variable : Employee2] Variable : Emp Name : String Variable : Designation : String In the function below, contents are copied from Compound V ariable Employee1 to Employ ee2: [Function : Compound Var Copy Function] VARIABLE : Employee1 VARIABLE : Employee210 : COPY VARIABLE : Employee2 : Employee1 20 : LOG : “Source” + ## Employee1. Emp Name 30 : LOG : “Source” + ## Employee1. Designation40 : LOG : “Destination” + ## Employee2. Emp Name 50 : LOG : “Destination” + ## Employee2. Designation Example: Copying from List Variable to List Variable Let us suppose that the following compound variables are define d:-[Variable : Employee1] Variable : Emp Name : String Variable : Designation : String [Variable : Employee2] Variable : Emp Name : String Variable : Designation : String In the following function, the compound variables Employee1 and Employee2 are declared as List Variable. We are copying all the elements from the compound list variabl e Employee1 to the compound list variable Employee2. [Function : List Var Copy Function] LIST VARIABLE : Employee1, Employee2 10 : LIST FILL : Employee1 : Employees : $Name : $Name The content will be copied from a member variable of a Compound Variable (Source) to another member variable of a compound variable (Destination), basedon the member variable names, since more than one member variable may have the same data type. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 50 3 20 : LIST FILL : Employee1 : Employees : $Name : $Designation + : Designation 30 : COPY VARIABLE : Employee2 : Employee1 40 : LOG : “Source Variable-Employee” 50 : FOR IN : KEY VAR : Employee1 60 : LOG : $$LISTVALUE:Employee1 : ##KEYVAR : Emp Name 70 : LOG : $$LISTVALUE:Employee1 : ##KEYVAR : Designation80 : END FOR 90 : LOG : “Destination Variable-Employee” 100 : FOR IN : KEY VAR : Employee2110 : LOG : $$LISTVALUE:Employee2 : ##KEYVAR:Emp Name 120 : LOG : $$LISTVALUE:Employee2 : ##KEYVAR:Designation 130 : END FOR 2. 3 Scope Specification in Variable Dotted Syntax The Dotted Notation Syntax for V ariables (##) has now been enha nced to allow specification of scope / relative scope, etc. Syntax.. (DOUBLE DOT) denotes owner scope... (TRIPPLE DOT) denotes owner's owner scope and so on (). denotes a system scope Where, <Definition T ype> is the name of the definition such as Report, Function, etc., i n the current execution chain. <Definition Name Expression> can be any expression which evaluates to a Definition Name. The Definition Name Expression is optional. (<Definition T ype>, <Definition Name Expression> ) can be used for absolute scope specification. The element (<Definition Type>, <Definition Name Expression>) has to be in the current execution chain, else one will not be able to refer to the same. Example: Let us suppose that the V ariable TSPLSMPScope Var is declared at System Scope. [Variable : TSPLSMPScope Var] Type : String [System : Variable] | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 504 TSPLSMPScope Var : “System Scope” The function TSPLSMP Scope Spec is called from a Menu. We have declared the variable TSPLSMPScope Var in the 'Function' scope also. [Function : TSPLSMP Scope Spec] VARIABLE : TSPLSMPScope Var 01 : SET : TSPLSMPScope Var : “Function Level” 02 : Display : TSPLSMP Scope Spec The following report is displayed from the function TSPLSMP Scope Spec. We have declared the variable TSPLSMPScope Var in the 'Report' Level also. [Report : TSPLSMP Scope Spec] Form : TSPLSMP Scope Spec Variable : TSPLSMPScope Var Set : TSPLSMPScope Var : “Report Level” Following are the field definitions of the report TSPLSMP Scope Spec. Let us see the variable values at the field level by specifying the scope in V ariable D otted Syntax. [Field : TSPLSMP Scope Spec Current] Use : Name Field Set As : ##TSPLSMPScope Var ;;Variable value in this field will be "Report Level" (Current Scope) [Field : TSPLSMP Scope Spec Owner] Use : Name Field Set As : ##.. TSPLSMPScope Var Border : Thin Left Right ;;Variable value in this field will be "Function Level" (Owner's Scope) [Field : TSPLSMP Scope Spec System] Use : Name Field Set As : ##(). TSPLSMPScope Var Border : Thin Left ;;Variable value in this field will be "System Level" (System Scope) [Field : TSPLSMP Scope Spec Absolute] | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 50 5 Use : Name Field Set as : ##(Function,“TSPLSMP Scope Spec”). TSPLSMPScope Var Border : Thin Left ;;Variable Value in this field will be "Function Level" (Absolute Specification) 2. 4 Definition Name and Instance Name of Variable can be diffe rent now A variable can be declared in a scope in two ways, i. e., either by specifying the name of the variable (in this case, a separat e variable definition is requi red) or by specifying the name of the variable and a data type (in this case, a separate variable definition is not required; and hence, is called as inline declaration). Let us look into the variable declaration syntax of Report Scop e. Syntax [Report : <Report Name>] ;;This syntax expects a separate variable definition in the same name Variable : <Variable Names> OR ;;Inline declaration Variable : <Variable Names> [:<Data Type>[:<Value>]] OR List Variable : <Variable Names> [:<Data Type>[:<Value>]] Example: [Report : SMP Report] Variable : Emp Name Variable : Emp Relation : String List Variable : Employee1List Variable : Employee2 : String :“Prem”[Variable : Emp Name] Type : String [Variable : Employee1] Variable : Emp Name : String In this chapter, we will go through the 'Report' Scope va riable declaration, syntax and examples. It is applicable for other scopes also. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 506 Variable : Emp ID : String Now, the 'Data Type' parameter can be pointing to a variable defini tion; in which case, it will allow one to have a variable which has the instance name and definiti on name different. This allows flexibility to create two instances of a compound structure in the same scope, with different instance names, without requiring to duplicate the definition. This capability is available at all the scopes where variable declaration is allowed. Existing Syntax [Report : <Report Name>] Variable : <Variable Names> OR Variable : <Variable Names> [:<Data Type>[:<Value>]] OR List Variable : <Variable Names> [:<Data Type>[:<Value>]] New Enhanced Syntax [Report : <Report Name>] Variable : <Variable Names> OR Variable : <Variable Names> [:<Data Type>[:<Value>]] OR List Variable : <Variable Names> [:<Data Type>[:<Value>]] OR Variable : <Instance Names> : [<Variable Name>] OR List Variable : <Instance Names> : [<Variable Name>] Where, <Instance Names> is the list of Simple/Compound/List V ariables separated by comm a (instance variables). <Variable Name> is the Simple or Compound variable name. A separate variable de finition is required. It should not be an inline variable. Example: 1Given here is the definition of a Compound V ariable “Employee”. [Variable : Employee] Variable : Emp Name : String Variable : Designation : String Now, we can create a variable instance using the definition of anot her variable. Let us understand this with the help of the following 'Report' definition: | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 50 7 [Report : Employee Report] ;;An instance is declared with the name as 'Prem' and definition name as 'Employee'. The variable instance 'Prem' will inherit the entire structure of the variable definition 'Employee'. Variable : Prem : Employee ;;An instance is declared with the name as 'Ramesh' and definition name as 'Employee'. Variable : Ramesh : Employee ;;Locally, the instance "Ramesh" is modified to add a member variable. Local : Variable : Ramesh : Add : Variable : Emp ID : String ;; Two instances are declared with the names "Kamal" and "Vimal", and the definition name as "Employee" Variable : Kamal, Vimal: Employee ;; A List Variable instance is declared with the na me "Employee List" and the definition name as "Employee" List Variable : Employee List : Employee Example: 2 [Report : TSPL SMP Variable Instance] Variable : Employee : String : “Suresh” Variable : New Employee : Employee In this example, we are trying to declare a variable instance ' New Employee', which is of the type of another variable 'Employee'. This will NOT work because the variable 'Employee' is declared as inline and an explicit Definition does not exist for the sam e. Hence, inline variables cannot be used to declare another varia ble instance. 2. 5 Use Case-Multiple Email Configurations Scenario ABC Company Ltd., a manufacturing company, is having the Head Office in Bangalore and branch offices in Delhi, Mumbai, Kolkata and Chennai. The compa ny uses T ally. ERP 9 at all the locations. The Head Office and Branch Offices are using the e-mail capabil ity of T ally extensively to send remainder letters, outstanding statements, etc., to the customers. The System Administrator at the Head office will be facilitatin g the Branch office staff for email configurations in T ally. The company is using its own mail server and also another mail server “SIFY”. If there is a change in the mail server, the system admin needs to communicate the information to branch staff, and they will be updating the emai l configurations in T ally. ERP 9. Now, the company wants to set the email configurations centrally fo r all the branches so that the branch staff need not struggle for email configurations, partic ularly when there is a change in the mail server. This solution provides the facility of saving multiple configu rations in multiple file names, and later loading them from the file, based on user sele ction. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 508 Requirement Statement Presently in T ally. ERP 9, users need to set email configuration s locally & update required details. Now, the configurations can be created centrally and shared among t he locations. Thus, the user need not set email configuration every time. They have to simpl y load the configuration from the file. This can be achieved using newly introduced actions SA VE V ARIABLE & LOAD V ARIABLE. Functional Demo Before looking into the design logic, we will have a functional demo. Let us suppose that ABC Company Ltd. is using its own mail serv er and another mail server Sify in its Head Office and its branch offices. Saving Email Configurations Let us suppose that the System Administrator in Head Office wan ts to save the required email configurations in T ally. ERP 9 for HO and Branches Gateway of T ally-> F12 (Configure)-> E-Mailing. The email configuration screen will appear as follows: Figure 7. Email C onfiguration Screen | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 50 9 The System Admin needs to save the configurations for mail serv ers abc and Sify. Hence, he has to specify Email server as “User Defined” and enter the require d configuration settings as follows: Figure 8. User Defined Configuration Now, the System Admin has to press Alt+S, or click on the Button Save Config. The following screen will appear, where he has to enter the configuration file name: Figure 9. Save Configuration Screen Once the System Admin accepts this screen, the configuration de tails will be saved in the file “abc. pvf”. Similarly, he has to create the Configuration for the mail server “Sify”. The files will be created in T ally. ERP 9 application folder, as shown in the following screenshot: Figure 10. Files in Application folder | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 510 The admin can share these two files to the staff in HO and Bran ch Offices, and they should place the file in the respective T ally. ERP 9 Application folders. Loading Configurations Gateway of T ally-> F12(Configure)-> E-Mailing. The Email configuration screen will be displayed with the previ ously set configurations. Now, the user at HO/Branch wants to load the configurations for the email server “abc”. He has to press Alt+L or click on the Button “Load Config”, and enter the file name, as shown in the figure: Figure 11. Load Co nfiguration Screen Accept the screen. The Email Configuration Report will display the con figuration details loaded from the file “abc”. Accept the configuration screen, and the s ettings will be applicable to all reports. Suppose the User now wants to mail the report Balance Sheet. He has to select 'Balance sheet' and press Alt + M. The following configuration report will appear: Figure 12. Email Configuration Screen Note that the configuration details are changed as per the sele cted configuration. Now, the user wants to change the email server as “Sify”. Go to Gateway of T ally-> F12(Configure)-> E-Mailing. Press Alt + L. Enter the file name as “Sify” and press Enter. The email configuration screen will have new configurations loaded from the file “Sify”. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 51 1 Similarly, we can save/load multiple configurations. Solution Development The steps followed to achieve Saving of Multiple Email Configur ations are: 1. Declaring variables at 'Report' Level V ariables SVMail Server Name, SVMail Server, SVMail Format, SVMail Use Ssl, etc., are declared at 'Report' Level. All these variables have the attribute Persiste nt set as YES at the Definition level. [#Report : EMail Configuration] Variable : SVMail Server Name, SVMail Server, SVMail Format, SVMail Use Ssl Variable : SVMail Use SSLOn Std Port, SVMail Auth User Name, SVExport Format 2. Saving Configuration A Button is added to the Form, and the action will call a User Defined Function. In a User Defined Function, we are executing a report to accept a File Name from the user. We are persisting all the report scope variables in the specified file through the Ac tion SA VE V ARIABLE. 3. Loading Configurations A Button is added to the Form and on clicking it, the action wi ll call a User Defined Function. In the User Defined Function, we are executing a report to accept the File name from the use r. We are reloading the report scope variables from the file through the Action LOAD V ARIABLE. Please refer to the following code snippet for Save and Load configura tions. [Function : TSPL Smp Save Load Var] Parameter : Is Save Var : Logical : Yes Variable : Config Namewith Ext : String : Yes 00 : EXECUTE : TSPL Smp Save Load Config ;; Correcting the file name entered with or without extension by the user 06 : IF: ##Save Load Config Name CONTAINS ". Pvf" 10 : SET : Config Namewith Ext : ##Save Load Config Name 20 : ELSE : 30 : SET : Config Namewith Ext : ##Save Load Config Name + ". pvf" 40 : ENDIF ;; Saving or Loading the variables based on parameter value 50 : IF : NOT $$Is Empty : ##Save Load Config Name 60 : IF : ##Is Save Var 70 : SAVE VARIABLE : ##Config Namewith Ext 80 : ELSE : 90 : LOAD VARIABLE : ##Config Namewith Ext | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 512 100 : ENDIF 110 : ENDIF The corresponding field values need to reflect the values of th e variables loaded from the file. This is handled by using the following code: Local : Field : DSPMail Server : Set as : + If #DSPMail Server Name Contains $$Sys Name:User Defined + Then ##SVMail Server Else + If #DSPMail Server Name NOT Contains $$Sys Name:User Defined + Then $$Get Mail Server Addr : #DSPMail Server Name + Else ##SVMail Server Local : Field : DSPMail Server Name : Set As : ##SVMail Server Name Local : Field : DSPMail Format : Set As : ##SVMail Format Local : Field : DSPMail Use Ssl : Set As : ##SVMail Use Ssl Local : Field : DSPMail Use SSLOn Std Port : Set As : ##SVMail Use SSLOn Std Port Local : Field : DSPMail Auth User Name : Set As : ##SVMail Auth User Name Local : Field : DSPFinal Export Format : Set As : ##SVExport Format Also, if the field values are changed, the Report level variabl es need to be modified with those values. This is handled us ing the following code: Local : Field : DSP Mail Server Name : Modifies : SVMail Server Name: Yes Local: Field : DSP Mail Server : Modifies : SVMail Server : Yes Local : Field : DSP Mail Format : Modifies : SVMail Format : Yes Local : Field : DSP Mail Use Ssl : Modifies : SVMail Use Ssl : Yes Local : Field : DSP Mail Use SSLOn Std Port : Modifies : + SVMail Use SSLOn Std Port : Yes Local : Field : DSP Mail Auth User Name : Modifies : + SVMail Auth User Name : Yes Local : Field : DSP Final Export Format : Modifies : + SVExport Format : Yes On Accepting of the Form EMail Configuration, we are calling a User Defined Function to set the System V ariable values. Thus, the changed configuration details will be available for all the reports. Please refer to the following Code Snippet: | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 51 3 [Function : TSPL Smp Update System Variables] 10 : SET : (). SVMail Server Name : ##SVMail Server Name 20 : SET : (). SVMail Server : ##SVMail Server 30 : SET : (). SVMail Format : ##SVMail Format 40 : SET : (). SVMail Use Ssl : ##SVMail Use Ssl 50 : SET : (). SVMail Use SSLOn Std Port : ##SVMail Use SSLOn Std Port 60 : SET : (). SVMail Auth User Name : ##SVMail Auth User Name 70 : SET : (). SVExport Format : ##SVExport Format 3. Event Framework Enhancements This is a path-breaking enhancement in T ally which will enable scheduled execution of any Action. This has been supported with the introduction of a System Event called Timer. We can have a set of timer events of specified durations and trigger an Action on the same. For example, if we require Synchronization to be triggered at every one hour, we can define a Timer event which triggers the action 'Sync'. Actions for Starting and Stopping t he timer have been provided. 3. 1 Timer Event As we are already aware, Events like System Start, System End, Load Company, Close Company, On Form Accept, etc., introduced earlier as a part of the Event Framework, req uire user intervention. Automated events which can be used to take t imely backups, display automated messages, etc., were not possible earlier. With the breakthrough introduction of Timer Event, performing Timer based automated events is possible now. System Event Timer has been introduced to perform the required set of operations automatica lly at periodic intervals. Syntax [System : Event] <Timer Name> : TIMER : <Condition> : <Action> : <Action Parameters> Where, <Timer Name> is the user defined name for the timer event. <TIMER> keyword indicates that it is a Time-based event. <Condition Expr> should return a logical value. <Action Keyword> is any one of the actions. <Action Parameters> is nothing but the parameters of the action specified. We can have multiple Event Handlers with unique names which can invoke specific Actions at different intervals. In order to specify the interval for the v arious Timers and to begin and end the Timers, the associated Actions introduced are 'Start Timer' and 'Stop Timer'. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 514 Actions-Start Timer and Stop Timer Action-START TIMER It starts the specified timer and accepts the Timer Name and Du ration in seconds as the action parameters. Syntax START TIMER : <Timer Name> : Duration in seconds Where, <Timer Name> is the user defined name for the timer event. Action-STOP TIMER This Action stops the specified timer, and it accepts the Timer Name as its parameter. Syntax STOP TIMER : <Timer Name> Where, <Timer Name> is the user defined name for the timer event. Following is an example of scheduling automatic backups every h our: Example: [System : Event] ;; Setting up timer event to call a function Auto Backup : TIMER : TRUE : CALL : Take Backup Function ;; Starting the Timer when T ally Application Starts Schedule Backup : System Start : TRUE : START TIMER : Auto Backup : 36 00 ;; Adding Keys to 'Company Info' Menu [#Menu : Company Info. ] Add : Keys : Stop Backup Timer ;; Declaring a Key to Stop the Timer [Key : Stop Backup Timer] Key : Alt + S Action : Stop Timer : Auto Backup Title : “Stop Backup” In this example, following is done: Auto Backup, a Timer Event is declared under System Event to invoke the Function T ake Backup Function at periodic intervals, as specified within the Action Start Timer. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 51 5 Schedule Backup, a System Start event is declared under System Event to Start the above Timer 'Auto Backup' and execute the specified action every 3600 Seconds, i. e., every hour. A corresponding Key to Stop the Timer is associated to Menu Company Info, which is defined to Stop the Timer. User can stop the timer if he chooses not to continue taking automatic backups any further. Timer Events can be very useful in many cases like displaying Exception Repo rts, Negative Balances intimation, Inventory Status below Minimum or Reorder Level, Outstanding Reminders, Auto Sync at regular intervals, and many more. 4. Action Enhancements New actions have been introduced in this release, viz. Refresh Data, Copy File and Sleep. 4. 1 Action-Refresh Data In T ally, whenever any report is being viewed, it contains the most rece nt updates till the last entry. If any report is left open and subsequently viewed later, possibly few more entries would have gone in the system entered by various other users on the Networ k. Hence, the report which is currently being viewed is older. T o view the updated report, the user has to exit the report an d once again, enter the Report. T o solve this problem, a new acti on 'Refresh Data' has been introduced, which refreshes the data in memory automatically, as and when required. Syntax REFRESH DATA Refresh Data can be used along with Timer Event and every few seconds, the Report can be refreshed automatically to display the updated information. Example: [System : Event] Refresh Timer : TIMER : TRUE : Refresh Data [#Form : Balance Sheet] Add : Keys : Enable Refresh [Key : Enable Refresh] Key : Alt + R Action : Start Timer : Refresh Timer : 300 In this example, Refresh Timer, a Timer Event is declared under System Event to invoke the Action Refresh Data at periodic intervals. A key Enable Refresh is added in the Balance Sheet Report, which will be used to Start the Timer Refresh Timer every 5 minutes. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 516 4. 2 Action-SLEEP Action SLEEP has been introduced to specify time delays during the execution of the code. For few seconds, the system will be dormant or in suspended mode. Syntax SLEEP : <Duration in Seconds> <Sleep> is the action which halts the functioning of the Application fo r a few seconds as specified in <Duration>. Example: [#Menu : Gateway of Tally] Add : Item : Trial Balance after 10 secs : CALL : TBafter Sleep[Function : TBafter Sleep] 00 : SLEEP : 1010 : DISPLAY : Trial Balance In this example, the system will halt for 10 seconds and display the Trial Bala nce subsequently. 4. 3 Action-Copy File A new Action 'Copy File' has been introduced, which allows: Copying from one location to another within the same System Uploading of Files from a given Path to a FTP Site Downloading of File from FTP Site to the specified location/fol der Syntax Copy File : <Destination File Path> : <Source File Path> Where, <Destination File Path> can be any expression evaluating to a valid local/FTP path. <Source File Path> can be any expression evaluating to a valid local/FTP path. Example: Copy File : ##My Dst File Path : ##My Source File Path If any of the File path is an FTP path, the same can be constructed using functions like $$Make FTPName. It accepts various parameters like servername, u sername, password, etc. The following code snippet sets the value of the variable My Dst File Path using the function The Action 'Refresh Data' is a Company R eport-Specific Action. It will always require a Report in memory to Refresh the Data. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 51 7 $$Make FTPName. SET : My Dst File Path : $$Make FTPName : ##SVFTPServer : ##SVFTPUser : + ##SVFTPPassword : @SCFile Path Name The function $$Make FTPName uses the various parameters which ar e System V ariables captured from the default configuration reports. 5. TDL Enhancements for Remoting There have been various enhancements at the TDL level to enable Remote Edit Capability in the product. The enhancements are as follows: 'Fetch Object' Attribute Changes The attribute 'Fetch Object' has been supported at Report, Form, Field and the Function level as well. The Object Name specification in the syntax allows expres sions now. It is also possible to specify multiple Object Names separated by the Fetch Separator Character. A n e w f u n c t i o n $$Fetch Separator has been introduced to return this character. 'Fetch Values' Attribute Introduced The evaluation of External Methods of an Object requires Object Context to be available at the Client End. A new Attribute 'Fetch V alues' has been provided at the 'Report' level to specify the list of External Methods. 'Multi Objects' Attribute Introduced Whenever multiple Objects of the same collection are getting mo dified at the Client's End, a new attribute called 'Multi Objects' is introduced at the Report Lev el to enable the same. 'Modifies' Attribute Changes The 'Modifies' attribute of the field has been changed to accep t a third parameter (optional) which is an expression. This allows the variable to be modified with the value of the expression rather than the field value. Collection Attribute 'Parm Var' Introduced As we already know, the 'Collection' Artefact eval uates the various attributes eit her during initialization or at the time of gathering the collection. It m ay require various inputs from the Requestor context for the same. The direct reference of values/expressions from the report elem ents and objects in the collection at various points creates various issues like code complexity, performance lapses and non availability of these values on Server in Remote Environment. In order to overcome these, a new Collection attribute 'Parm V ar' has been introduced. 'Pa rm V ar' in collection is a context-free structure available within the collection. The requestors Object context is available for the evaluation of its value. This is e valuated only once in the context of the caller/requestor. This happens at collection initialization, and the expression provided to it is evaluated and stored as a variable, which can be referred withi n any of the attributes of the collection anytime, and is made available at the Server end as well. | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 518 Lets understand each of these in detail. 5. 1 'Fetch Object' Attribute Changes When multiple methods of a Single Object/Multiple Objects of th e same type are required, then that Object can be fetched at Report, Form, Field and Function levels. Report Level 'Fetch Object' attribute has been enhanced at 'Report' level to take an expression instead of a variable name that evaluates to the name of an object. The existing syntax of the 'Fetch Object' attribute at report l evel is as follows: Syntax: Prior to 2. 0 Fetch Object : <Object Type> : <Variable Identifier > : <List of methods> Example: Fetch Object: Ledger: Ledger Name: Name, Parent, Closing Balance Syntax: 2. 0 Onwards Fetch Object : <Object Type> : <Expression> : <List of methods> Example: Fetch Object: Ledger: ##Ledger Name: Name, Parent, Closing Balance Here, since the Object name is an expression, we need to prefix the variable name with ##. Form Level Attribute 'Fetch Object' has been introduced at 'Form' Level. I n scenarios where multiple forms are available at a report; for each form, we require to fetch m ethods pertaining to different objects. Syntax Fetch Object : <Object Type> : <Expression> : <List of methods> Example: [!Form : Accouting View Voucher] Switch : Acc Voucher View : Normal Accouting View Voucher : + NOT$$Is Attendance : ##SVVoucher Type Switch : Acc Voucher View : Attd Accouting View Voucher : + $$Is Attendance : ##SVVoucher Type [!Form : Attd Accouting View Voucher] Fetch Object : Attendance Type : @@Attd Entry List : + Attendance Production Type, Attendance Period, Base Units [!Form : Normal Accouting View Voucher] Fetch Object : Ledger : @@All Led Entry List : Name, Parent, Reserve Name | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 51 9 Field Level There may be scenarios where we may need to Fetch Object values dynamically based on the current field values. For example, the field may be associated with a T able of ledgers. Based on the ledger selected, the corresponding methods of the Object re quire to be fetched. I n s u c h cases, this attribute will be useful. Syntax Fetch Object : <Object Type> : <Expression> : <List of methods> Example: [Field : LED VAT Class] Fetch Object : Tax Classification : $$Value : First Alias, Rateof VAT, + Tax Type Function Level There may be scenarios where the method values need to be fetch ed based on the Object name passed as a parameter to the function. In such cases, 'Fetch Ob ject' at the function level is required. If we have already fetched the object methods at the 'Report' o r 'Field' level, the same will be propagated to the called function. In case it is not fetched ea rlier, the same can be fetched at the 'Function' level as well. This enables dynamic fetching of Obje cts. Syntax Fetch Object : <Object Type> : <Expression> : <List of methods> Example: [Function : Fill Using Tracking Obj] Parameter : p Track Key : String Fetch Object : Tracking Number : ##p Track Key : *. * In case the same set of methods for multiple objects needs to b e fetched, the multiple Object Names need to be specified in the syntax of 'Fetch Object', sep arated by the Fetch separator character. Function-$$Fetch Separator This function returns C_FETCH_SEP ARA TOR character that is used for separating multiple object names in FETCH OBJECT attribute. There may be scenarios w here the same set of methods needs to be fetched from multiple objects. In that case, it is possible to specify multiple object names in the 'Fetch Object' syntax, separated by the cha racter which is returned from the function $$Fetch Separator. Example: Fetch Object : Ledger : “Debtor North” + $$Fetch Separator + “Debtor South” : Name, Parent, Closing Balance | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 520 5. 2 'Fetch Values' Attribute Introduced This is a report level attribute which allows computation of va lues for user defined (external) methods, based on the current Object context available. Syntax Fetch Values : <List of methods> Example: [Report : VAT Classification] Object : Tax Classification Fetch Values : Master ID, Can Delete 5. 3 'Multi Objects' Attribute Introduced This is a 'Report' level attribute which is required to be spec ified, in case Multiple Objects of the same collection are being added/modified in a Report. It is req uired specifically in case of multi master creation or alteration. Syntax Multi Objects : <Edit Collection> Where, <Edit Collection> is the name of the Collection for which modifications are to be done. Example: [Report : Multi Ledger] Multi Objects : Ledger Under MGroup 5. 4 'Modifies' Attribute Changes This is a field level attribute enhanced further to take a thir d optional parameter. P r i o r t o T ally. ERP 9 Release 2. 0, if a field had 'Modifies' parameter, the field value would be set to the variable. And based on this variable value, some calculations o r concatenation was required to be performed. An invisible field was required for the same. With the enhance ment in this Release, one can modify the variable value at the same field itself usin g an expression, i. e., the field, and the variable may have different values. Syntax: Prior 2. 0 Modifies : <Variable Name> : <Logical Value> Where, <Variable Name> is the name of the variable. <Logical Value> is any expression which evaluates to a logical value. Example: [Field : Batches In Godown] Modifies : DSPGodown Name : Yes | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 52 1 Syntax: 2. 0 onwards Modifies : <Variable Name> : <Logical Value> : <expression> Where, <Variable Name> is the name of the variable. <Logical Value> is any expression which evaluates to a logical value. <Expression> can be used to modify the variable value within the field. Example: [Field : Batches In Godown] Modifies : DSPGodown Name : Yes : ##DSPGodown Name + “-Godown” Here, considering that the field value is 'Main location', outp ut would be Main location-Godown. 5. 5 Collection Attribute 'Parm Var' Introduced As we already know, the 'Collection' Artefact eval uates the various attributes eit her during initialization or at the time of gathering the collection. It m ay require various inputs from the Requestor context for the same. For example, the evaluation of 'Child of' and 'Filter' attribu tes happens at the time of gathering the collection. It requires certain value s from Requestors context like $name. In 'Filter' attribute, if $name of each object is to be compared with $name of the Requestors context, then we have to refer it as $Req Object:$name. The dire ct reference of values/expressions from the report elements and objects in the collection at various points, creates a few issues as follows: Code complexity is increased, as observed in the Filter example above. The performance is impacted, as there is are repeated references in case of Filters. In a Remote Environment; where the Requestor Context is not ava ilable within the collec-tion at the Server side In order to overcome the above, a new Collection attribute 'Par m V ar' has been introduced. We already have the capability of declaring inline variables at collection level using the Attributes Source V ar, Compute V ar and Filter V ar. These are context free structures available within the collection for various evaluations. For storing values in these, the various object contexts available are Source Objects, T arget Objects, etc. One more attribute called 'Parm V ar' has been introduced in collection, which is a context-free structur e available within the collection. The request- ors Object context is available for evaluation of its value. Th is is evaluated only once in the context of caller/requestor. This happens at collection initialization and the expression provided to it is evaluated and stored as a variable which can be referred within any of the attributes of the collection anytime, and is made available at the Server end by passing it with the XML Request. Collection Attribute-Parm Var The attribute Parm V ar evaluates the value of the variable based on the requestor object's context. Syntax Parm Var : <Variable Name> : <Data Type> : <Formula> | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 522 Where, <Variable Name> is the name of variable. <Data T ype> is the data type of the variable. <Formula> can be any expression which eval uates to the value of 'V ariable ' data type. Example: [Part : Groups and Ledgers] Lines : Groups and Ledgers Repeat : Groups and Ledgers : List of Groups Scroll : Vertical [Line : Groups and Ledgers] Fields : GAL Particulars Right Fields : GAL Clos Bal Explode : List of Ledgers : ##Explode Flag [Part : List of Ledgers] Lines : List of Ledgers Repeat : List of Ledgers : Smp List of Ledgers [Collection : Smp List of Ledgers] Type : Led ger Child Of : $Name In the collection Smp List of Ledgers, the Child of attribute is evaluated based on the method $Name which is available from the Group Object in context. The line Groups and Ledgers (Requestor Object) is associated with a Group Object. In a Remote environment, when such a Report is being displayed at the Clients end, the request for the collection gathering goes to the Server End. At the ser ver end, the Requestor Context is not available. So, the evaluation of $Name will fail. T o overco me such a situation, a new attribute called “Parm V ar” has been introduced, which is a context-free structure available within the collection. It evaluates the expression based on the Requestors Context, thereby available at the Server Side also. The Collection is Redefined as follows using the attribute Parm Var [Collection : Smp List of Ledgers] Type : Ledger Child Of : ##Parm Led Name | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 52 3 Parm Var : Parm Led Name : String : $Name The value of variable “Parm Led Name” is evaluated at the Client side based on method $name available from Group Object Context, and sent to the Server. While gathering the objects at the server side, the attribute 'Child Of' is evaluated, which uses t he variable Parm Led Name instead of $Name, available at the Server. 6. Default TDL Changes In the release 2. 0, many new features like Remote Edit, SMS support, etc., have be en introduced. The TDL language is also enriched with new capabilities to supp ort these features. Using the new language capabilities, the source code of T ally. ERP 9 Release 2. 0 has also been enhanced. The changes have been made in many definitions. For example, the va lues of some of the attributes have been changed, new attributes have been added and formulas have been rewritte n. Although, it has been tried to ensure maximum backward compatib ility, there may be cases where the application developer may require to validate/rewrite the e xisting TDL codes to make them compatible with T ally. ERP 9 Release 2. 0. In this section, the c hanges have been summarised in t e r m s o f l i s t i n g t h e d e f i n i t i o n s. A l t h o u g h s i n c e r e e f f o r t s h a v e been made in the direction of providing a comprehensive listing of definitions, one may come across a few cases where changes have been made. If any of these definitions are being u sed in customisations, one must refer to the source code changes available with the latest Rele ase of TDE. 6. 1 Mandatory 'Fetch' at the Collection Level This release onwards, Fetch is mandatory in every collection. All the methods which are req uired to be used in a Report are to be fetched at the Collection leve l. 6. 2 V oucher Creation Whenever a new Voucher is being created, it is important to tak e care of the following: The variable name “SVView Name” has to be set to System Names Acctg Vch View-For all Accounting vouchers Inv Vch View-For all Inventory vouchers, except Stock Journal v oucher Pay Slip Vch View-For Payroll vouchers Cons Vch View-For Stock Journal voucher The method 'Persisted View' has to be set to the value of the va riable 'SVView Name'. Example: ds : Set : SVView Name : $$Sys Name : Acctg Vch View 10 : NEW OBJECT : Voucher | | Aa : Set Value : Persisted View : ##SVView Name30 : CREATE TARGET | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 524 6. 3 Extract Collections List and Usage as T ables Many existing 'collection' definitions have been converted as E xtract Collections. So, if these collections are used in any of the user TDLs, the code needs to be rewritten for T ally. ERP 9 Release 2. 0. Many fields which were using the old collections a s T ables have been modified to use the Extract Collections now. The 'T able' Attribute has been changed for those fields. The following T able shows the fiel ds in which extract collectio ns are used in the 'T able' attribute: Field Name Table Name OLD Extract Collection/Table Name EI Acc Alloc Name Inv Sales Ledgers Alloc Inv Purch Ledgers Inv Sales Income Ledgers Inv Purch Expense Ledgers Non Inv Purch Support Ledgers Non Inv Sales Support Ledgers Inv Sales Ledgers Alloc Extract Inv Purch Ledgers Vch Extract Inv Sales Income Ledgers Extract Inv Purch Expense Ledgers Extract Non Inv Purch Support Ledgers-Vch Extract Non Inv Sales Support Ledgers-Vch Extract EI Consignee Party Ledgers, Cash Ledgers Invoice Ledgers Party Cash Ledgers Extract Invoice Ledgers Extract EICommon LED Inv Sales Ledgers Inv Purch Ledgers Inv Sales Income Ledgers Inv Purch Expense Ledgers Inv Sales Ledgers Extract Inv Purch Ledgers Extract Inv Sales Income Ledgers Extract Inv Purch Expense Ledgers Extract VCH VATClass VCH VAT Sales Classification VCH VCH VAT Purc Classification VCH VCH VAT Sales Classification VCH Extract VCH VAT Purc Classification VCH Extract VCH Acc Alloc VAT Class VCH VAT Sales Classification VCH VCH VAT Purc Classification VCH VCH VAT Sales Classification VCH Extract VCH VAT Purc Classification VCH Extract VCH POS Party Contact Party Ledgers Party Ledgers Extract VCHACC Stock Item Vch Stock Item Vch Stock Item Extract VCHJRNLStock Item Vch Stock Item Vch Stock Item Extract ACGLLed Gain Loss Ledgers Gain Loss Ledgers Extract ACLSFixed Led Cash Class Ledgers Cash Class Ledgers Extract | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 52 5 ACLSLed Cash Ledgers Normal Ledgers Normal Ledgers, Cash Ledgers Non CENVAT Ledgers Non CENVAT Ledgers, Cash Ledgers, Cash Ledgers Vch Extract Normal Ledgers Extract Normal Cash Ledgers Extract Non CENVAT Ledgers Extract Non CENVAT Cash Ledgers Extract EI Acc Desc Sales Support Ledgers Purchase Support Ledgers Sales Support Ledgers Vch Extract Purchase Support Ledgers Vch Extract VCH Acc VATClass SD Sales Classification Etc... SD Sales Classification Extract Etc... VCHIndent Stock Item Vch Stock Item Vch Stock Item Extract VCHBATCH Godown Stockable Godown JOB Stockable Godown Stockable Godown Vch Extract JOB Stockable Godown Vch Extract VCHBATCH Ordr Name Active Batc hes Active Batches Vch Extract VCHBATCH Nrml Name Active Batc hes Active Batches Vch Extract VCHBATCH Jrnl Name Active Batc hes Active Batches Vch Extract EI VATClass SD Sales Classification VCH VAT Sales Classifica-tion VCH VCH VAT Purc Classification VCH VAT Sales With Rate Classification VCH VAT Purc With Rate Classification VCH Addl VAT Sales With Rate Classification VCH Addl VAT Purc With Rate Classification VCH Cess On VAT Sales With Rate Classification VCH Cess On VAT Purc With Rate Classification VCH CST Sales With Rate Classification CST Purc With Rate Classification SD Sales Classification Extract VCH VAT Sales Classification VCH Extract VCH VAT Purc Classification VCH Extract VAT Sales With Rate Classification VCH Extract VAT Purc With Rate Classification VCH Extract Addl VAT Sales With Rate Classification VCH Extract Addl VAT Purc With Rate Classification VCH Extract Cess On VAT Sales With Rate Classification VCH Extract Cess On VAT Purc With Rate Classification VCH Extract CST Sales With Rate Classification Extract CST Purc With Rate Classification Extract VCHBATCH GRNName Active Batches Active Batches Vch Extract POS Batch Name Active Batches Active Batches Vch Extract VCHBATCH Dealer Godown Stockable Dealer Godown Stockable Dealer Godown Vch Extract VCHBATCH Excise Mfgr Godown Stockable Excise Mfgr Godown Stockable Excise Mfgr Godown Vch Extract | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 526 VCHBILL TDSLedger TDS Ledger Table TDS Ledger Table Vch Extract VCHBILL STax Ledger Service Tax Ledger Table Service Tax Ledger Table Vch Extract VCHCSTCAT Name Voucher Cost C ategory Voucher Cost Category Vch Extract VCHCST Name Cost Centre All Cost Cen-tre Cost Centre Vch Extract All Cost Centre Vch Extract STKVCH Ledger Party Ledgers, Cash Led-gers Party Cash Ledgers Extract PF Cash Bank Ledger Cash Ledgers Cash Ledgers Vch Extract VCH Attd Emp Name Payroll Deactvation Employees Payroll Deactvation Employees Extract VCH Attd Type List of Attendance Types List of Attd Types Extract VCH Auto Attd Type List of Attendance Types List of Attd Types Extr act VCH Emp Name Payroll Cost Centres Manual Vch Employees Under Category Payroll Cost Centres As VCHExtract Manual As Vch Employees Under Category Extract PAYROLLFixed Led Payroll Liab Ledger s Payroll Liability Ledgers E xtract Payroll VCH Emp-Cat-Particulars List of Cost Categories List of Cost Categories Extract Payroll VCH Emp-Par-ticulars Payroll Cost Centres Manual Vch Employees Under Category Payroll Cost Centres VCHExtract Manual Vch Employees Under Category Extract Payroll VCHPayhead Name Vch Pay Heads Vch Pay Heads Extract Payroll Function Auto- Category Name Payroll Vch Categories Payro ll Vch Categories Extract Payroll Function Au-to C-st Tables Payroll Cost Centres Auto Vch Employees Under Category Auto Vch Pyrl Cost Centres VCHExtract Auto Vch Employees Under Category Extract Payroll Function Auto- Payhead Name Payroll Ledgers Auto Vch Payroll Ledgers Extract TDSAuto Ledger Normal Ledgers Normal Ledgers Extract TDSFilter Bank Cash Class Ledgers Cash Class Ledgers Extract EI Track Order Inv Sales Orders Inv Purc Orders Inv Sales Orders, Not Applicable, End Of List, New Number Inv Purc Orders, Not Applicable, End Of List, New Number | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 52 7 6. 4 Modified Definition Li st and corresponding Changes Changes in 'Set As'EI Sales Order Inv Sales Orders Inv Purc Orders Inv Sales Orders, Not Applicable, End Of List, New Number Inv Purc Orders, Not Applicable, End-Of List, New Number SRVTParty Name Service Party Ledgers Service Party Ledgers Extra ct SRVTParty Bill Name Pending Party Bills Pending Party Bills Extra ct Definition Type Definition Name Part VCH Excise Sub Cat Tax Rate Trader Purc Typeof Duty VCH Excise Sub Cat Tax Rate Field VCH Excise Sub Cat Tax Rate Trader Purc Typeof Duty TDS Tax Party Ledger VCH Tax Pymt Details Trader PLARG23Sl No Trader Supplier RG23No Trader Original Ref No Trader Mfgr Impr Name Trader DN Supplier Inv No Trader DN Supplier Inv Date Trader DN Natureof Purc Trader DN Qty Purchased Trader DN Qty Return Trader DN Assessable Value Trader CN Supplier Inv No Trader CN Sales Inv Date Trader CN Sales Inv No Trader CN Qty Sold Trader CN Qty Return Trader CN Spl AEDOf CVDNot Pass On Dealer Inv Amtof Duty Dealer Inv Duty Per Unit | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 528 Options Added-In Alter Mode In the definition [Form: V oucher], the option for 'Alter' mode is added and it is used to list a ll the fetches. 'Fetch Object' Added: 'Compute Var' and 'Fetch' Attributes Added Definition Type Definition Name Form Voucher Definition Type Definition Name Field VCH Stock Item Definition Type Definition Name Collection Vouchers of FBT Category Calc Memo Vouchers of FBT Category Calc FBTCategory Calc Vouchers of Regular FBT Category Calc Vouchers of Recovered FBT Category Calc VCHIn TNo VCHIn TNo G VCHIn TNo BVCHIn TNo BG VCHOut TNo VCH Out TNo GVCH Out TNo B VCH Out TNo BG Tax Bill Details Pay Function Cateroty Collection Pay Function Employee Collection All Stat Ledgers Slab Summary All PFStat Ledgers Admin Auto Fil Jrnl Employees Auto Fil PF Ledgers Admin Auto Fil Employees Admin Auto Payable Coll Admin Auto Payable Coll Payroll Src | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 52 9 Admin Auto Payable Coll Jrnl Admin Auto Payable Coll Jrnl Src PFESI Employee Filter Summary PFESI Employee Filter Vouchers Excise RG23DNo Coll Trader List Of Purc Cleared Trader List Of Purc Non Cleared Trader List Of Multi Purc Cleared Trader List Of Multi Purc Non Cleared Excise Dealer Inventory Entries Excise Dealer Invoice Inventory Entries TDS Deduct Same Voucher TDS Tax Obj Party Bills TDS ITIgnore NOP TDSDuty Led Table Tax Obj Agst Table Debit Note Tax Obj Agst Table SRCTax Obj Agst Table TDS Common Party Ledger Tax Obj Adv Agst Table Tax Obj Ded Table Pending TCS Bills Pndg Tax Bills Till Cur Vch Date Tax Bill Coll TCS Vouchers of Party Pending Tax Bills Bank Coll Inv Sales Orders Excise Inv Sales Orders Inv Purc Orders Inv Out Track Numbers Inv In Track Numbers Pending Sales Orders VCHSo Pending Purc Orders VCHPo | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 530 Few Attributes added and 'Debug Exec' Action Used VCH Out TNo Src In Pending Tracking Numbers Out Pending Tracking Numbers Pending Bills STX Sale Pending Tax Obj Pending STax Party Bills STX Cr Dr Note Pending Tax Obj STX Categorywise Pending Tax Obj STX Rcpt Pending Tax Obj STXSource STX Sale Pending Tax Obj STX JV Sale Pending Tax Obj STXTax Obj Output GAR7Pymt Alloc STXTax Obj Input GAR7Pymt Alloc Definition Type Definition Name Function ESIDeduction Pay Function ESIEligibility Pay Function ESIContribution Pay Function PFNormal Pay Function PTNormal Pay Function PTMonthly Pay Function First EPF12Pay Head Abs Val Function First EPF833Pay Head Abs Val Function PFNormal Vch Pay Function PTMonthly VCHPay Function PTNormal Vch Pay Function ESIDeduction Vch Pay Function ESIEligibility VCHPay Function ESIEligibility On Current Earn Vch ESIEligibility On Specified Frml Vch ESIContribution Vch Pay Function First EPF12Pay Head Abs Vch Val Function First EPF833Pay Head Abs Vch Val Function | TDL_Reference_Manual.pdf |
What's New in Release 2. 0 53 1 Is Excise RG23DNo Exists Func Is Special AEDOf CVDExists In Stk Item Set TDSPymt Details Voucher Fill Order Obj Exists Tracking Obj Exists Fill Using Voucher Copy Batch Allocations Values STCat Check STCat Rate STCat Cess Rate STCat Secondary Cess Rate STCat Abatment No STCat Abat Per STCat Check | TDL_Reference_Manual.pdf |
TDL_Reference_Manual.pdf |
|
533 What's New in Release 1. 8 1. Invoking Actions on Event Occurrence-with System and Printing Events Introduced In any language, event handling is one of the powerful features, as it allows the developer to perform some operation based on some implicit action. In order to detect the events and to perform some action based on the event, a proper Event Framewor k is required. Prior to this release, the Events Form Accept and Focus had been introduced. In this release, there has been a major enhancement in Event Framework as a whol e. We will see in detail the events supported in TDL. Let's start with an overview of Event Framework and types of events. 1. 1 Event Frame work Overview When the user does something, an event takes place. Events are actions which are detected by a program and can change the state of system or execution flow. Events can occur based on user actions, or can be system-generated. In TDL, the Key Framework is mainly used to handle user actions like keyboard and mouse events. This can be considered as a part of Event Framework. We know that TDL is a definition language which does not have a ny explicit control on the flow of execution. The programmer has no control over what will happen when a particular event occurs. There are certain attributes like SET/PRINTSET, used to initiate some action on occurrence of event/change of state (like report construction, etc. ). In this scenario, there is a need of a generic Event Framework, which allows the programmer to trap the events and initiate an action/set of actions in the state when the event has occurred. The event framework allows the specification of an Event Handle r, where it is possible to specify an Event Keyword, a Condition to control event handling and the Action to be performed. The process of detecting an event and executing the specified actio n is called as Event handling. 1. 2 T ypes of Events When the user operates the application, different types of even ts are generated. The events are classified as System Events or Object-Specific Events, based on their origin. System events are for which no object context is available, when they occur. Example: T ally application launch. Object Specific events are performed only if the specific object context is available. Example: Form Accept is a Form-specific event. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 534 System Events In TDL, a new type ' Events ' has been introduced in the System definition. All the system events are defined under this definition. As of now, TDL event framework supports the following four system events, viz. System Start, System End, Load Company and Close Company. Syntax [System : Events] Label : <Event Keyword> : <Condition Expr> : <Action Keyword> : + <Action Parameters> Where, <Label> is a name assigned to the event handler. It has to be unique for each event handler. <Event Keyword> can be one of System Start, System End, Load Company or Close C ompany. <Condition Expr> should return a logical value. <Action Keyword> can be any one of the actions. <Action Parameters> are parameters of the action specified. The events System Start and System End are executed when the user launches or quits T ally application, respectively. The events Load Company and Close Company are executed when the user loads or closes a company, respectively. Example: [System : Events] App Start1 : System Start : TRUE : CALL : My App Start The function My Appstart is called as soon as the T ally application is launched. Object Specific Events Objects specific events can be specified for the associated obj ect only. Example: Before Print event is specific to 'Report' object. The attribute ON is used to specify the object specific events as follows: Syntax ON : Event Keyword : <Condition Expr> : <Action Keyword> : <Action Parameters> Where, <Event Keyword> can be any one of 'Focus', 'Form Accept', 'Before Print' and 'A fter Print'. <Condition Expr> should return a logical value. <Action Keyword> can be any one of the actions. <Action Parameters> are parameters of the action specified. ON is a list type attribute, so a list of actions can be executed when the specific event occurs. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 53 5 Event-FORM ACCEPT The event Form Accept is specific to 'Form' object; hence, can be specified only with in Form definition. A list of actions can be executed when the form is accepted, which can also be based on some condition. After executing the action Form Accept, the current object context is retained. So all the actions that are executed further, will have the same object context. The event 'Form Accept', when specified by the user, overrides the default action Form Accept. So, when 'Form Accept' event is triggered, the Form will not be accepted until the user explicitly calls the action 'Form Accept'. Example: [Form : Test Form] On : Form Accept : Yes : Http Post : @@SCURL : ASCII : SCPost New Issue : + SC New Issue Resp Action Http Post is executed when the event 'Form Accept' is encountered. But, t he form will not be accepted until the user explicitly calls the action Form Acc ept on event Form Accept as follows: On : Form Accept : Yes : Form Accept Now, after executing the action Http Post, T ally will execute the a ction Form Accept as well. Event-FOCUS The event Focus can be specified within the definitions Part, Line and Field. W hen Part, Line or Field receives focus, a list of actions get executed, which can also be conditionally controlled. Example: [Part : Test Part2] On : FOCUS : Yes : CALL: SCSet Variables : $$Line Event-BEFORE PRINT The event Before Print is specific to 'Report' object; so it can be specified only wit hin 'Report' definition. The event 'Before Print' is triggered when the user executes the 'Print' action. The action associated with the event is executed first, and then the report is printed. A list of actions can be executed before printing the report, b ased on some condition. Example: [Report : Test Report] On : BEFORE PRINT : Yes : CALL : Before Rep Print The function Before Rep Print is executed first and then the report T est Report is printed. Event-AFTER PRINT The event After Print can be specified for Report, Form, Part and Line definitions. I t first prints the current interface object and then executes the specified action s for this event. A list of actions can be executed after printing the report based on some condition. Print is an alias for After Print. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 536 Example: [Line : LV Acc Title] On : After Print : Yes : CALL : Set Index LV : #Ledger Name The function Set Index LV is called after printing the line LV Acc Title. So, if there are 10 lines to be printed, the function will be called ten times. 2. Collection Enhancements 2. 1 Using External Plug-Ins as a Data Source for Collections Introduction A Dynamic Link Library takes the idea of an ordinary library on e step further. The idea with a static library is for a set of functions to be collected together, so that a number of different programs could use them. This means that the programmers only have to wr ite code to do a particular task once, and then, they can use the same function in lots of other programs that do similar things. A Dynamic Link Library is simila r to a program, but instead of being run by the user to do one thing, it has a lot of functions “exported”, so that other prog rams can call them. There are several advantages of this. First, since there is only one copy of the DLL on any computer used by all the applications that need the library code, each application can b e smaller, thus saving disk space. Also, if there is a bug in the DLL, a new DLL can be created an d the bug will be fixed in all the programs that use the DLL just by replacing the old DLL file. DLLs can also be loaded dynamically by the program itself, allowing the program to install extra fu nctions without being recompiled. What is DLL? A Dynamic Link Library (DLL) is a library that can be called from any other executable code, i. e., either from an application or from another DLL. It can be shared by several applications running under Windows. A DLL can contain any number of routines and var iables. Dynamic Link Library has the following advantages: Saves memory and reduces swapping : Many processes can use a single DLL simultaneously, sharing a single copy of the DLL in memory. In contrast, Windows must load a copy of the library code into memory for each application that is built with a static link library. Saves disk space : Many applications can share a single copy of the DLL on disk. I n contrast, each application built with a static link library has the library code linked into its executable image as a separate copy. Upgrades to the DLL are easier : When the functions in a DLL change, the applications that use them do not need to be recompiled or re-linked, as lon g as the function arguments and return values do not change. In contrast, statically linked object code requires that the application be relinked when the functions change. A potential disadvantage of using DLLs is that the application is not self-contained; it depends on the existence of a separate DLL module. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 53 7 Differences between Applications and DLLs Even though DLLs and applications are both executable program m odules, they differ in several ways. T o the end user, the most obvious difference is that DLLs are not programs that can be directly executed. From the system's point of view, there are two fundamental differences between applications and DLLs: An application can have multiple instances of itself running in the system simultaneously, whereas a DLL can have only one instance. An application can own things such as a Stack, Global memory, File handles, and a message queue, but a DLL cannot. Types of DLL When a DLL is loaded in an application, there are two methods o f linking, i. e., Load-time Dynamic Linking and Run-time Dynamic Linking. Static Linking happens du ring program development time, whereas dynamic linking happens at run time. Load time Dynamic Linking /Static Linking In Load-time Dynamic Linking, an application makes explicit cal ls to exported DLL functions like local functions. T o use load-time dynamic linking, a header(. h) file and an import library (. lib) file are provided, while compiling and linking the application. Thus, the linker will provide the system with information required to load the DLL and resolve the expor ted DLL function locations at load time. Run-time Dynamic Linking /Dynamic Linking Dynamic linking implies the process that Windows uses to link a function call of one module to the actual function in DLL. In Run-time Dynamic Linking, an application calls either the function Load Library or the function Load Library Ex to load the DLL at run time. After the DLL is successfully loaded, the function Get Proc Address can be used to obtain the address of the exported DLL function that has to be called. In case of run-time dynamic linking, an import library file is not required. Please note that T ally does not support Static Linking; only Dynamic Link ing is possib le. DLL Approach in T ally As discussed before, Dynamic Link Library (DLL) is a file that can contain many functions. We can compare it with the library functions provided with many pr ogramming languages like C, C++. In T ally, there is provision to access the external functions by uploadi ng the DLLs. In general, the DLLs can be generated using VC++, VB,. Net framework, etc., and can be invoked from TDL. Hence, using TDL, the functions of DLL can be invoked to perform the necessary o perations. Why it is required in Tally?In T ally, all functions are not required for all the customers. Only gen eralized features are included to keep the functionality of T ally simple. But, for some custom ers, basic T ally may not cater the need. For that, we may need to extend the functionality of T all y by writing programs in TDL. TDL is designed to handle the functions in-built in T ally. For the functions that are not available in T ally, we use DLL, wherein we can include many functions and use it in T ally by calling those functions. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 538 How to use DLL in Tally? Loading the DLL's1. Copy the DLL file to T ally folder, say C:\T ally. ERP9. DLL points to the external functions that are to be loaded duri ng startup of T ally application. T ally loads DLLs from the source to the memory, and DLL functions are available with T ally for usage. OR 2. Register the DLL file using setup program or Command prompt. In TDL, DLL can be invoked by using Call DLLFunction and DLL Collection. Function-$$Call DLLFunction The internal Function $$Call DLLFunction can be used to call an external DLL containing multiple Functions Example:If a DLL “ Te s t D l l ” contains two functions Func A and Func B, where Func A takes one parameter of 'String' Data Type and returns a S tring Func B takes a parameter of 'String' Data Type and Executes the Function. It only returns the status of the function execution (boolean value) The syntax of invoking the DLL from TDL will be as follows: Syntax [Field : <Field Name>] Set As : $$Call Dll Function : <Dll Name>:<Function Name> : + <Param 1> : <Param 2>.... Where, <DLLName> is the name of the DLL. <Function Name> is the name of the Function. <Param1> and <Param2>.... are the Parameters for the function. The value returned from the function will be available in the f ield. T o call Func A [Field : Field2] Use : Name Field ;; Assuming Field1 is of Type 'String'The Call DLLFunction is a platform function which was already available earlier, and is NOT a part of Collection Enhancements. It has been discussed here just as an additional information. DLL Collection is an enhancement in this Release, which has been emphasized in the subsequent sections. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 53 9 Set As : $$Call Dll Function : Test Dll : Func A : #Field1 T o call Func B [Key : Key1] Key : Ctrl+A Action : Set : Var Status : $$Call Dll Function : Test Dll : Func B : #Field1 This key can be associated to a Form or a Menu. The function Func B in T est Dll can be used to return the status of the execution, i. e., Success/Failure (1/0). This value can be obtained in a variable in TDL and used to display the appropriate message to the user. $$Call Dll Function can be used to call any function which returns single values. I f the function returns an array of values, then it is advisable to use $$DLLCollection. Let us have an overview of the usage of DLL Collection. DLL Collection, its Attributes and Usage T ally now provides a TDL interface to obtain data sets in Colle ction from external Plug-Ins. These Plug-Ins are written as DLL's which can be used to fetch extern al data (i. e., from Internet, external Database, etc. ). These DLL's should return a valid XML which ca n be easily mapped into TDL Collection. In other words, TDL developer can provide a simple string value and/or XML to the DLL function. The DLL gives XML data as an output. Collection t akes this data and converts it into objects and object methods, which can be accessed in TDL like o ther objects. DLL collection will be very useful in the following scenarios:1. T o display stock quotes from the internet 2. T o get data from different formats like CSV, HTML 3. External device interfaces 4. RFID Barcode scanner5. Petrol Pump device interface 6. Foot fall count 7. External application interfaces8. GAS distributor application 9. T o get attendance details in Pay Roll through swipe In DLL collection, support is being provided for Plug-Ins and A ctive X-Plug-Ins. Plug-Ins : DLLs created using C++ or VC++. These DLLs need not be regist ered separately. Active X Plug-Ins : DLLs created by using VB6, VB. Net, C#. Net, etc. These DLLs ha ve to be registered. Registration process has been explained in detai l later. At present, the 'Collection' definition allows working with a C ++ DLL, VB DLL,. Net DLL, e t c., which has a function defined by the name TDLCollection (The function has to be created by this name ONL Y). This function delivers an XML which is available as objects in the Collection. Attributes of DLL Collection The attributes of DLL Collection can be categorized as follows: For specifying the source | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 540 Data Source For sending inputs to DLL Input Parameter Input XML For validating/formatting the data received from DLL Break On XSL T For selective conversion of XML XML Object XML Object Path Attribute-Data Source The attribute Data Source is used to set the source of the collection. By using this attribute, the actual DLL is invoked to TDL for further process. Syntax [Collection : <Collection Name>] Data Source : <Type> : <Identity> [:< Encoding>] Where, <T ype> specifies the type of data source, i. e., File XML, HTTP XML, Re port, Parent Report, V ariable, Plug In XML, Ax Plug In XML. <Identity> can be file path / source of DLL. <Encoding> can be ASCII or UNICODE. It's applicable only for File XML and HTTP XML. a. For Plug-in DLL Syntax Data Source : Plug In XML : <Path to dll> Where,<T ype> is 'Plug In XML'. <Identity> identifies the source of DLL, i. e., the path of DLL. Example: Data Source : Plug In XML : mydll. dll b. For Active X DLL Syntax Data Source : Ax Plugin XML : < Project Name>. <Class Name> Where,<T ype> is “Ax Plugin XML”. <Identity> identifies the source of DLL, i. e., < Project Name>. <Class Name> | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 54 1 Example: Data Source : Ax Plugin XML : DLLEg1. My Class For C#. Net, which has concept of namespaces, the source identifier is “Nam espace. Class Name” Syntax Datasource : Ax Plugin XML : <namespace>. <classname> Example: Datasource : Ax Plugin XML : testcsharpdll. Class1 Attribute- Input Parameter The attribute Input Parameter is used to pass a single stri ng value to the DLL function. Syntax Input Parameter : <Expression> Where, <Expression> returns a string value, which is used to pass to the DLL functi on. Example: Input Parameter : Test string In this example, 'T est String' is the string value, which is used to pass to the specified DLL. Attribute- Input XML The attribute Input XML is used to pass the XML format data to the DLL function. Syntax Input XML : <Post Request Report Name>, <Pre-Request Report Name> Where, <Post Request Report Name> is the name of the TDL report. It is responsible for generating XML data, which is passed to the DLL function as input. <Pre-Request Report Name> is optional. It is used to get any input from the end user. Example: Input XML : DLLRequest Report Attribute- Break On The attribute Break On is used to validate the XML data received from the DLL function. If the XML data contains the string specified in this attribute which is referred as error string, then the validation fails and the collection will not be constructed. Syntax Break On : <String Expression1>, <String Expression 2>..... Where, <String Expression 1>, <String Expression 2>... gives the string values which act as error string to validate the XML data. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 542 Example: Break On : My Error String If XML data received from DLL function contains “My Error Strin g”, then the collection will not be constructed, just as in XML collection. Attribute- XSLT The attribute XSL T is used to transform the XML document received from DLL functio n to another XML document. It will be applied before constructing the collection. This at tribute is same like in XML collection. Syntax XSLT : <XSLT File name> Where, <XSL T File name> is the name of the XSL T file name. Example: XSLT : "C:\ \Myfile. xslt" Attribute-XML Object The attribute XML Object is used to represent the structure of DLL collection object to which the obtained data is mapped. It is an optional attribute, and is sa me like in XML collection. Syntax XML Object : <Object Name> Attribute-XML Object Path The attribute XML Object Path is used to set the starting XML node from where the object construction starts. If only a specific data fragment is requir ed, it can be obtained using the collection attribute 'XML Object Path'. This attribute is same like in XML collection. Syntax XML Object Path : <Start Node> : <Start Node Position> : <Path to start node> Where, <Start Node> gives the name of the starting XML Node. <Start Node Position> gives the position of the starting XML Node. <Path to Start Node> gives the path of the starting XML Node. <Path to start node> can be extended as follows: <root node> : <child node> : <start position> : <child node> : <start position>:.... Example: XML Object Path : My Node : 1 : Root | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 54 3 Usage of DLL Collection attributes The following examples demonstrate the usage of DLL collection attributes: Example: Data Source-Ax Plug In Xml XML data received from the Active XDLL “testdll. class1” is to be displayed in a Report. For this, a DLL XML collection is constructe d and only a fragment of XML da ta is to be populated in the collection. Consider the following input XML fragment: <Emp Collection> <Emp> <Name>Emp1</Name> <Emp Id>101</Emp Id><Designation>Manager </Designation > </Emp> <Emp> <Name>Emp2</Name> <Emp Id>102</Emp Id> <Designation >Senior Manager </Designation> </Emp> </Emp Collection> The TDL code snippet for generating the report is as follows: [Part : DLL Coll Part] Lines : DLL Coll Line1, DLL Coll Line2 Repeat : DLL Coll Line2 : My DLL Collection i. In DLL collection, all the attributes except Datasource are optional. ii. All error messages related to DLL collection are stored in dllcollection. log file. The same XML has been used to explain all further examples. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 544 Scroll : Vertical [Line : DLL Coll Line1] Fields : DLL Coll Field1 [Field : DLL Coll Field1] Set As : “Retrive fragment EMP List from XML data” [Line : DLL Coll Line2] Fields : SL No, Emp Name, Emp ID, Emp Desig [Field : SL No] Use : Name Field Set As : $$Line [Field : Emp Name] Use : Name Field Set As : $Name [Field : Emp ID] Use : Name Field Set As : $Emp Id [Field : Emp Desig] Use : Name Field Set As : $Designation [Collection : My DLL Collection] Datasource : Ax Plugin XML : testdll. class1 XML Object Path : Emp : 1 : Emp Collection In this example, the attribute Datasource is used to set the source of DLL, i. e., the class name from the DLL “ testdll. class1 ”. The attribute XMLObject Path retrieves the XML fragment starting from the first <EMP> tag under the XML tag <Emp Collection> from the specified DLL. The XML data thus fetched from the DLL is then displayed in a Report. H e r e, Emp is the name of the starting XML Node, 1 is the position of the starting XML Node and Emp Collection is the path of the starting XML node | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 54 5 Example: Data Source-Plug In XML In the previous example, Active X Plugin DLL was used. Now, instead of 'Active X Plugin' DLL, the data source is simple Plug In DLL. The source keyword Plugin XML is used in the attribute Data source. In this case, only the DLL name must be specified. The collection definition is as follows: [Collection : My DLL Collection] Datasource : Plugin XML : testdll. dll XML Object Path : Emp : 1 : Emp Collection Example: Attribute-Input XML There are scenarios where the DLL expects some input as in XML fragment before sending the required XML output. The DLL XML collection attribute Input XML allows sending the Input XML to the source DLL in XML format. As explained earlier, the attribute Input XML accepts two parameters, i. e., Post Req Report and Pre Req Report. The collection is defined as follows: [Collection : Input XMLCollection] Data Source : Ax Plugin XML : Test DLL. Class1 XML Object Path : Emp : 1 : Emp Collection Input XML : Post Req Rep, Pre Req Rep In this example, the report 'Pre Req Rep' accepts the user input and the report 'Post Req Rep' generates the input XML, which is sent to the DLL. The response received from the DLL is populated in the collection Input XMLCollection. The reports 'Post Req Rep' and 'Pre Req Rep' are defined as follows : [Report : Post Req Rep] Form : Post Req Report In this case, DLL has to be registered. The registration process is explained in detail in the section “ Implementation and Deployment of DLL ”. The only difference from the previous example is that, here the DLL registration is not required. What's just required is to Copy the DLL to T ally. ERP 9 folder and execute the program. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 546 Export : Yes [Form : Post Req Report].. [Line : Post Req Report] Fields : Short Name Field, Post Req Report Name, Name Field, + Post Req Rep ID, Simple Field, Post Req Rep Desig Local : Field : Short Name Field : Set As : “Name:” Local : Field : Name Field : Set As : “Emp ID:”Local : Field : Simple Field : Set As : “Designation:” [Field : Post Req Report Name] Set As : ##Pre Req Name Var XMLTag : “Name”.. ;; Pre Request Report accepting User Inputs [Report : Pre Req Rep] Form : Pre Req Report.. [Part : Pre Req Report] Lines : Pre Req Report Name, Pre Req Report ID, Pre Req Report Desig [Line : Pre Req Report Name] Fields : Short Name Field, Pre Req Report Name Local : Field : Short Name Field : Info : “Enter Employee Name:” [Field : Pre Req Report Name] Use : Name Field Set As : “Enter your Name” | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 54 7 Width : 50 Modifies : DLLPre Req Name Var.. [System : Variable] DLLPre Req Name Var : “” Example: Attribute-Input Parameter In scenarios where only one value is to be sent as an input to the source DLL, the attribute Input Parameter can be used as follows: [Collection : Inp Parameter Coll] Data Source : Ax Plugin XML : Test DLL. Class1 XML Object Path : result Input Parameter : ##Input Parameter Var The value of the variable Input Parameter Var is sent as an input to the DLL “ T est DLL. Class1 ”. The response received is available in the collection Inp Parameter Coll. Example: Attribute-Break On The following code snippet validates the XML received from the DLL " tesdll. class1 ". [Collection : DLL XML Get Coll Obj Path] Datasource : Ax Plugin XML : testdll. class1 XML Object Path : Emp : 1 : Emp Collection Breakon : Manager Break On attribute is used to check whether the error string “ Manager ” exists in the output xml. If the error string exists, the XML is considered as an invalid XM L and an empty collection is created. Otherwise, the XML is considered as valid and the coll ection is populated from the received XML fragment. Signature of function 'TDL Collection' in the DLL The DLL created using any programming language, when called from T ally, must contain a main function named as TDL Collection. The signature of this functio n is specific to each programming language. The detailed signature of the function TDL Collection in different languages is as follows: For VC++ DLLConsider the following example for VC++ DLL to generate an XML fragment for Employee details. This DLL accepts the input from the TDL, and returns an XML fil e as output from DLL. Using this XML fragment, it constructs a collection. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 548 extern “C” HRESULT declspec(dllexport) TDLCollection (const wchar_t * p Input Param, const wchar_t * p Input XML, wchar_t ** p XMLCollection, long * p Collection Size) { *p Collection Size = 1024;if ((*p XMLCollection = (wchar_t *) (Co Task Mem Alloc (*p Collection Size * sizeof(wchar_t))))== NULL) { return-1; } wcscpy (*p XMLCollection,L"<Emp Collection>\ <Emp> \ <Name>Emp1</Name> \ <Emp Id>1 01</Emp Id>\ <Designation>Manager</Designation>\ </Emp>\ <Emp> \ <Name>Emp2</Name> \ <Emp Id>1 02</Emp Id>\ < Designation >Senior Manager</Designation>\ </Emp>\ </Emp Collection>" \ ); In this example, there are different inputs given as parameters to the function TDLCollection. p Input Param : It is an input value to the DLL and is a string value of coll ection attribute “Input Parameter ”. The TDL passes an input parameter to the DLL. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 54 9 p Input XML : It is an input to DLL and XML data constructed using collecti on attribute " Input Xml" Output values from TDLCollection function: p XMLCollection : O/P buffer containing resultant data, based on which, collect ion is constructed. p Collection Size : Number of wide characters, including the terminating NULL cha racter. For VB 6 DLLConsider the following example for displaying the values in XML format using VB6. Here also, two parameters are being passed to the TDL Collection. Public Function TDLCollection(p Input Param As String, p Input XML As String) As String TDLCollection = “<Root> <Name>Amazing</Name> <Name>Brilliant</Name> </Root>” End Function In this example, two attributes are being given as parameters to the function TDLCollection. p Input Param : Simple string value to the function, as specified in 'Collect ion' definition, using the attribute “ Input Parameter ”. p Input XM : Input value in Xml format, as specified in the 'Collection' d efinition, using the attribute “ Input XML ”. The function must return an output String value in XML format. For C#. Net DLLConsider the following example for. Net DLL to convert the inpu t string's case to upper case. Here, TDLCollection is passed two parameters. public string TDLCollection (string p Input Param, string p Input Xml) { string resultxml;// to contain xml to be sent back to Tally if (!String. Is Null Or Empty(p Input Xml)) { resultxml = p Input Xml. To Upper(); } else{ | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 550 resultxml = null; } return resultxml; } In this example, XML data is being passed to the function TDLCollection. All the data present in various tags are converted to upper case. The Input XML will be as follows: <Root> <Name> <fname>fname 1</fname> <lname>lname 1</lname> </Name><Name> <fname>fname 2</fname> <lname>lname 2</lname> </Name> </Root> The output XML will be as follows: <Root> <Name> <fname>FNAME 1</fname> <lname>LNAME 1</lname> </Name><Name> <fname>FNAME 2</fname> <lname>LNAME 2</lname> </Name> </Root> Inputs to the TDLCollection function: | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 55 1 p Input Param : It is an input value to the DLL and is a string value of coll ection attribute “Input Parameter ”. The TDL passes an input parameter to the DLL. p Input XML : It is an input value to the DLL and the XML data constructed using collection attribute "Input Xml ". For VB. Net DLL In VB. Net, the signature for the function TDL Collection is as follows: Public Function TDLCollection (By Val p Input Param As String, By Val p Input XML As String) As String Inputs to the TDLCollection function: p Input Param : It is an input value to the DLL and is a string value of coll ection attribute “Input Parameter ”. The TDL passes an input parameter to the DLL. p Input XM : This is an input value to the DLL and the XML data constructe d using collection attribute “ Input Xml ”. Implementation and Deployment of DLL Once the DLL is ready for deployment, the following should be e nsured for implementation of the same: 1. The dependency for the particular DLL needs to be checked, based on the environment in which it is developed. The necessary environment needs to be in stalled for the same. 2. The DLL needs to be registered in the system where it is to b e deployed. This can be done in two ways: Registering the DLL manually. Running the setup program which is created for deployment. Dependencies with respect to DLLs created using various Environ ments Created using. NET framework: For DLLs created using VB. NET, C # . N E T, etc., we require Microsoft. Net Framework. For example, if the DLL is cr eated using Visual Studio 2005, then Microsoft. Net Framework 2. 0 or above should be installed on the system. Created using Visual Basic 6. 0: For DLLs created using VB 6, we require service pack 6 to be installed on the system. References. Net Framework can be downloaded and installed from the followi ng link: http:// download. mic rosoft. com/ downloa d/6/0/f/ 60fc5854-3cb8-4 892-b6 db-bd4f 42510f 28/dot net- fx35. exe Service Pack 6 for Visual Basic 6. 0 can be downloaded from the following links: http:// www. microso ft. com /downlo ads/details. as px?Family Id =9EF9BF70-DFE1-4 2A1-A4C8-39718C7E381D&displaylang=en Multi part-http://www. micr osoft. com/ downloa ds/details. aspx?familyi d=83BF08E6-012D-4DB2-8109-20C8D7D5C1FC&displ aylang=en | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 552 How to register DLLs? After downloading the necessary environment, the DLL needs to b e registered before it is used and called by the T ally program. As already discussed, there are two ways in which a DLL can be registered. Let's discuss the two ways of Registering a DLL ( Manual & Set Up ) one by one: Manual Registration For VB6 DLLs 1. Copy the DLL file to the specific folder say C:\T ally. ERP9 2. Open Command Prompt and change the current directory to the f older where DLL is copied, i. e., :\T ally. ERP9 3. Type the command Reg Svr32 <DLL Name> 4. After the command is entered in command prompt, a message box is displayed as shown: Figure 1. Registering DLL using command prompt Now you can use the DLL for calling from T ally. For. NET DLLs T o register. Net DLL, the Reg Asm command needs to be used, instead of Reg Svr32. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 55 3 Registering DLLs by using Setup Program T o register using this method, double click on the setup progra m and proceed with the installation. This automatically registers the required DLL into the selected folder. Creating a Set Up Program The creation of Set Up program varies from one language to anot her. Please refer to any learning material for Set Up creation specific to your Development Envir onment. As an example and common usage, we will just discuss creating Set Up using VB 6. The steps for deployment of VB6 DLLs using Package and Deploym ent Wizard are as follows: 1. Open the VB project where you want to create a setup program. 2. Select Package and Deployment wizard from Add-In menu. 3. If the option isn't there, choose Add-In Manager and double click Package and Deployment wizard. 4. Proceed with the Wizard options. For more details, please refer to the following links: htt p://ww w. configure-all. com/ deployment. php http://ww w. developerf usion. com/article/27/ packag e-deployment-wizard/2/ 2. 2 Dynamic T able Support-using 'Unique' Attribute The Unique attribute of 'Collection' definition is used to control the dis play of unique values in the table for a specified method, based on values selected from the table previously in a field. The display of values is changed dynamically based on the field val ue. Existing syntax The existing syntax of the attribute 'Unique' is: Syntax Unique : <Table Object Method> [,<Field Object Method>] Where, <T able Object Method> is a method whose value is uniquely displayed in the table. <Field Object Method> is the storage/method, which is associated with the field which is used to control the display of T able values dynamically. If a particular table object method value from the T able is selected in the field, then that value is removed from the table based on the value of <Field Object Method>. This parameter is optional. Example: [Part : Stk Bat] Repeat : Grp Led Ln : Stk Item Coll Manual registration does not automatically take care of missing dependencies. So, it is always advisable to use Se t Up Programs for Registration. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 554 [Line : Grp Led Nm] Field : Stk It, Stk Bat Nm [Field : Stk It] Use : Name Field Storage : Item Name [Field : Stk Bat Nm] Use : Name Field Table : Bat List Storage : Bt Name Show Table : Always Dynamic : Yes [Collection : Bat List] Title : “List of Batches” Type : Batch Format : $Batch Name,20 Child of : #Stk It Unique : $Batch Name, $Bt Name [Collection : Stk Item Coll] Type : Stock Item Fetch : Name [System : UDF] Bt Name : String : 2010 Item Name : String : 2010 The table “Bat List” is used to display batch names in a T able attached to the field “ Stk Bat Nm ”. The storage associated with the field is “ Bt Name ”. Once the Batch name is selected in the field “Stk Bat Nm”, in the next line, the table will be populated with batches which are not selecte d previously in the field. Even if some stock items belong to more than one batch, the tab le won't display the common batches, since it may have been already selected in the field f or a different stock item. T o provide this flexibility for controlling the uniqueness of data, the at tribute 'Unique' has been enhanced. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 55 5 New Enhanced Syntax The new enhanced syntax is: Syntax Unique : <Table Object Method> [,<Field Object Method> + [,<Extended method>]] Where, <T able Object Method> is a method whose value is uniquely displayed in the table. <Field Object Method> is the storage/method, which is associated with the field which is used to control the display of T able values dynamically. If a particular table object method value from the T able is selected in the field, then that value is removed from the table based on the value of <Field Object Method>. This parameter is mandatory if <Extended method> is specified, else it is optional. <Extended Method> is a storage/method, whose value specifies whether the previous value of the field object method should be used to control unique values display in the table. If the current value of the value of <Extended Method> is same as that of prev ious values, then <Field Object Method> value is considered while populating unique values in t he table. Otherwise, the <Field Object Method> value is ignored to set the unique values in the table. This parameter is optional. The collection and definition is modified as follows, so that w hile populating unique values of Batch names in the table, Stock Item name is also considered apart from the value of the field storage/method “Bt Name”, i. e., if the same stock item is selected in the field which has been selected previously, then the field storage/method value “Bt Name” is considered for controlling display of Batches, else it is ignored. Example: [Collection : Bat List] Title : “List of Batches” Type : Batch Format : $Batch Name,20 Child of : #Stk It Unique : $Batch Name, $Bt Name, $Item Name Here, the method $Itemname used in the 'Unique' attribute is the storage defined in the fi eld 'Stk It '. Use Case:Consider the following Scenario: Stock Item Batch Name Item 1 Batch A Batch B | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 556 There are two fields in the line, one of which displays stock i tem name and the other displays batches. The selected batch is stored in a UDF, say Bt Name. Following table displays the values in each field and unique va lues in tables based on selection: 2. 3 Using Variable as a Data Source for Collections Collection attribute Data Source has been enhanced to support 'V ariable' as a data source. Now, variable element(s) can be gather ed as objects in the collectio n and the respective simple member variables are available as methods. Member list variable s will be treated as sub-collections. Syntax Data Source : <Type> : <Identity> [:<Encoding>] Where, <T ype> is the type of data source, i. e., File XML, HTTP XML, Report, P arent Report, V ariable. <Identity> can be file path/scope key words/variable specification, based on type of data source. <Encoding> can be ASCII or UNICODE. It's applicable for the types File XML & HTTP XML. Batch C Item 2 Batch A Batch C Item 3 Batch A Batch BBatch C Line No Value in Field 1 Values in Table Selected Value in Fiel d 2 1I t e m 1 B a t c h A Batch B Batch C Primary Batch Batch A 2I t e m 2 B a t c h A Batch C Primary Batch Batch C 3I t e m 3 B a t c h B Batch C Primary Batch Batch B Please refer to the topic “Using Variable as a Data Source for Collections” under Variable Framework for more clarity, with examples. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 55 7 3. Evaluating expressions by Changing the Object Context with $$Req Owner Introduced In a programming language, an expression is a combination of va lues, variables, operators and functions that are evaluated according to the rules of their pr ecedence and association. Similarly, expressions in TDL can be a combination of Method/V ariable/Fiel d/Constant V alues, and Function/Formula evaluation results. Example: For TDL Expression $Name + ##Var Test + $$Machine Date + @@Form ABC + 90 + #Field XYZ Where, Name is a Method, Var T est is a V ariable, Machine Date is a Function, Form ABC is a System Formula, 90 is a constant value, and Field XYZ is a Field. Methods, V ariables and Fields are Leaf components in an expression as other components like Formulae or Functions finally evaluate into either one of these, or result into constants. A TDL Expression always gets evaluated in the context of an Int erface (Requestor) and Data Object. Whenever a report is constructed, an Interface object h ierarchy is created, i. e., Report contains a Form, Form contains a Part, and so on. Every Interfa ce Object is associated with a Data Object. In the absence of explicit data object association, an implicit anonymous object gets associated. A method value is evaluated in context of the data object, while V ariable and Field values are evaluated in context of Interface object. There may be cases where we would require evaluating these in a context different from the implicit conte xt (Interface and Data). TDL provides many functions which provide the facility to change the Data or Interface Object Context. A change in Data Object context does not change the current Inter face (Requestor) Object context and a change in Interface Object Context does not change the cu rrent Data Object Context. We can categorize these functions into mainly two categories: Data Object Context Switching Functions Interface Object Context Switching Functions 3. 1 Data Object Context Switching Functions The T ally database is hierarchical in nature, in which the obje cts are stored in a tree-like structure. Each node in the tree can be a tree in itself. An object in T al ly is composed of methods and collections. Method is used to retrieve data from the database. A collection is a group of objects. Each object in the collection can further have methods and collectio ns. The Internal Object hierarchy is predefined in T ally and cannot be altered. These can only be pe rsisted in T ally Database. Every Interface Object exists in the context of a Data Object w hich is associated to it. As discussed above, an expression (specifically method value) gets evaluated in context of the Data | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 558 Object associated with the Requestor (Interface Object). By usi ng the functions as given ahead, we can change the Data Object Context for expression evaluation. In all the subsequent examples, we will be using the 'Voucher' Data Object hierarchy to demonstrate the various scenarios for Context Change. Hierarchy of the 'Voucher' Object is as shown in the following figure. Figure 2. Data Object Hierarchy of V oucher Function-$$Owner The function $$Owner evaluates the given expression in the context of the parent dat a object in the Data Object hierarchy chain, i. e., it will change the Data Object context to the parent of the current Data Object in context. For example, if the current obj ect context is Batch Allocations, then to access the value from Inventory Entries, which is its parent data object, the $$Owner function can be used. Syntax $$Owner : <Expression> Example: 1 In this example, let us assume that the “Bill Allocations Amoun t” field (Requestor) exists in context of Bill Allocations Data Object. In order to evaluate the method “ Amount ” from Ledger Entries Object Context, we need to use the function $$Owner. [Field : Bill Allocations Amount] Switching the Data Object Context does no t imply a change in the current Requestor (Interface Object) | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 55 9 Set As : $$Owner : $Amount In this field, method Amount from parent object Ledger Entries is set by using $$Owner function. Example: 2Similarly, let's assume that the current data object context fo r the field “ Bill Allocations Remarks ” is Bill Allocations, and we need to evaluate the method Narration from V oucher Object. [Field : Bill Allocations Remarks] Set As : $$Owner : $$Owner : $Narration In this field, Narration from object V oucher, which is 2 levels above in hierarchy, is set using $$Owner twice. In other words, we are requesting for method Narration from the owner of owner. Alternatively, in these examples, we can use the dotted method formula syntax. [Field : Bill Allocations Amount] Set As : $..Amount [Field : Bill Allocations Remarks] Set As : $... Narration In these examples,.. denotes the parent and... denotes the Grand Parent. Function-$$Base Owner Function $$Base Owner evaluates the given expression in the context of the base/prima ry data object in the Data Object hierarchy chain available with the 'R eport' Object (in memory). For example, if the current data object context is Batch Allocations, then to access the method value from V oucher, $$Base Owner function can be used. Syntax $$Base Owner : <Expression> Example: As per the V oucher hierarchy, let's assume that our current data object context for the fiel d “Bill Allocations Remarks ” is Bill Allocations. In order to access the value of Method Narration from Voucher Object, which is the base/primary object in the object hierarchy chain, we can use the function $$Base Owner. [Field : Bill Allocations Remarks] Set As : $$Base Owner : $Narration Since the entire Data Object hierarchy is cached with the Object associated at the Report, the function $$Base Owner changes th e Data Object context to the Object associated at the Report. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 560 In this field, the Method Narration from the base Object V oucher is set, using $$Base Owner. Alternatively, in the above example, we can use the dotted method syntax. [Field : Bill Allocations Remarks] Set As : $(). Narration In this example, (). navigates to the Primary/Base Data Object Function-$$Prev Obj Function $$Prev Obj evaluates the given expression in the context of the previous d ata object of the collection, which contains the current data object in conte xt. Syntax $$Prev Obj : <Expression> Example: Assume that a line is being repeated over a collection of Outst anding Bills, which is sorted based on Party Name. After every Party Info, a T otal Line is needed to print subtotal for current Party. [Line : Outstanding Bills] Option : Partywise Totals : $$Prev Obj : $Party Name! = $Party Name [!Line : Partywise Totals] Add : Lines : At Beginning : Party Sub Total Line In this example, an optional line will be included only if the method Party Name of the previous object is not equal to that of the current object. Function-$$Next Obj Function $$Next Obj evaluates the given expression in the context of the next data object of the collection, which contains the current data object in context. Syntax $$Next Obj : <Expression> Example: Assume that a line is being repeated over a collection of Outst anding Bills, which is sorted based on Party Name. After every party Info, a T otal Line is needed to print the subtotal for current Party. [Line : Outstanding Bills] Explode : Partywise Totals : $$Next Obj : $Party Name! = $Party Name In this example, a part is exploded, provided the method Party Name of the next object is different from that of the current object. This will enable explosion for each party only once, and thereby, we can easily achieve the subtotal line as desired. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 56 1 Function-$$First Obj Function $$First Obj evaluates the given expression in the context of the first data object of the collection, which contains the current data object in context. Syntax $$First Obj : <Expression> Example: Assume that a line is being repeated over the ledger collection, where in a field, we require the first object's name to be set. [Field : First Name] Set As : $$First Obj : $Name In this example, a Field First Name is set as the Name Method of the first object in the Collection. Function-$$Last Obj Function $$Last Obj evaluates the given expression in the context of the last data object of the collection, which contains the current data object in context. Syntax $$Last Obj : <Expression> Example: Assume that a line is being repeated over the ledger collection, where in a field, we require the last object's name to be set. [Field : Last Name] Set As : $$Last Obj : $Name In this example, a Field Last Name is set as Name Method of the last object in the Collection. Function-$$Tgt Object As we already know, apart from Interface (Requestor) and current Data Object Conte xt, there is one more context available with reference to User Defined Funct ions and Aggregate Collections, i. e, the T arget Object Context. In case of functions, the object be ing manipulated is the T arget Object. In case of aggregate Collection, the object being popul ated in the resultant collection is the T arget Object. There are scenarios where the expression needs to be evaluated in the context of the T arget object. In such cases, the function $$Tgt Object can be used. Using $$Tgt Object, values can be fetched from the target object without setting the target objec t as the current context object. Syntax $$TGTObject : <Expression> Example: 1 Consider writing a Function to import a Voucher from Excel, whe rein the Source Object is the Collection gathered out of Objects in an Excel Worksheet, the T arget Object being the Voucher and its sub objects. While setting v alue to Inventory Entries sub-o bject, the T arget Object is | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 562 changed to Inventory Entries and the Source Object continues to be Excel Objects. In order to set values to the methods Quantity and Rate, Stock Item context is required since Unit Information is available for Item. Hence, $$TGTObject Function is prefixed to the Expression @Bill Qty and @Bill Rate, in order to evaluate these Methods in the context of the T arge t Object, which is the 'Inventory Entries' Object. [Function : Import Voucher] Local Formula : Bill Qty : $$As Qty : $Excel Billed Qty Local Formula : Bill Rate : $$As Rate : $Excel Item Rate90 : INSERT COLLECTION OBJECT : Inventory Entries 100 : SET VALUE : Billed Qty : $$Tgt Object : @Bill Qty 110 : SET VALUE : Rate : $$Tgt Object : @Bill Rate 120 : SET TARGET.. 130 : SAVE TARGET Example:2 Consider another example where, while populating a summary coll ection of Sales Vouchers, we need to track the maximum sales amount for each Item with the d ate on which the maximum sales was triggered. [Collection : Src Voucher] Type : Vouchers : Voucher Type Child Of : $$Vch Type Sales [Collection : Summ Voucher] Source Collection : Src Voucher Walk : Inventory Entries By : Item Name : $Stock Item Name ;; The following returns the Date and Amount for an Item, on which Maximum sales has happened Aggr Compute : Max Date : SUM : IF$$Is Empty : $$Tgt Object : $Max Item Amt + OR $$Tgt Object : $Max Item Amt <$Amount THEN $Date ELSE + $$Tgt Object : $Max Date ;; Max Item Amt is a method in the T arget Object. Henc e, the function $$Tgt Object is used to evaluate the Method ;; Max Item Amt in T arget Object Context Aggr Compute : Max Item Amt : MAX : $Amount | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 56 3 In this example, while populating the Summary Collection, Metho d Max Item Amt is being computed for Maximum Amount. Subsequently, Date is also computed by validating if the current object's Amount is greater than the previous computed Amount. Since Maximum Amount so far is computed and accumulated in the T arget Object being populated, we need to access it using the function $$TGTObject. Hence, $$Tgt Object:$Max Item Amt evaluates the Method Max Item Amt in the context of the computed T arget Object Max Item Amt. Function-$$Loop Coll Obj As we are aware, it is now possible to gather Data Collection in context of eac h object of another collection, which is referred to as a Loop Collection. T o acces s the methods of Loop Collection Objects from within the Data Collection, $$Loop Coll Obj is used, with which the expression is evaluated in the context of the Loop Collection Objects. Syntax $$Loop Coll Obj : <Expression> Example: T o see a consolidated list of vouchers across all the loaded co mpanies. [Collection : Company Collection] Type : Company Fetch : Name [Collection : Vouchers of Multiple Companies] Collection : Multi Cmp DB Vch Collection : Company Collection Sort : Default : $Date, $Ledger Name [Collection : Multi Cmp DB Vch Collection] Type : Voucher Fetch : Date, Vouchernumber, Voucher Type Name, Amount, Master ID, + Ledger Name Compute : Owner Company : $$Loop Coll Obj : $Name In this example, the function $$Loop Coll Obj changes the context to Loop Collection Objects, which is the Company Collection and hence, returns the company name. Function-$$Report Object The function $$Report Object evaluates the given expression in the context of the Data Objec t associated with the Report Interface Object. One of the important Use Cases of $$Report Object is its usage in purview of in-memory Collection gathering. Whenever a collection is gathered, it is retained in memory wi th the Data Object of the current Interface (Requestor) Object. If the same collectio n is being used in expressions again and again, then it is beneficial from the performance point of view to at tach it to | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 564 the 'Report' Object and evaluate it in the context of 'Report' Object n number of t imes. This eliminates the need to re-gather the collection every time in context of other Data Objec ts. Syntax $$Report Object : <Expression> Example: 1 From Bill Allocations Data Object context, Voucher No. of Report Object V oucher is required. [Field : Bill No] Set As : $$Report Object : $Voucher Number Example: 2 In a Report, Sales of each Item against the corresponding Parti es is required. [Collection : CFBK Voucher] Type : Voucher Filter : Is Sales VT [Collection : CFBK Summ Voucher] Source Collection : CFBK Voucher Walk : Inventory Entries By : PName : $Party Ledger Name By : IName : $Stock Item Name Aggr Compute : Billed Qty : SUM : $Billed Qty Search Key : $PName + $IName [Field : CFBK Rep Party] Use : Qty Primary Field Set as : $$Report Object : $$Collection Field By Key : $Billed Qty : + @My Formula : CFBKSumm Voucher My Formula : ##PName + #CFBKRep Name Here, the function $$Report Object, during its first execution, retains the collection within the Voucher Object (which is the Data Object associated with the 'R eport' Object). During subsequent calls, method values are fetched from the Objects available in the 'Report' Data Object, instead the entire Collection being regathered again. This helps in imp roving the performance drastically. Function-$$Req Object This function evaluates the given expression in context of the Data Object associated with the Interface (Requestor) Object. There may be scenarios where duri ng expression evaluation, Data | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 56 5 Object context changes automatically and all the methods referr ed to are evaluated in context of the changed Data Object. The Data Object associated with the In terface (Requestor) Object is lost. Specifically in those cases, where we need to evaluate me thods in context of the data object associated with the Interface (Requestor) Object, we will use t he function $$Req Object. Syntax $$Req Object : <Expression> Example: A Report is required to display Ledgerwise Sales T otals [Field : Fld Led Sales Total] Set As : $Ledger Sales Total [#Collection : Ledger] Compute : Ledger Sales Total : $$Filter Amt Total : Led Vouchrs : + My Party : $Amount [Collection : Led Vouchers] Type : Voucher Filter : Only Sales [System : Formula] My Party : $Party Ledger Name = $$Req Object : $Name Only Sales : $$Is Sales : $Voucher Type Name In this example, a new method Ledger Sales T otal is added in the Ledger Object to compute the Sales T otal from all the Vouchers filtered for the current Part y Ledger Object. The Interface Object (Requestor) for this method is the field “ Fld Led Sales T otal ”. In the Formula My Party, current Ledger Name must be checked with the Party Ledger Name of the V oucher Object, which is the current Data Object context. The Data Object associated with th e Requestor is Ledger Object. So, in order to evaluate the method $name from the Interface (Requestor) Object's Data Object context, the function $$Reqobject must be used. Function-$$Object Of As we are already aware, there is the capability to identify a Part and Line Interface Object using a unique Access Name. A Form/Report can be identified from any level using the Defin ition Type. The function $$Object Of is used to evaluate the expression in context of the Data Objec t associated with the Interface Object identified by the Access N ame. The Interface Object being referred to, should be assigned a unique Access Name via Access Name attribute. Syntax $$Object Of : <Definition Type> : <Access Name Formula> : <Evaluation Formula> | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 566 Example: [Part : Cust Object Association] Lines : Cust Object Association ;; Object associated at Part Object Ex : (Ledger, "Customer"). ;; Access Name specified so th at this part can be accessible Access Name : “Cust Ledger” ;; In some other fields across parts, we can access the methods of the Ledger Object associated with the part “Cust Object Associa-tion”, using the function $$Object Of [Field : Ledger Parent] Set as : $$Object Of : Part : "Cust Ledger" : $Parent The Part “ Cust Object Association ” is associated with the Ledger Object “ Customer ”. It is identified by the Access Name “ Cust Ledger ”. The Field Ledger Parent from a different Part accesses the method $Parent from the Ledger object 'Customer', as it is the Object associat ed with the part Cust Object Association, identified by Access Name “ Cust Ledger ”. Function-$$Table It evaluates the expression in the context of 'T able' object, which is selected in the give n Field. Syntax $$Table : <Field Name> : <expression> Example: [Field : Vehicle Number] Table : List of Vehicles Show Table : Always [Field : Vehicle Type] Set as : $$Table : Vehicle Number : $Veh Type [Field : Vehicle YOP] Set as : $$Table : Vehicle Number : $Veh YOP [Collection : List of Vehicles] Type : Veh Agg UDF : Company Child Of : ##SVCurrent Company Format : $Veh No, 20 Format : $Veh Type, 40 | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 56 7 Format : $Veh YOP, 4 Fetch : Veh No, Veh Type, Veh YOP ;; For Remote Client End In this code, the table is displayed in the field “Vehicle Numb er”. In the other fields 'Vehicle Type' and 'Vehicle YOP', $$T able is used to evaluate the methods $Veh Type and $Veh YOP in context of the Data Object selected in the field “Vehicle Number”. Function-$$Table Obj $$T able Obj is similar to the function $$T able. The expression is evaluated in context of the Data Object selected in the T able in the field specified. The differ ence of this function from the function $$T able is that, in case no object is selected in the T able, or expression evaluation fails, $$T able returns a blank string. In such a case, $$T able Obj returns a lo gical value (FALSE) as the result. Syntax $$Table Obj : <Field Name> : <expression> Example: A Field needs to be skipped based on the selection of the table in a field. [!Field : VBOrd Due DRNote] Skip : $$Table Obj : VCHBATCHOrder : $$Is Order In this example, if the Object selected in the Field Vch Batch Order is an Object Order, then the current field needs to be skipped. 3. 2 Interface Object Co ntext switching functions Objects used for designing the User Interface are referred to a s Interface objects. I n t e r f a c e objects like Report and Menu are independent items and can exis t on their own. The objects Form, Part, Line and Field can't exist independently. A Report can have more than one Form, Part, Line and Field definitions but at least one has to be the re. The hierarchy is as follows: Report uses a Form Form uses a Part Part uses a Line Line uses a Field A Field is where the contents are displayed or entered | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 568 Figure 3. Interface Object Hierarchy We can take an example of the Simple Customized Invoice Report (as given in the diagram) in order to understand the containment hierarchy of Interface Obje cts. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 56 9 A set of available attributes of interface objects have been pr edefined by the platform. A new attribute cannot be created for an interface object. Interface objects are always associated with a Data Object and essentially add, retrieve or manipulate the inf ormation in Data Objects. At run time, when a report is constructed after the evaluation of all of the above, a complete hierarchy of Interface Objects is created. As we have already d iscussed, an expression is evaluated in the context of the current Interface Object, which is referred to as the Requestor, and the Data Object associated to it. We will now discuss the swit ching functions which will change the Interface Object Context for expression evaluation. Function-$$As Req Obj The function $$As Req Obj is used to save the Interface (Requestor) context to the curren t object, for the evaluation of the expression. All the future references done using $$Req Object will point to the saved Interface Object context. The actual requestor is overridden using the function $$As Req Object. Syntax $$As Req Obj : <Expression> Example: Here, a T able of Company Vehicles is displayed in a Field “ Select Vehicle ”, which exists in the context of the V oucher Object. The table is filtered on the basis of Unused Vehicles. [Field : Select Vehicle] ;; In Voucher Entry Table : CMP Vehicles Storage : VCHVehicle [Collection : CMP Vehicles] Type : Company Vehicles : Company Childof : ##SVCurrent Company Format : $Vehicle Number, 20 Format : $VBrand, 10 Title : “Company Vehicles” Filter : Unused Veh [System : Formula] Unused Veh : $$As Req Obj : $$Filter Count : Prev Sales Vchs : + Used Vehicle = 0Switching the Interface (Requestor) Object Context does not imply a change in the current Data Object context. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 570 Used Vehicle : $$Req Object : $Vehicle Number = $VCHVehicle Only Sales : $$Is Sales : $Voucher Type Name [Collection : Prev Sales Vchs] Type : Voucher Filter : Only Sales In this example: Field Select Vehicle is the Interface (requestor) object, associated with the data o bject Voucher. T able/Collection of Company Vehicles is displayed in the Field. T able is filtered for Unused vehicles. This collection contains the list of Vehicle Numbers which need to be compared with the ones used in the previous sales vouchers. Since Requestor is th e Field with the data object 'Voucher', Function $$Req Object will get evaluated in the context of 'Voucher' Object, which is not expected. Hence to make the current collection, i. e., CMP Vehicles, a s requestor object for future reference, Function $$As Req Obj is used. In the Function $$Filter Count, when the object context changes to the list of sales vouchers, the Function $$Req Object evaluates the parameter $Vehicle Number in the context of the requestor Collection CMP Vehicles set earlier using $$As Req Obj, and compares the same with the Voucher UDF Vch Vehicle stored in the respective vouchers. Function-$$Req Owner The Function $$Req Owner evaluates the given expression in the context of the Interface (Requestor) object's Owner in the current Interface object hier archy. For instance, Report is an owner requestor for Form, Form is an owner requestor for Part, and so on. From the Line, when the function $$Req Owner is used, the expression gets evaluated in the context of the Pa rt containing the current line. Syntax $$Req Owner : <Expression> Example: [#Menu : Gateway of Tally] Add : Key Item : Req Owner Sample : W : Alter : ICCF Req Owner [Report : ICCF Req Owner] Form : ICCF Req Owner Variable : Var Req Owner : String : “Keshava” [Form : ICCF Req Owner] Parts : ICCF Req Owner | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 57 1 [Part : ICCF Req Owner] Lines : ICCF Req Owner [Line : ICCF Req Owner] Fields : ICCF Req Owner[Field : ICCF Req Owner] Set As : $$Functoreturn Req Owner Set Always : Yes [Function : Functoreturn Req Owner] Variable : Var Req Owner : String : “Madhava” Variable : Temp : String : $$Req Owner : ##Var Req Owner 01 : MSGBOX : ##Var Req Owner : ##Temp 10 : RETURN : $$Req Owner : ##Var Req Owner In this example, the V ariable Var Req Owner is declared & initialized in a Report as well as in a function. From the Field, the function $$Req Owner Func is referred to perform some computation and return the result. Since, $$Req Owner is used in the Function and Field is the Requestor Owner for Function, the Field walks back the Interface (Request or) Object hierarchy to fetch the V ariable value. Hence, the V ariable value Keshava of the nearest Interface Object, i. e., of the Report is returned. Function-$$Access Obj As we are already aware, there is the capability to identify a Part and Line Interface Object using a unique Access Name. The function $$Access Obj changes the Interface Object context to the one identified by the Access name to evaluate the expression The Interface Object being referred to should be assigned a uni que Access Name via Access Name attribute. Syntax $$Access Obj : <Definition Type> : <Access Name Formula> : <Evaluation Formula> Example: [Line : ABC] Access Name : “Acc ABC” [Field : XYZ] Set As : $$Access Obj : Line : “Acc ABC” : ##Var ABC In this example, the function $$Access Obj changes the Interface Object context from the field “XYZ” to the line “ ABC ”, which is identified by the Access Name “ Acc ABC ”. The variable value is evaluated in context of the line “ABC”. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 572 Function-$$Explode Owner The function $$Explode Owner changes the Interface (Requestor) Object to the Line owning the current exploded Part, and evaluates the given expression, i. e., Field and V ariable V alues, in the context of Interface Object. Syntax $$Explode Owner : <Expression> Example: [Line : Smp Inv Entries] Fields : Name Field Local : Field : Name Field : Set As : $Stock Item Name Explode : Smp Expl Part [Part : Smp Expl Part] Lines : Smp Batch Allocations Repeat : Smp Batch Allocations : Batch Allocations Scroll : Vertical [Line : Smp Batch Allocations] Fields : Name Field Local : Field : Name Field : Set As :$$Explode Owner : #Name Field In this example, the field Name Field is being evaluated in the context of the Line Smp Inv Entries, which owns the current exploded part Smp Expl Part. Function-$$Prev Line When the line is repeating, we may require evaluating an expression in the context of the previous line. For example, we might require to fetch the field values s tored in the previous line for an expression in the current line. The function $$Prev Line is used to change the Requestor to the Previous Line for expression evaluation. Syntax $$Prev Line : <Expression> The function $$Prev Line not only changes the Interface (Requestor) Object context, but also changes the Data Object cont ext to the Object associated with the Requestor. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 57 3 Example: [Line : Prev Particulars] Explode : Prev Particulars Exp Part : $$Prev Line : + #Party Particulars != #Party Particulars In this example, in case of repeated lines, where subtotals are required to be displayed or printed for the same party, we can explode a subtotal line after comparing the previous li ne's and the current line's Ledgers. If the field values are not the same, t hen the subtotal line is exploded. 4. Variable Framework with Compound Variables Introduced V ariables in TDL (T ally Definition Language) are entities which can hold values during the execution of a program. The values of these variables are initi alized when they are created and can change during the entire execution of program. The Program can change the variable value by specifying expressions which are evaluated to set the values of the variables. V ariables are context-free structures which do not require any specific object context for manipulation. They are declared by name and can be operated usi ng the same name. It is also possible to access and operate variables declared at the parent scope. V ariables are lightweight data structures, which are simple to operate and provide the capability of storing multiple values of the same type and different types as well. It is also possible to perform various manipulation operations like insert/update/delete/sort/ find. These are mainly used to perform complex computations. V ariable can hold a single value, or more than one value of sam e type or different types. It can be declared at various scopes such as Report, Function and System Level. 4. 1 Classification of Variables The various types of variables in TDL are: 1. Simple Variable Simple variables allow storage of a single value of the specifi ed data type. 2. Simple Repeat Variables The Simple V ariable can hold method values of multiple objects of a collection based on an implicit index. This concept is used in Columnar Reports only, where the lines should be repeated vertically and the fields should be repeated horizontally. 3. Compound Variable Compound V ariables allow us to store values of different data t ypes. This is achieved by making the variable itself compound, by allowing variable declaration inside itself. These sub variables are called member variables of the main variable. A member variable can be a single instance or a list variable. A member variable can be a compound variable and can have members again, and therefore any hierarchy can be created. Compound variables help grouping of related information togethe r into one specification. In another terms, we can think about compound variables as an 'obj ect'. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 574 Following table shows the similarities between an object and a compound variable: We can have a comparison between the internal Data Object 'V oucher ' and a Compound V ariable 'CL V Emp' to understand the similarities between an Object and Compound V ariable. For instance, the Compound V ariable 'CL V Emp' is defined as follows: [Variable : CLV Emp] Variable : Name : String Variable : Designation : String Variable : Age : Number Variable : Salary : Amount List Variable : Contact Nos : String List Variable : Relatives Variable : Contact Address ;; Defining Compound Variable [Variable : Relatives] Variable : Name : String Variable : Age : Number Variable : Relation : String Variable : Salary : Amount ;;Defining another compound variable [Variable : Contact Address] Variable : Street Name : String Variable : City Name : String Object Compound Variable Can have methods Can have Sim ple Variables as its members Can have repeated methods (simple collections) Can have a Simple List Variable as member Can have collections (compound collections) Can have Compound L ist Variable as its member *Cannot have objects under it directly* Can have Compound Varia bles as members | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 57 5 4. List Variable A variable at declaration time can be declared as a single inst ance or as a list. List variable is a container (data structure) variable and hence it is not defined. V ariables can be declared as list. List V ariable can hold one or more variables which can be eithe r a simple or a compound variable. Each of these is called Element V ariable. Element V ariable hold s value as well as key, if specified. The key is optional, and hence without a key also, elements can be added to list variables. The value of key specified for each of the element variables must b e unique. Simple List Variable Simple V ariable can be declared as a list. Simple List V ariables can hold multiple values of single data type. Compound List Variable Compound V ariable can be declared as a list. Compound List V ari ables can hold multiple values of different data types. 4. 2 'Variable' Defini tion and its Attributes Definition-V ARIABLE A Variable definition is similar to any other definition. The behaviour of the variable is specified by the programmer via 'V ariable' definition. Syntax [Variable : <Variable Name>] Attribute : Value A meaningful name which determines its purpose can be given as a variable name. Attributes of 'Variable' Definition Let us discuss the attributes of 'V ariable' definition in detai l. Attribute-TYPE This attribute determines the Type of value that will be held b y the variable. All the data types Object: Voucher Compound Variable: CLV Emp Object “Voucher” is having methods directly under it such as Date, Voucher Number, Narration, etc. Compound Variable “CLV Emp” is having Simple Member Variables such as Name, Age, Salary, etc. Voucher is having the repeated method Basic Buyer Address (Simple Collection) CLV Emp is having the Simple List Member Variable 'Contact Nos' Voucher is having the collection “Inventory Entries” (Compound Collection). CLV Emp is having the Compound List Member Variable 'Relatives' Voucher object is not having another voucher (primary object) under it directly. CLV Emp is having the another Compound Member Variable 'Contact Address' | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 576 supported by TDL such as String, Number, Date, etc., can be used to specify the variable data type. In the absence of this attribute, a variable assumes to b e of the Type 'String' by default. Syntax [Variable : <Variable Name>] Type : <Data Type> Example: [Variable : Group Name Var] Type : String In this example, a variable which holds the data of Type 'String' is defined. Attribute-DEFAUL T The default value of variables can be specified during definiti on, using DEFAUL T attribute. It is the initial value assigned to the variable when it is instantiated / declared. We can also specify the default value during declaration / instantiation. The difference is that the default value specified using this attribute at definition time will be applicable to a ll instances of the variable declared (at any scope). Default value specified while declaration will appl y only to the specific instance. Syntax [Variable : <Variable Name>] Default : <Default Value> Example: [Variable : Group Name Var] Type : String Default : $$Locale String : "Sundry Debtors" In this example, the default value for the variable is set as “Sundry Debtors”. Attribute-VOLATILE If the Vo l a t i l e attribute in V ariable definition is set to Yes, then the variable is capable of retaining previous values from the caller scope. The default value of this attribute is Yes, i. e., if the variable by the same name is declared in the called Report/Function and the 'Volatile' attribute is set to “Y es”, then in the called Report, it will assume the last value from the caller Report. The default value of the attribute 'Volatile' is always YES. For better understanding, let us elaborate it further. When a variable is declared / instantiated, it assumes a default value. The default value which it assumes is controlled by the following factors: 1. If 'Volatile' is set to “Y es” for a variable in its definitio n which is instantiated / declared inside a function/report, and the variable by the same name exists in th e parent scope, then it will take its default value from the Parent scope. If no variable by the same name exists in the parent scope, it will take the default value specified within the defi nition. Declaration and scope will be covered in det ail in the subsequen t topics. The above explanation will be more clear after that. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 57 7 2. If the default value is specified within the declaration itse lf, it will assume that value. If a new report Report2 is initiated, using a volatile variable Group Name Var, from the current report Report1, the same variable in Report 2 will have the default value as t he last value saved in Report 1. Within Report 2, the variable can assume a new val ue. Once the previous report Report1 is returned back from Report2, the previous value of the variable will be restored. A classic example of this is a drill down Trial Balance. Syntax [Variable : <Variable Name>] Volatile : <Logical Value> Example: [Variable : Group Name Var] Type : String Volatile : Yes V olatile Attribute of Group Name Var V ariable is set to Yes, which means that 'Group Name V ar' can inherit values from one Report to another. V ariables defined at the function level are Non Volatile by def ault. They do not inherit the values from the caller scope. Attribute-PERSISTENT This Attribute decides the retention periodicity of the variabl e, i. e., till when it will retain the value: i) till application termination, or ii) after application termi nation as well. Setting the attribute Persistent to Yes, means that the value saved during the last application session will be retained permanently in the system. When the next session of T ally is st arted, it will take its initial value from the value saved in the previous session, i. e., the latest value of the variable will be retained across the sessions. Please note that V ariables declared at the system scope can only be persisted. A List variable at System scope can also be persisted by specif ying the 'Persistent' attribute for its element variable (whether it is simple/compound) within the def inition. Inline variables even at system scope cannot be persisted. Inline variable declaration w ill be discussed in further topics. Syntax [Variable : <Variable Name>] Persistent : <Logical Value> Example: [Variable : SV Backup Path] Type : String Persistent : Yes Scope will be discussed in deta il in the subs equent topics. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 578 The Attribute Persistent of the variable SV Backup Path has been set to Yes, which means that it retains the latest path given by the user, even during the subsequent sessions of T ally. Attribute-REPEA T The attribute Repeat for a variable is used for its usage in Columnar Reports. It ac cepts Collection name and optional Method name, as parameters. Multiple values a re stored in the variable based on an implicit Index. Method value of each object of the collec tion will have to be picked up and stored in the variable, based on implicit index. In case the method name is not specif ied, the variable name is considered as the method name and picked up fr om the collection. Syntax [Variable : <Variable Name>] Repeat : <Collection Name> [:<Method Name>] Where, <Variable Name> is the name of the variable. <Collection Name> can be any expression which ev aluates to a Collection name. <Method name> is the name of the method whose value needs to be picked up fro m each object of the collection. If not specified, the variable name is consi dered as the method name. Example: [Variable : SVCurrent Company] Volatile : Yes Repeat : ##DSPRepeat Collection Suppose 'DSPRepeat Collection' holds the value “List of Primary Companies”. Method value 'SVCurrent Company' will be gathered from each object of the col lection and stored in index 1, index2, and so on. Attribute-V ARIABLE The attribute Variable is used to define the member variables (Simple/Compound) for a Compound V ariable. Syntax [Variable : <Variable Name>] Variable : <Variable Names> [:<Data Type> [:<Value>]]All the Persistent Variable Values are st ored in a File Name d Tally Sav. Cfg in the folder path specified for Tally Configuration file in F12-> Data Configuration. Each time Tally is restarted, these variable values are accessed from this file. 'Repeat' Attribute will be elabor ated further under the topic “Implic ation of Repeat Variables in Columnar Report”. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 57 9 Where, <Variable Names> is the list of Simple or Compound V ariables, separated by comma. <Data T ype> is used to specify the data type of Simple V ariable. In case of Compound V ariable, data type cannot be specified, as it consists of members belonging to various data types. If the data type is not mentioned, the primary variable definition is mandatory. <Value> is the default/initial value provided for the variable. Specifying <Data Type> and <V alue> is optional. If data type is specified, then it is called inline declaration of variable. [We will learn about inline declaratio ns and Compound V ariables further]. Example: [Variable : CLV Emp] Variable : Name : String Variable : Age : Number : 25 Variable : Salary : Amount Variable : Relatives In this example, the simple variables Name, Age and Salary and the compound variable 'Relatives' are defined as members for the Compound V ariable CL V Emp. Attribute-LIST V ARIABLE The attribute List Variable is used to specify a list of Simple/Compound V ariables. Syntax [Variable : <Variable Name>] List Variable : <Variable Names> [:< Data Type> [:<Value>]] Where, <Variable Names> is the list of Simple or Compound V ariables, separated by comma. <Data T ype> is the data type of Simple V ariable. In case of Compound V ariab le, data type cannot be specified, as it consists of members belonging to various da ta types. <Value> denotes the no. of elements in the list. Specifying <Data Type> and <V alue> is optional. Example: [Variable : CLV Emp] Variable : Name : String Variable : Age : Number Variable : Salary: Amount List Variable : City : String : 3 List Variable : Relatives [Variable : Relatives] | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 580 Variable : Name : String Variable : Age : Number Variable : Relation : String Variable : Salary : Amount In this example, in addition to simple variables, a simple list variable City and a compound list variable Relatives are defined as members using the attribute List Variable. A separate definition is required for the compound list variable Relatives, as it holds the multiple values of different data types. 4. 3 Variable Declaration and Scope V ariables can be declared at various scopes. The availability o f the variable within the definition under which it is declared is called as the scope. The lifetime of the variable will be within the scope. For example, if the scope of a particular variable is wi thin a function, then the variable will last till the function is executing, and then it is destroyed. V ariables can be declared at System, Report and Function scopes. Let us have a detailed look on the variable scopes. System Scope declaration V ariables declared at the system level will start their life wh en the application starts, and will be alive till the application's termination. System variables are declared using a special [System: V ariable ] definition. The variables declared at system scope are accessible everywhere in the syste m. Syntax [System : Variable] Variable Name : <Initial Type Based Value> Or Variable : <Variable Names> [:<Data Type>[:<Value>]] List Variable : <Variable Names> [:<Data Type>[:<Value>]] Where, <Initial T ype Based Value> is the initial value specified to the variable. The variables can be declared at the system scope by using the above. The usage of the attributes 'V ariable' and 'List V ariable' is same as described above in the “V ariable Definition”. Example: [System : Variable] BSVertical Flag : No The BSVertical Flag V ariable is declared in System Scope. Hence, this variable valu e being modified in a Report, is retained even after we quit and re-enter the report. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 58 1 Report Scope declaration V ariables declared at Report definition are termed as having 'Report' Scope. These variables will exist till the life of the repor t. The variables declared at Re port scope are accessible from the report itself and all the TDL elements which are executed from within this report such as another report, function, etc. Report variables get their default value from definition specif ication, or from the declaration specification, or the values are inherited from the owner scope, if the variable is marked as Volatile. Report allows two special attributes SET and PRINT SET t o s e t / o v e r r i d e t h e v a l u e s o f t h e variable during the startup of t he report in Display / Print mo de respectively. 'Form' definition also has a SET attribute, which overrides the variable's value during startup creation and subsequent re-creation of the form during any refr esh / regeneration. We will study about these value specification attributes in detail under the topic “Manipulating Simple and Compound List V ariables”. Syntax [Report : <Report Name>] Variable : <Variable Names> Or Variable : <Variable Names> [:<Data Type> [:<Value>]] Or List Variable : <Variable Names> [:<Data Type> [:<Value>]] The variables can be declared at Report scope by using the abov e. The usage of attributes Variable and List Variable is same as described above in the “V ariable definition”. Example: [#Report : Balance Sheet] Variable : Explode Flag 'Explode Flag' V ariable is made local to the Report 'Balance Sh eet' by associating it using the Report attribute ' Variable '. This variable retains its value as long as we work with this Report. On exiting the Report, the variable is destroyed and the values ar e lost. Function Scope declaration Function (User Defined Function) also allows the variables to b e declared at its scope. Function variables have lifetime till the end of execution of the functi on. Function variables can also be declared with default value. Function variables will never inherit the value from the paren t context. This means that 'Volatile' attribute on function variables has no effect. Functions allow actions to change the values of the variables. Function allows a special scope called ST A TIC. A static variabl e declared in a function is equivalent to a system variable, but can be accessed only withi n the defined function. Its initial value is set only during the first call to the function, and later it re tains the value for further calls. Only simple or compound variables can be declared as static. List va riables are not currently supported at 'Static' scope. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 582 Syntax Variable : <Variable Names> Or Variable : <Variable Names> [:<Data Type> [:<Value>]] Or List Variable : <Variable Names> [:<Data Type> [:<Value>]] Or Static Variable : <Variable Names> [:<Data Type> [:<Value>]] The variables can be declared at 'Function' scope by using the above. The usage of the attributes Variable and List Variable is the same as described above in the “V ariable” definition. Example: [Function : Factorial Of] Variable : Factorial The Function ' Factorial Of ' requires variable ' Factorial ' for calculation within the Function. Example: [Function : Sample Function] Static Variable : Sample Static Var : Number The static variable ' Sample Static Var ' retains the value between successive calls to the Function 'Sample Function'. Inline Declaration V ariables can also be defined (with limited behaviour) during d eclaration itself; so a separate definition would not be mandatory. This is called inline variable specification (i. e., during declaration itself, the variables are defined inline). Only the DA T A TYPE and the DEFAUL T V ALUE can be specified as th e behaviour for inline variables. If the DA T A TYPE is spec ified as a var iable name (i. e., not an implicit data type key word such as String, Amount, etc. ) or is left blank, it is treated as a pre-defined variable. Persistence: Inline variables even at system scope cannot be persisted. Declaring Simple Variable Inline The ' Variable ' attribute allows declaring Simple V ariable inline by specifyi ng the data type. Initial value to the variable can also be specified optionally. Syntax Variable : <Variable Names> [:<Data Type> [:<Value>]] Where, <Variable Names> is a list of Simple V ariables, separated by comma. <Data T ype> is the data type of the Simple V ariable. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 58 3 <Value> is the default/initial value provided for the variables, and th is value specification is optional. Example: [Report : Cust Group Report] Variable : Var Group Name1, Var Group Name2 : String : “Sundry Debtors” In this example, the Simple V ariables 'V ar Group Name1' and 'V ar Group Name2' of ty pe 'String' are declared in a Report; hence, the following separate variable de finitions are not required, which will help to reduce the coding complexity. [Variable : Var Group Name1] Type : String [Variable : Var Group Name2] Type : String Declaring Simple List Variable Inline 'List V ariable' attribute allows declaring Simple List V ariable inline by specifying the Data Type. If the default value is specified, it is treated as the count to i nitialize the list with the specified elements by default. Syntax List Variable : <Variable Names> [: <Data Type> [: <Value>]] Where, <Variable Names> is a list of Simple V ariables, separated by comma. <Data T ype> is the data type of the Simple V ariable. <Value> is treated as the count to initialize the list with the specifi ed elements by default. The number of elements can be specified only for an index-based lis t. Example: [System : Variable] List Variable : Var Group Name1, Var Group Name2 : String : 10 In this example, the variables 'V ar Group Name1' and 'V ar Group Nam e2' of 'String' data type are declared as inline simple list variables at System level, and e ach variable will have 10 elements by default. Declaring Compound List Variable Inline For Compound List V ariables, definition is mandatory. They cannot be declared inline. 4. 4 Using Modifiers with Variables V ariable allows static modifiers such as Add/Delete/Change and Dynamic modifier 'Local'. Static Modification Add/Delete/change modifiers can be used on variables to change the behaviour. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 584 Example: [#Variable : SV From Date] Delete : Default Locally modifying variables When different reports require the same Compound V ariable, and some modifications are required specific to respective reports, like adding additional members (local to the report); this is possible through the Dy namic Modifier 'Local'. Example: In this example, a Compound V ariable CL VEMP is defined as shown: [Variable : CLV Emp] Variable : Name : String Variable : Designation : String Variable : Age : Number Variable : Salary : Amount List Variable : Contact Nos : String List Variable : Relatives Variable : Contact Address ;; Defining Compound List Variable [Variable : Relatives] Variable : Name : String Variable : Age : Number Variable : Relation : String Variable : Salary : Amount ;;Defining another compound variable [Variable : Contact Address] Variable : Street Name : String Variable : City Name : String In 'Employee Report1', the vari able is declared and no modifica tions are required locally. [Report : Employee Report1] Variable : CLV EMP | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 58 5 In 'Employee Report2', the same variable is declared but locall y one member variable is added and one existing member variable is deleted. [Report : Employee Report2] Variable : CLV EMP Local : Variable : CLV EMP : Add : Variable : Qualification : String Local : Variable : CLV EMP : Delete : Variable : Age Also, member variables can be localized within a compound varia ble. This provides the ability to re-use a compound structure defined earlier and do any local mo difications, as required. Example: [Variable : CLVEMP] Variable : Contact Address Local : Variable : Contact Address : Add : Variable : State : String 4. 5 List Variable Manipulations Simple and Compound List variables support various data manipul ation operations such as Adding/Deleting/Expanding List elements, V alue Specifications, Retrieving values from the list elements, Searching and Sorting, Populating List V ariable from a Collect ion, etc. New Actions and Functions specific to List V ariables have been introduced for t hese manipulations. Before looking into these manipulations, let us understand the concept of Key, Index and V ariable Path Specificaton using Dotted Notation Syntax. Concept 1. Key List variables can hold multiple values of variable types using a string based 'Key' specification. 'Key' is of type String, by default. We can specify a different data type for a key onl y in scenarios where we require key-based sorting. It is optional to specify k ey value while adding values to the list variable. The TDL Programmer has to explicitly specify the key value. Key is unique for all elements in the list. If an element is added with duplicate key, the existing element is overwritten. It is advisable to use a key only if we require frequent access to elements of the list based on key. 2. Index An element of the list can be accessed via 'Index'. Index of an element is the location/position of the variable from the first element in the current sorting orde r. Even if we have specified keys for elements of a list, index is generated internally. It is always possible to access each element in the list by specifying the index wit hin square brackets [ ] in the dotted notation syntax. This is explained below. Index can be negative as well. In that case, it is possible to access the elements in the reverse order of entry. 3. Variable Path Specification using Dotted Notation Syntax We aware that in T ally. ERP 9, method value of any object includ ing its sub-collections to any level can be accessed or modified with dotted notation syntax. The be haviour of the symbol prefix $ was enhanced to access the method value of any object, and an a ction MODIFY OBJECT was introduced to modify multiple values of any object. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 586 Compound V ariables allow us to store values of different data t ypes. A member variable can be a single instance or a list vari able. A member variable can be a compound variable and can have members again, and thus, any hierarchy can be created. In short, it is similar to a Data Object. Hence, all the attributes and actions which operate the V ariabl e, have now been enhanced to take extended variable path syntax, i. e., the variable path can be s pecified using dotted notation syntax. The syntax can be used to fetch any value from any memb er within the hierarchy. This syntax is applicable wherever we need to specify either the var iable identifier or access the value of the variable. In case of value access the operator ## is use d. V alue access using operator ## has been discussed in detail in the topic Index Based Retrieval using ## Operator. Syntax <Element Variable Specification>. <Member Variable Specification>. + <Simple Member Value specification> Where, <Element Variable Specification> can be a Compound V ariable or Compound List V ariable [Index Expression]. <Member Variable Specification> can be a Compound V ariable Member or Compound List Member V ariable [Index Expression]. <Simple Member Value Specification> refers to the name of the simple member in the specified path. <Index Expression> is an expression evaluating to a number. Suffixing a variable with index refers to an Element V ariable. It can be positive or negative. Negative index denotes reverse access. Example: 1Consider the compound variable defined below:-[Variable : CLV Emp] Variable : Name : String Variable : Age : Number Variable : Salary : Amount List Variable : Relatives [Variable : Relatives] Variable : Name : String Variable : Age : Number Variable : Relation : String Variable : Salary : Amount The same is declared at System Scope, and hence can be accessed anywhere in the system. [System : Variable] | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 58 7 List Variable : CLV Emp Example: 2 Suppose we want to set the value of a simple variable 'Employee Name', which is declared at Report Level: [Report : Employee Report] Variable : Employee Name : String SET : Employee Name : ##CLVEMP[1]. Name The variable Employee Name will be set with the value of the member “Name” of the first element of the Compound List V ariable “CL VEMP”. Example: 3In case the age of first relative of the second employee needs to be displayed, the following statement would be used in the field in a report. [Field : Rel Age] Set As : ##CLVEMP[2]. Relatives[1]. age The value specification attributes and actions, with the enhanc ed variable path specification, will be discussed in detail in the further topics. List Variable Manipulations-A Detailed Look Let us have a detailed look on Li st V ariable manipulations with examples:-Adding/Deleting/Expanding Elements 1. Adding Elements to the List Variable Action-LIST ADD The Action LIST ADD is used on a list variable to add an elemen t to the list variable based on KEY. This is mandatory before we set value into the element. KE Y is compulsory in this case. Key is unique for all elements in the list. If an element is added with duplicate key, then the existing element is overwritten. Syntax LIST ADD : <List Variable Specification> : <Key Formula> [:<Value Formula> [:<Member Specification>]] Where, <List Variable Specification> is the Simple List or Compound List V ariable specification. <Key Formula> can be any expression which evaluates to a unique string value. <Value Formula> can be any expression which returns a value. It sets the initia l value of the element variable, and is optional. <Member Specification> is required only if the value needs to be added to a specific m ember of a Compound List V ariable. If member specification is not provided, the first member variable is considered for the value. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 588 T o add multiple values dynamically to the List variable, we can use LIST ADD within a looping construct like While, W alk Collection, etc. Example:Adding elements to Simple List Variable using LIST ADD1. Adding an element to the Simple List V ariable SL V Emp with a Key LIST ADD : SLV Emp : “E001” 2. Adding an element to the Simple List V ariable SL V Emp with a Key and a value LIST ADD : SLV Emp : “E001” : “Kumar” 3. Adding an element to the Simple List V ariable SL V Emp with a Key and a value, and subse-quently overriding a value corresponding to a particular key LIST ADD : SLV Emp : “E001” : “Kumar” LIST SET : SLV Emp : “E001” : “Keshav” The value corresponding to the Key 'E001' is changed to Keshav Adding Elements to Compound List Variable using LIST ADDA Compound V ariable CL V Emp is defined, which stores employee d etails such as Name, Age, Salary, etc., and the details of the Relatives. [Variable : CLV Emp] ;;simple member variable Variable : Name : String ;;simple member variable Variable : Age : Number ;;simple member variable Variable : Salary : Amount ;;compound list member variable List Variable : Relatives ;; Compound Variable is defined here [Variable : Relatives] Variable : Name : String The actions LIST APPEND and LIST SET ar e aliases for the action LIST ADD. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 58 9 Variable : Age : Number Variable : Relation : String Variable : Salary : Amount The same is declared at the System Scope; hence, can be accesse d anywhere in the system. [System: Variable] List Variable: CLV Emp 1. Adding an element to Compound Li st Variable CLV Emp with a Ke y LIST ADD : CLVEmp : “E001” 2. Adding an element to Compound List V ariable CL V Emp with a Ke y and a V alue LIST ADD : CLVEmp : “E001” : “Kumar” Since member specification is not provided, the first member variable is considered for value. 3. Adding an element to Compound List V ariable CL V Emp with a Ke y and a value with member specification LIST ADD : CLVEmp : “E001” : 25 : Age Since member specification is provided, member variable 'Age' is considered. 4. Adding an element to the Compound List Member of a Compound L ist V ariable with a Key and a value with member specification LIST ADD : CLVEmp[1]. Relatives : “R001” : “Prem” : Name In this example, we are adding an element to the Compound List V ariable “Relatives” and the member variable 'Name' is considered for the value. 'Relatives' is a Compound List Member variable of the Compound List V ariable CL VEMP. Action-LIST ADD EX This action is used on a list variable to add an element to the list variable without KEY. Syntax LIST ADD EX : <List Variable Specification> [:<Value Formula> + [:<Member Specification>]] Where, < List Variable Specification> is the Simple List / Compound List V ariable specification. <Key Formula> can be any expression which evaluates to a unique string value. <Value Formula> can be any expression which returns a value. It sets the initia l value of the element variable, and is optional. The values are hard coded in the exampl es for explanation purpose. The above Simple and Compound List Variable examples are used to explain further list variable manipulations. | TDL_Reference_Manual.pdf |
What's New in Release 1. 8 590 <Member Specification> is required only if the value needs to be added to a specific m ember of a Compound List V ariable. If member specification is not provided, the first member variable is considered for the value. Adding elements to Simple List Variable using LIST ADD EX 1. Adding an element to Simple List V ariable SL V Emp LIST ADD EX : SLV Emp 2. Adding an element to Simple List V ariable SL V Emp, with V alue LIST ADD EX : SLV Emp : “Kumar” Adding elements to Compound List Variable using LIST ADD EX1. Adding an element to Compound List V ariable CL V Emp LIST ADD EX : CLV Emp 2. Adding an element to Compound List V ariable CL V Emp, with val ue LIST ADD EX : CLV Emp : “Kumar” Here, since member specification is not provided, first member variable is considered for value. 3. Adding an element to Compound List V ariable CL V Emp, with val ue and member specification LIST ADDEX : CLV Emp : 25 : Age Here, member specification is p rovided, hence member variable ' Age' is considered for the value. 4. Adding an element to the Compound List Member variable of a C ompound List V ariable with value and member specification LIST ADDEX : CLVEmp[1]. Relatives : “Prem” : Name In this example, we are adding an element to the Compound List V ariable “Relatives” and the member variable 'Name' is considered for the value. 'Relatives' is a Compound List Member variable of the Compound List V ariable CL VEMP. 2. Deleting Elements from the List Variable Action-LIST DELETE The Action LIST DELETE is used to delete an element from the li st based on Key. Key formula is optional. If not specified, all the elements in the list are de leted. Syntax LIST DELETE : <List Variable Specification> [ : <Key Formula>] Where, <List Variable Specification> is the Simple List or Compound List V ariable specification. Action LIST APPENDEX is an a lias for the action LIST ADDEX. | TDL_Reference_Manual.pdf |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.