How to shift udiMagic to another System?

This post guides you on how to shift udiMagic software to another system.

STEP 1: Remove OLD SYSTEM from the Portal

a. Login to the portal using this link: https://udimagic.in/accounts/login/
b. In the Dashboard, click on All Licenses tile. This will display all the license serial numbers in your account.
c. Click on required license no. This will display a new page with the License information.
d. Click the Active Systems tab. Next, select the System to remove and click the Remove System.

STEP 2: Install udiMagic Software on the NEW SYSTEM and Active License

a. Download and Install udiMagic software in the New System.
Download link: https://udimagic.in/downloads/
b. Activate the license using Serial / Key.

Note:
If you do NOT have the KEY, use this link to get the same on your registered email id:
Forgot Key link: https://udimagic.in/forgotkey/

Regarding Server Software Upgradation

We have recently upgraded our Server Software.

udiMagic users using older versions (V12 Release3.3 or lower) may get "Trial version" message. To resolve this issue, users are requested to download and install the latest release (V12 Release 3.4 or higher) from:
https://udimagic.in/downloads/

After installation, you will have to re-activate the license using the Serial / Key no.

If you do NOT have the KEY, use this link to get the same on your registered email id.
https://udimagic.in/forgotkey/

udiMagic Single User vs Multi-user
As per the licensing terms, single user can be used in ONE system, whereas multi-user can be used in max 5 systems. Please refer the licensing FAQs [point 13].

udiMagic v12 Release 3.5

 udiMagic v12 r3.5

New functionality added to Auto-update the application.

FIXES

1. Vouchers-V11-Journal-with-multiple-references.xls 

Problem Description

When splitting Tally data, the following error occurs:
"Bank Allocation tags in non-banking ledgers"

Solution
This issue has been fixed now in v12 r3.5

udiMagic v12 Release 3.4

udiMagic v12 r3.4

FIXES

1. Master-StockItem.xls 

• Changes relating to HSN
• Incorrect column-reference in SKIP condition. Now fixed.
• Added APPEND attribute
• APPLICABLEFROM tag value is now taken from column AT instead of hard-coded value
• Added alert for tax-rates. i.e. IGST = CGST+SGST
  

OTHER CHANGES (v12 r2.8 to v12 r3.3)

Changes in udiMagic software as udiMagic Server Software was upgraded.

udiMagic v9.0 support to be discontinued from 1st Sep 2024

udiMagic v9.0 (or lower versions) customers / users are requested to note that the support for udiMagic v9.0 shall be discontinued from 1st September 2024 and there shall be no product enhancements in udiMagic v9.0 thereafter.

Also, to avail technical support and / or product enhancements, users will have to subscribe / buy the udiMagic Subscription license.

Perpetual license users can continue to use udiMagic v9.0 even after 1st September 2024 in accordance with the licensing agreement, but no support or upgradation to latest version shall be available after the said date.

Run-time error 91

Error : Run-time error 91
Error description : Object variable or With block variable not set

Problem Description
The aforesaid error appears when you click the "Open your Excel file" button in udiMagic Standard template and then select an Excel file having the same name as the standard template file.

Solution
You cannot open two Excel files having the same name at the same time. The solution is to rename one of the files.

udiMagic v12 Release 2.7

 udiMagic v12 r2.7

The following changes have been done in the templates:

1. Master-LedgerMaster.xls 

Added the following columns:
- CC-Email (Column AC)

FIXES

Problem description
In udiMagic settings, CreateDependentMasters is set as disabled and WarnIfMasterDoNotExists is set as enabled. On importing Vouchers, the udiMagic software generates incorrect Warning message showing that the Ledger Master does NOT exists even though it exists in Tally. This happens when the name contains special character like & (ampersign)

Solution
The aforesaid issue has been fixed in Version 12 Release 2.7