banner banner Skip to main content

User Defined Fields

In Tally.ERP 9, the structure of an object, the data type and storages required in order to store the
data are all pre-defined by the platform. All the data is stored in the Tally database. By default,
data is always stored in pre-defined storages only.


There may be instances when additional information needs to be stored in the existing objects.
This need gave rise to concept of User Defined Fields (UDF). A UDF can be used to store additional
information to the Tally database. In other words, UDFs store additional information into the
existing objects.


User Defined Fields have a storage component defined by the user. UDFs are stored in the
current object context. They can be of any Tally data type such as String, Amount, Quantity, Rate,
Number, Date, Rate of Exchange and Logical.

Defining UDFs does not serve the purpose, unless it is associated with one or more internal
object. When a UDF is created and used in an already existing report, the data is stored in the
context of the object, i.e., it is always associated to the object to which the report is associated,
i.e., the object in context.


Syntax
[System: UDF]
          Name of UDF: Data Type: Index Number
Where,
Identifies the UDF. Ideally, it should describe the purpose for which it has been
created.
is any of the Tally data types or ‘Aggregate’.
can be any number between 1 and 65536.

Comments

Post a Comment

Popular posts from this blog

Tally ODBC Driver Issue

Based on the Operating System bit (32/64) Tally has given the Exe. However the Micro Soft Excel application should be compatible to O/S and Tally.ERP9. Please note, On 64 Bit OS and 64Bit Tally.ERP9, a 32 Bit Excel application can act as a server with following steps. Please download from the Portal- ‘Microsoft Access Database Engine 2010 Redistributable’.  1. Install AccessDatabaseEngine_x64.exe Installed (steps given below separately.) 2. Excel 32 Bit (Excel 2003) Installed – and acting as server 3. Tally 64 Bit As Client –                      with ODBC Driver [ODBC: "Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};DBQ=C:Tally.ERP 9 4.5 Build 7Sample Data.xls;"] and  Tally 32 Bit as Client – with ODBC Driver [ODBC : "Driver={Microsoft Excel Driver *.xls)};DBQ=Sample Data.xls"] This will resolve the problem by NOT upgrading MS Office to 64 bit. you can continue using 32 bit application of Excel.
16 comments
Read more

LOG In function

During expression evaluation, intermediated values of the expression can be passed to calculator window and a log file ‘tdlfunc.log’ inside the application directory. This is very much helpful for debugging the expression. By default, logging is enabled inside the function. Syntax LOG : < Expression> Where, is the expression whose value needs to be passed to the calculator window. [Function : GetCurrentUserApprovelAmt] Parameter : PsvCurrentUser : String Variable : ApprovelAMT : Amount Return : Amount  10 : Walk Collection : ApprovelRequredColl  11 : If : $CustVAUser =  ##PsvCurrentUser  12 : Set : ApprovelAMT : $ApprovelAmount  12A : Log : ##ApprovelAMT  13 : End If  14 : End Walk  15 : Return : ##ApprovelAMT
Post a Comment
Read more

Differences between Applications and DLLs

Differences between Applications and DLLs Even though DLLs and applications are both executable program modules, they differ in several ways. To 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.
Read more