udiMagic v11 Release 1.3

The following new features have been  incorporated in udiMagic v11 Release 1.3:

Data Grouping or GroupBy

udiMagic now supports data-grouping. This feature makes it possible to automatically import summarized data into Tally ERP. Here's an example :

SOURCE : Excel Sheet extract - Sales with StockItems

As you can see, the Item 1 appears 3 times and Item 2 appears twice in the given data. Now, here's how this data will be imported into Tally when groupby is enabled.

DESTINATION : Tally screen - After importing data using udiMagic 

As you can see, the Item 1 and Item 2 quantity and value are now grouped.

i.e.
Item 1 (3 + 2 + 5 = 10 Nos)
Item 2 (4 + 6 = 10 Nos)

Remarks
1. The Data-Grouping feature is now supported by the template "Vouchers-Sales-Purchase-with-StockItems-Advanced.xls"
2. A new field / column GroupBy has been added. 
3. A sample Sales entry with GroupBy set as Yes has been included in the said Standard template.

OTHER TEMPLATE MODIFICATIONS

1. Master-StockItemMaster.xls

The following new fields have been added :
a. Cess on Quantity (Column BI)
b. State Cess on Quantity (Column BK)

2. Vouchers-V11-Sales-Purchase-with-Stockitems-Advanced.xls

The following new fields have been added :

a. Shipping Bill No (Column FQ)

b. Shipping Bill Date (Column FR)

c. Port Code (Column FS)

FIXES

1. Vouchers-V11-Sales-Purchase-with-Stockitems-Advanced.xls

An error "Cost Centre xxx does not support forex amount" appears when Sales or Purchase entry without Stockitems is imported in Tally and the entry included Cost Centres and forex currency. This issue has now been corrected.

Could not set SVCURRENTCOMPANY

The aforesaid error may appear while importing data from Excel to Tally in the following situations :

Case 1
The Company Name in Tally ERP contains special characters viz Linefeed [#13] and carriage return [#10] at the end of Company Name. To check whether the Company Name is correct or not, please follow the underneath steps :

1. Open your Company in Tally ERP
2. Press Ctrl+F3 to select the "Company Info" 
3. Next, select the option "Alter"
4. In the Company alteration screen, press END-key while in the the Company Name field. If there is space between the last character and the cursor (as shown in this snapshot), press BACKSPACE to remove the special characters at the end of Company Name and save it.

Solution

ALTER the Company and remove the special characters (blank spaces) if any from the end of the Company Name. 

Case 2

The Company Name in Tally ERP contains & (i.e. ampersand sign). Example, the Company Name is "ABC & Co"

Solution

A. Upgrade to the latest version of udiMagic; 

or 

B. Change the Company name in Tally. Example: "ABC and Co"

udiMagic v11 Release 1.2

The following changes have been done :

udiMagic v11 Release 1.2

1. In the udiMagic screen "Create a Custom Custom", the grid HEIGHT for Standard Excel and User Excel template has now been increased for better user experience.

2. The Tally to Tally feature (separately available) is now compatible with the latest Tally ERP.

udiMagic v11 Release 1.1

1. In some of the Standard templates, the "DataFromRow" and "MappingRow" was incorrectly specified. This has now been corrected / fixed. Those using udiMagic v11 Release 1.0 are advised to upgrade to the latest udiMagic release.

INTRODUCING UDIMAGIC V11.0

We are pleased to announce the launch of udiMagic v11.

The details are as follows :

TEMPLATE MODIFICATIONs

The following templates now support multi-currency feature :

1. Vouchers-V11-Bank-statement.xls
2. Vouchers-V11-Bank-statement-Single-Column-Dr-Cr.xls
3. Vouchers-V11-Financial-Transactions-Single-line-entry-Basic.xls
4. Vouchers-V11-Financial-Transactions-Single-line-entry-Advanced.xls

udiMagic v10 Release 2.3

TEMPLATE Modifications 

1. Vouchers-V10-Financial-Transactions-Single-line-entry-Basic.xls

NEW COLUMNs
Column I  - PARENT DR. LEDGER (Specify the Parent Group name for Debit Ledger)
Column K - PARENT CR. LEDGER (Specify the Parent Group name for Credit Ledger)

Remarks
a. These newly added columns are optional.
b. However, for Bank entries you must specify the Parent Group Name as "Bank Accounts" for the Bank entries to be reflected in Bank Reconciliation Statement.

2. Vouchers-V10-Financial-Transactions-Single-line-entry-Advanced.xls

Remarks
For Bank entries you must specify the Parent Group Name as "Bank Accounts" for the bank entries to get reflected in Bank Reconciliation Statement.

3. Vouchers-V10-Horizontal-Sales-Without-Stockitems.xls

Old Formula in Column AC
=SUM(AD6:IV6)

New ARRAY Formula in Column AC (Press Ctrl + Shift + Enter for Array Formula)
=SUM(ROUND(AD6:IV6,2))

In the Column AC, we have now used Array Formula instead of simple Sum() function. This is because we need to Round off the values to 2 decimals before adding them using the Sum() function.

What are Array Formulas?
Array formulas are powerful formulas that enable you to perform complex calculations that often can’t be done with standard worksheet functions. They are also referred to as "Ctrl-Shift-Enter" formulas, because you need to press Ctrl+Shift+Enter to enter them.

4. Vouchers-V10-Horizontal-Purchase-Without-Stockitems.xls

Array Formula used in Column AC as mentioned in the previous point

OTHER CHANGES
The following fixes / corrections have been done in udiMagic v10 Release 2.3

Invalid key
The aforesaid error appears when we copy/paste the udiMagic Serial Number while activating the license. This problem has been now resolved. In the older versions, users can use "Right-click and then Paste" functionality to paste the Serial Number. 

XML Parse error
The aforesaid error is displayed when udiMagic Software is started and then the software hangs. This problem has been now resolved.

udiMagic v10 Release 2.2

The template "Vouchers-V10-Sales-Purchase-With-Stockitems-Advanced.xls" now includes additional columns for Cost Category and Cost Centre for the Party ledger.

TEMPLATE : Vouchers-V10-Sales-Purchase-with-StockItems-Advanced.xls
NEW COLUMNS
1. Cost Category (Columns L)
2. Cost Centre (Columns M)

The following fixes / corrections have been done in udiMagic v10 Release 2.2

XML Parse error
The aforesaid error is displayed while importing the template Vouchers-V10-Financial-Transactions-Single-line-entry-Basic.xls when the CompanyName in Tally contains Ampersand Sign (&) . This problem has now been resolved.

PS: Those using the older versions of udiMagic can set / enable the option "Disable Fetch Objects" in udiMagic settings to resolve the issue.

Invalid USB drive details
When activating with USB flash drive, invalid details are shown in certain cases. This problem has now been resolved.

New setting option in udiMagic Settings screen
A new option "Remove Invalid XML Chars automatically" is now included in the udiMagic Settings. When enabled, invalid XML chars are automatically removed from text data. This option is enabled, by default.

PS:
Option "Use Advanced sockets" has now been removed from the udiMagic settings. This option was kept for backward compatibility purpose only and hence has been now removed. 

SQL Server : Using named parameters in SQL Query

SQL Statement with named parameters

You can use named parameters :FromDate and :ToDate in your SQL Query to provide input for the fields "From Date" and "To Date" in udiMagic for uploading data from SQL Server to Tally ERP.

How to use parameters in SQL query?

Here's a sample SQL SELECT query that shows how to use the :FromDate and :ToDate named parameters

SELECT field1, field2, fldDate FROM table WHERE table.fldDate>=:FromDate AND table.fldDate<=:ToDate

Instead of hard-coding the period (from and to dates) in SQL-query, we have used 2 named parameters viz :FromDate and :ToDate. The values for these parameters are assigned at runtime based on the period you enter in the udiMagic screen.

Remarks
1. In udiMagic screen, you must specify the FromDate and ToDate in dd/mm/yyyy format only.
2. The date format of SQL server  or your system may be different (ex: yyyy-mm-dd). However, udiMagic automatically sets the date format internally and hence there is no need to change your SQL Server / System date format.