ERP 2.08.00.00 Version Announcement

Warnings

•             If there are tables generated by General Table Management section and used before, these tables have to be updated as well. Table updates have to be done before the firm update transaction.
•             "Version Upgrade for Tables" operation must be performed in 1.7x.xx, 1.8x.xx version upgrades.
•             Database Tools have to be generated for company periods. 
•             Upgrading can be started for all firms at the same time.
•             If Unity Objects and OD usage is available, these versions’ tools have to be updated.

Warnings for 1.88.xx.xx version:

G/L connection codes must be redefined in 1.87.xx.xx version, and the following query must be run for all companies separately before running " Version Upgrade for Tables" operation for those upgrading to 1.88.xx.xx version.

CREATE TABLE [dbo].[LG_XXX_ACCCODESTMP](
[FIRMNR] [int] NULL
) ON [PRIMARY]

Warnings for 1.8x.xx.xx versions

•                        By 1.8x.xx version, new directories are added to STFICHE, PRCLIST, PAYTRANS, L_LDOCNUM, KSLINES, EMUHACC, SRVCARD, CLCARD, INVDEF, SPECODES tables with a view to provide performance increase. During “Version Upgrade for Tables” operation, updating may take some time due to the new directories to be added. Furthermore, along with the new directories, there may be a growth in database side, depending on the number of data in kept in these tables. 
•                       By 1.8x.xx versions owing to recent features, new tables and table fields are added to database side. You can view information documents about newly added fields to the features such as Bank Credit Tracking, exchange rate difference calculations from Safe Deposit and Bank and f. currency tracking in safe deposit. 
•                         In HR-Unity integration there will be no need to upgrade the existing versions of these two programs by Unity 1.84.00 version. As of 1.84.00 version, the integration will be done according to the content of defined personnel G/L codes. This feature will be valid for the HR 3.7.4. version and the later versions.

Warnings for 1.86.00.00 Version

•                         In 1.86.00.00 version, it is provided to perform banking transactions in accordance with the authorizations of the Garanti Bank service contract by Logo-Garanti integration. In order to work with this configuration, make sure that the Microsoft.NET Framework 2.0 is installed in all terminals during version updates. After new version installation, when you want to start the system administration or the application, a link will be opened that will provide you to install Microsoft.NET Framework 2.0 automatically. This link will be active only when the internet connection in terminals is active. Users who will not use LOGO - Garanti Integration must remove "Garanti Bankası (2009)" addition authorization from System Administration > Users > Addition Authorizations.
•                          As of 1.86.00.00 version, the Connect version updates will be done at the same time when the application version is updated. And Logo Connect Configuration info will be copied to administration folder. Because Connect Service contracts will be updated too, the related terminal’s internet connection has to be active. Please read the relevant documents of this version for further information.
•                         Users upgrading from 2.00 or earlier versions must install all additional specification packages and user licenses before upgrading version.

Warnings for upgrading from 2.04.00.00 and earlier versions:

•                   Database architecture has been updated. In line with the relevant arrangements, SEQ tables are removed and tables are converted to identity feature. Converting tables to identity feature will be performed for General tables in System Administration by updating General Table Management, and it will be performed for Firm tables by updating firm tables by version. Updating firm tables may take a longer time than the earlier version, please do not interrupt  the process.
•                      While upgrading to 2.04 version, INDEXES added (apart from the application) may be deleted during IDENTITY update. Therefore users must take a back up of these indexes before upgrading and recreate them after upgrading.
•                      If there are views created before upgrading in database by using SCHEMABINDING, these views must be deleted.
•                 After upgrading identity, users will not be able to access the relevant database through programs of the earlier version. Even if not all firms are upgraded, the structure of joint tables will change and tables with SEQ extension will be deleted. The absence of tables with SEQ extension indicates that data will not be used in earlier versions.