Hotfix 0002 (TBD)
New Enhancement List
Closed Issues List
- Fixed the Promotion Builder being unavailable in Promotion Studio after upgrading to 2026.2. The builder buttons were greyed out with "You do not have access right to this screen" for every user group, and the right could not be set in Setup User Group, because the upgrade had not created it. The hotfix creates the right and grants it to all existing user groups. It also restores the Validate now, Acknowledge, Exclude item and Remove item buttons in Items & overlaps. Users need to close and reopen Promotion Studio once after applying the hotfix. (Ticket: 180166)
Hotfix 0001 (14/09/2026)
New Enhancement List
- Database upgrade progress screen – the database upgrade that runs at login now reports on the DynaMod start-up screen instead of a small pop-up window whose caption did not fit. The screen shows the version being upgraded to, which upgrade script is running out of how many, a progress bar with the batch count (for example “Batch 1,240 of 14,442”), the object currently being created and the elapsed time, so a long upgrade on a large database no longer looks frozen.
- Reconnect after a Server Socket restart – when the Server Socket is restarted while DynaMod is open, DynaMod now shows a single “Disconnected from Server” dialog. Pressing Reconnect signs the session back in and the operation that was interrupted (a query, a save or a posting) continues on the new session.
- Added StockID column into the TikTok sync quantity screen (Ticket: 179950)
- Added StockTransactionTypeControl screen to system menu
Closed Issues List
- Fixed SEP QR Private Key missing become 'fJAsAg3UtTU='.
- Fixed error 1934 “DELETE failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'” when posting (reported on Goods Receive Note posting after upgrading to 2026.2). During a database upgrade run from DynaMod, a stored procedure could be created with the wrong QUOTED_IDENTIFIER setting when the Server Socket was serving other connections at the same time; the procedure then failed the first time it touched a table with a filtered index. The upgrade now carries the correct settings with every statement it runs, and this hotfix re-creates the affected posting procedure, so sites already showing the error are repaired by applying the hotfix. A support script is available to check a database for other procedures created with the wrong setting.
- Fixed dozens of stacked “Disconnected from Server. Please retry” dialogs after the Server Socket was restarted while DynaMod was open. Every background refresh (unread messages, licensed-user count and others) opened its own dialog on top of the previous one, each with its own Reconnect button taking a licence session. Only one dialog is shown now; background refreshes wait for it and continue after Reconnect.
- Fixed an occasional “Object reference not set to an instance of an object” error box on the Server Socket when it starts up while clients are reconnecting (its configuration file was being read by two threads at the same time). Server Socket component; the DynaMod fixes above do not require the Server Socket to be updated.
- Fixed DynaMod refusing to log in after a database upgrade with the message “The upgrade script … is not run”, even though the upgrade had completed. This happened when another PC opened DynaMod while the upgrade was still running. DynaMod now records the completed upgrade correctly and recognises an already-upgraded database at the next login, so no manual fix by support is needed.
- Fixed missing fetch trade account no when importing multi-document for supplier invoice (Ticket: 179670)
- Fixed missing fetch E-Invoice mandatory fields when importing multi-document (Ticket: 179847)
- Fixed an occasional “Object reference not set to an instance of an object” error on the DynaMod Server Socket when it starts up while DynaMod clients are reconnecting. Requires DynaMod Server Socket 2026.2 Build 0001. The other fixes in this hotfix are in DynaMod itself and work with the existing Server Socket.
- Fixed Stock Department not clearing on purchasing documents when the supplier is not under Supplier Stock Department Control.
- Fixed transaction detail level stock balance location did not retrieve correctly.