**You MUST install or upgrade all modules to v22 at the same time, including common components, e.g. if you have two Sicon products that are pre-v17 and you install a new product (not previously installed) which is v22, then ALL modules HAVE to be upgraded Sicon v22**
NB: Import template definitions and examples are now included on each import screen for all relevant products. There will be no import templates on our website to download.
To install the Sicon v22 add-on packages, please install the new v22 add-on package as if it is a new product install. DO NOT TRY AND UPGRADE IT.
You will get some warning messages during the install and you may get a failed to install message, please continue and ignore these message. Then remove the previous version of the add-on package.
https://www.sicon.co.uk/user-guide/installing-upgrading-sicon-additions-sage-200/
Doing the install in this way will ensure you maintain your user configured menus. If you remove the add-on and then add the product you will not lose any data but you will have to setup the user menus again.
If the Sicon Stock Transfer and Contact Manager packages are installed, they will need to be un-installed. These are now included in the Common Components install and if left installed will cause data model errors.
Note: No data will be lost when these add-on modules are removed.
Important Note about Data Model warnings during upgrades: If you have several Sicon modules currently installed, until you install & remove the final add-on package it is likely that you will see a message that indicates an error / issue – don’t worry, this is simply because until the final module is installed and removed, the data model is not fully compiled. When you install & remove the final Sicon v22 module the Data Model file(s) will then be built.
For more information, please refer to the Product New Features & Important Information documents.
You are no longer able to download individual files from the BP Portal manually, instead you will need to use the Sicon Installer. A new version of this is availabe for Sicon v22 that will further improve the installation of the Sicon products, stop the installation of incorrect versions, ensure all users are logged out, stop the Web API & WAP services, and restart required services after the installations are complete. NB: we recommend users are logged out during an upgrade/install.
If you need specific file versions for projects you can request these from your project administrator.
**Upgrades to Sicon v22 are one-way. Once ANY single module, including Common Components, is upgraded to v22 then all modules must then immediately be upgraded to v22 – downgrades are NOT possible. The reason this is not reversible is various database tables are moved or migrated to other tables, uninstalling will not revert these changes **
We’ve started making use of the Sage X-tables to improve performance where more than one of our products needs to provide information to the same Sage 200 screen. For example, the Purchase Ledger transaction enquiry has Sicon Documents information and Sicon CIS information from Sicon Construction. Nominal Ledger has the Document count and project/project header. Below is some information about why we’ve started to do this and what challenges we’ve come across during the process:
Speed Issues | Changing the products to work with X-Tables has been relatively straightforward, but when we started rolling this out to sites with speed issues we found problems related to the versions of Sage 200 that they are using.
Sage Hot Fixes | Some versions of Sage have patches to fix the X-Table issues, and some do not. We are looking for ways to work around these version. Our tests have shown that this will work from Sage 200c Summer 2018 onwards, apart from Sage 200c 2020 R2 (Version 12.00.0041), which has a Sage Hot Fix – available here. We are currently testing versions back to Sage Summer 2018 that matches the TLS patch roll back versions. We would not want to force a client to upgrade their Sage 200 in order to use our new versions when they have been told they don’t need to for TLS.
Upgrade Recommendations | We did suggest that all users must be out of Sage 200 when you upgrade to the X-table version. This is still our advice, but we are not enforcing it in the installer as it is impractical in many circumstances. The end result of an upgrade with users logged in can be that all the transaction history appears to be missing. The data is fine and there is a script to run that corrects the problem. This script is included in the installer so it should run automatically, but do not be alarmed if you have missing transactions. Many of you have told us this is a fairly common issue with other ISV’s and your own development that uses X-tables so you are probably more familiar with handling this issue than we are.
The v22 release also includes a new warning screen that will open at start-up for specific Sage 200 settings that cause issues for BP’s and customers. The warning recommends that unconfirmed costs is not used unless really necessary, and that the update stock at invoice setting is not used if you use barcoding. There are links to the website for further advice on why we are suggesting these settings should be avoided. We are not saying they cannot be used, but if you do use them it is important that you and your customers fully understand the implications of these settings, and you will deal with any nominal reconciliation queries that occur as a result of them. To understand why you should be cautious with unconfirmed costs, please see our Help & User Guide.
With the release of Sicon v22, we are withdrawing the previous CRM mobile app. There is a new app to replicate the CRM web functionality on mobile devices, and this is installed via accessing the relevant CRM website on the mobile device. The functionality in this new mobile app is a significant improvement on the previous one; more information will be available in the coming weeks.
With the release of Sicon v22 we have reduced the number of versions being covered by Mainstream Support from four, down to three. We have taken this step due to the difficulties experienced in trying to maintain active release builds for four different versions of each of our products.
For Sicon v22 the versions covered by Mainstream Support are versions 21, 21.1 and 22.
Sicon version 20 and 20.1 will move to Extended Support, meaning that any required hotfixes will be reviewed on a case by case basis, and the option of updating the customer to one of the newer versions as an alternative may be discussed with the business partner.
Sicon version 19.2 and prior are no longer covered by Mainstream Support. Customers with these versions are still supported under the terms of their support contracts by our Support Team, but no further hotfixes will be done for these versions. In case of any hotfixes being required for these customers, they will need to update to one of the newer versions.
Here is a summary of which versions of Sage 200 are compatible with our products:
| Sicon v22 | Sage 200c |
| Sicon v21.1 | Sage 200c |
| Sicon v21 | Sage 200c |