Hotfixes
Q: What is a Hotfix?
A: If an issue is found / reported either via Support, a Customer or one of our Partners, it is fixed and Hotfix applied for the benefit of all users.
If you do find something not quite right, always remember to report it to the V1 Support Team in the first instance where it is logged, triaged and applied to the download media.
The last update indicates when the hotfixes listed have been applied to the R14 download media, so a new install downloaded on or after this date will include them.
A Hotfix can come in one of two forms, Core (meaning the front end software) or Integration (meaning back-end code). Check out below to see the latest fixes and enhancements.
Core
Last Update 09/12/2021
Reference |
Problem Summary |
Solution |
DMC-7285 |
When SmartMail is connected to O365 mailboxes it used IMAP4. |
When SmartMail connects to O365 it will now use Microsoft’s Graph API. |
Integration
Last Update 09/12/2021
PIA (DbCapture)
Reference |
Problem Summary |
Solution |
DMI-4022 |
DbCapture may have been configured to automatically extract PO numbers from Invoices. This was causing long delays to the validation process due the tool’s interaction with Windows Defender. |
The tool used to extract PO numbers has been modified and no longer poorly interacts with Windows Defender. |
DMI-4099 |
Excessive validation times on BIS only sites. |
A new flag has been added (PROCESSORDERS). If this is set to 0 then no attempt will be made to process any PO numbers found on the document. If set to 1 then an attempt will be made to process orders. |
DMI-4041 |
Performance issues in DbCapture due to the tool used to monitor requests to X3. |
A new flag has been introduced (DEBUGMODE). When this is set 1 then the tool will be used to monitor requests to X3. When it is set 0 then the tool will not be used. |
DMI-4130 |
When Archiving failed as part of the Export process from DbCapture, on the next attempt a duplicate invoice was created in X3. |
A new field has been introduced to DbCapture. It contains the following options: Create in Sage and Archive, Archive only. It will default to the first option. If Archiving has failed but an invoice has been created in X3 then the second option can be used. |
EDD
Reference |
Problem Summary |
Solution |
DMI-4096 |
When a document is to be printed, the file name was incorrectly constructed. This meant that the document was not printed. |
We now check that the filename is correct before printing. If it is incorrect it moves it to the FAILEDTOPRINT folder. |
EDM
Reference |
Problem Summary |
Solution |
DMI-3752 |
Where files or folders are incorrectly named then the EDM service would not run correctly. |
If a file is incorrectly named a failed folder will programmatically be created to move the file to and an email notification will be sent. |
Hotfix Scenarios
The following spell out in detail exactly what you have to do to apply a hotfix, depending where the implementation is up to.
I am installing R14 as a new Project
No action required.
Hotfixes are always absorbed into the release from the date updated onwards, you can proceed with running the merge program and follow the installation instructions as normal, all hotfixes will be included.
I have ran the merge program and downloaded R14, but not yet installed it
You're advised to just delete the files the merge program has downloaded and re-run it.
It will download the files plus the hotfix content for you and you'll be ready to go as if installing as a new project.
I have installed R14 already and want to apply the Hotfixes
Both the Core and Integration components have received the hotfixes as detailed in the above tables, so to benefit from them, they both require the following activity.
NOTE: Downtime will be required as whilst the hotfix is applied, the system will be un-available.
Click
here to download the R14 distribution componenents and un-compress to a temporary location.
For the following scenario, we will assume it's been installed to C:\V1 and downloaded to C:\TEMP\R14DISTRIB, change as appropriate to your installation.
When the following procedures have been completed your system will be brought up to the equivalent version as if installed as a new Project.
They are at a relatively high level assuming a good understanding of Windows, service management and the cmdline, none the less
follow very carefully, step by step, and you shouldn't get any problems.
V1 Core Components
The hotfixes only apply to the following components, if they have not been implemented, no action is required.
SmartMail
1. From the C:\TEMP\R14DISTRIB\SmartSuite directroy, run the SmartMailInstaller.MSi
2. It will detect the existing installation, run over the top and your previous settings will be preserved.
V1 Integration Components
If you have made any bespoke changes to the integration since the original implementation, they must be manually retro-fitted back in to the following procedures.
The hotfixes only apply to the following components, if they have not been implemented, no action is required.
EDD
1. Stop the EDM Print Management Service
2. From the C:\TEMP\R14DISTRIB\EDMPRINTMANAGEMENT dir, take a copy of Print_Pickup.def
3. In C:\V1\EDMPRINTMANAGEMENT, take backup of Print_Pickup.def calling it Print_Pickup.def.prehotfix
4. Paste in place the new Print_Pickup.def
5. Start the EDM Print Management Service
EDM
No Action required.
PIA with DbCapture
No Action required.
Sage Patches
EDM
1. Using the Install the Server Components instructions as a guide, re-apply the C:\TEMP\R14DISTRIB\PATCH\EDM\PROD_ENDPOINT\X3EDM_0140000_60_000.dat patch to your production Endpoint(s)
PIA with DbCapture
1. Using the Install the Server Components instructions as a guide, re-apply the C:\TEMP\R14DISTRIB\PATCH\PIA\PROD_ENDPOINT\XV1PIA_0140000_60_000.dat patch to your production Endpoint(s)
NOTE: You may receive a warning regarding 'incorrect file structure', this is not serious and can be ignored, in some circmestances, Sage will just attempt to re-apply the OCR entry transaction.
Final Recommended Step
Using the Troubleshooting chapters as a guide, tick off each section which is a good way to check the Hotfix has been applied successfully, if so, this completes the procedure.