What's new in Lime CRM Desktop Client 11.3 for customers upgrading from 11.2

Product

Lime CRM Desktop Client

From version

11.2.3960

To version

11.3.4747

Date

2026-10-15

Platform

Windows

This page is for IT administrators and customers who plan the upgrade from Lime CRM Desktop Client 11.2 to 11.3. It compares 11.2.3960, the 11.2 build that most on-premise customers run, with 11.3.4747. It lists what changes for users and administrators, what to check before the upgrade and what to test after it. Version 11.3.4747 is the final feature release of 11.3. Later 11.3 builds contain only corrections. New features are added in the next version. The earlier page “What's New in Lime CRM Desktop 11.3” compared 11.3 with an older 11.2 build. Many items on that page are already in 11.2.3960, so this page does not repeat them. The full detail for each release is in the release notes of each 11.3 version, for example 11.3.4362, 11.3.4483 and 11.3.4747.

• Security hardening of the update service and the installer. The Lime Maintenance Service, which installs client updates, and the installer are hardened. Lime recommends that all computers with the client are updated to 11.3.4747.

• Works with Smart App Control. Every program and library that the installer delivers is signed by Lime Technologies. Smart App Control in Windows 11 no longer blocks the client or parts of it.

• Document locking is active again. When you edit a document, a colleague who opens it gets a read-only copy. Locked documents can be found and released from the client.

• Documents that could not be saved to Lime CRM are reported and can be recovered. The new dialog Tools > Unsent documents… lets you retry the save, save a copy or discard the local changes.

• New inspector layout. A splitter separates the fields from the tabs. Multi-line fields such as notes grow and shrink with their content.

• Better search in relation fields. The dropdown shows how many records match and where they come from. You can find a record by its id and choose the order of search results per record type.

• Safer opening of links and files. The client blocks known dangerous link types and asks before it opens a file that Windows considers unsafe.

• Filter validation report and many filter corrections. A new report shows how a filter is rewritten and how many records each step returns. Many cases where a filter returned wrong records are corrected.

This section lists changes that administrators need to know before the upgrade. Read it before you plan the rollout.

• The installer no longer installs the Visual C++ redistributable. The client does not need it as a separate installation. An update can therefore no longer stall when Teams, OneDrive or Office hold the runtime files.

• The VBA setup installs everything VBA needs. The VBA setup (setupVBA) installs the Visual C++ 2010 runtime that VBA needs. It also installs and registers the VB6 controls, license keys and compatibility entries that VBA forms use. These were part of the main installer in 11.2. The VBA setup repairs the VBA installation each time it runs.

• All installed files are signed. The installer, its packages, the setup programs it runs and the files it installs are signed by Lime Technologies and timestamped. Files that already have a valid signature from their vendor keep it. This makes the client work with Smart App Control in Windows 11.

• Updates never restart the computer. When a component needs a restart, the restart is completed at the next normal restart of the computer.

• The Lime Maintenance Service starts only unattended installations. The service passes on only the unattended switches /passive, /quiet, /silent and /verysilent, and also /repair, /suppressmsgboxes, /norestart and LaunchLime. Other arguments are removed and recorded in the log. A request without an unattended switch is refused. Review deployment scripts that start installers through the service.

• The Lime Maintenance Service refuses installers with an old installer engine. An installer package built with WiX older than 3.14.1 is refused. Setup programs that are not WiX bundles, such as the VBA setup, are not affected. Automatic updates to an older build that uses an older engine can therefore be refused.

• The Lime Maintenance Service writes to the Windows event log. Requests, refused requests and started installers are recorded in the Application log. The source is LimeMaintenanceService and the events are 1000 to 1003.

• A separate update package exists for the Lime Maintenance Service. setupMaintenanceService.exe updates only the service and leaves the client unchanged. It is for computers that cannot install the full 11.3.4747 client yet. A user without administrator rights can start it, and it runs through the installed service or asks for elevation. If it cannot upgrade an older service, it stops and disables that service and exits with code 2. Automatic updates do not work while the service is disabled. The state is recorded under HKLM\SOFTWARE\Lime\MaintenanceServiceUpdate.

• Running Lime is closed in a controlled way during an update. The installation asks Lime to close through the Windows Restart Manager. A manual installation lists the running applications and asks first. An automatic update closes them without a question. The setup variable ForceClose set to 1 ends a Lime that does not close when asked.

• Automatic updates work where installation rollback is turned off by policy. The right to start and stop the Lime Maintenance Service is now part of the normal service installation.

• Setup logs have a new location. When setup programs run with administrator rights, they write their logs under %WINDIR%\Logs\Lime. Without administrator rights, the logs stay under %ProgramData%\Lime\Setup.

• The WebView2 runtime is checked by version. The installer checks the installed version of the Microsoft WebView2 runtime. A runtime that was removed is installed again.

• Documents are locked while they are edited. 11.2.3960 did not lock documents during editing, so two users could overwrite each other's changes. In 11.3.4747, a colleague who opens a document that you edit gets it read-only. Teams that want several people to edit the same document at the same time can turn locking off with the NoLock setting. Set NoLock to 1 under Application\FileExtensions\*.* for all file types, or under Application\FileExtensions\<extension> for one type.

• Empty fields are no longer dimmed by default. In 11.2.3960, dimming of empty fields was on by default. In 11.3.4747 it is off for users who never saved the setting. Users who saved the setting keep their choice. The option is under Options > Misc.

• Cards include the filters and views of the related record type. The filter and view lists in an inspector tab now also contain the filters and views of the related record type. Two new options in Options > Misc turn this off per database: “Include class filters on cards” and “Include class views on cards”. A change takes effect at the next start.

• A list refresh runs the full query. 11.2.3960 used a refresh based on timestamps in some cases. That refresh caused unexpected load on the server and is turned off. A refresh now runs the full query.

• QueryTimeout limits the total waiting time. The timeout of a filter now includes the time a query waits in the client queue, not only the time on the server. When the time ends before the query leaves the client, the user sees a message that says so.

• Automatically generated option queries time out after 1 second. Before, the limit was 10 seconds. Option queries that are written by hand keep the 10-second limit.

• Links and files are opened through a security check. Application.Shell and the other places that open links and files block dangerous link types, such as ms-msdt, and the runas verb. Normal web, mail, telephone, Teams, Slack and document management links are not affected. For a file that Windows considers unsafe, the client asks for confirmation. Without a user interface, for example in an unattended automation, such a file is blocked. Administrators can change the behaviour per computer under HKLM\Software\Lundalogik\Lime\Security with ShellGateHardBlock, ShellSchemeAllowList, ShellSchemeBlockList, ShellVerbAllowList and ShellVerbBlockList.

• Message boxes follow Application.DisplayAlerts. Message boxes from the standard VB6 and .NET add-ins, and alert() messages from pages in action pads and web bars, are now shown through the client. An unattended run therefore no longer stops at a dialog that nobody can close. The Template Manager uses the standard error dialog. Its button that sent the error by e-mail is removed.

• limecrm: links use UTF-8. The client decodes limecrm: links as UTF-8 and creates links as UTF-8 with percent-encoding. Swedish letters and other non-English characters from call center integrations are now correct. For an integration that still sends links in the local code page, set UrlEncoding\UseLegacyCodePage to 1.

• Login tries a secure connection first. When a secure (https) connection to a server on a non-standard port fails, the client asks before it uses unencrypted http. The answer is remembered per server. While the connection is unencrypted, the login dialog shows a red footer and a warning icon.

• Each solution has its own integrated browser profile. Each combination of server, database and user has its own browser profile. A session cookie from one solution is no longer used in another.

• Automation cannot replace a document that has unsent changes. When a script sets a document field to another document while the current document is checked out and edited, the client refuses the change with a message. A script that wants to discard the edits needs to check in the document with “abandon changes” first.

• The embedded web client is opt-in. Records can be opened in the embedded web client instead of the inspector. This is off by default. AllowWebClient (“Use embedded web client for access to new features”) and PreferWebClient (“Prefer web client for cards if configured”) are read from database scope. Values stored per Windows user by earlier 11.3 builds are ignored. Each record type can also be controlled with the tags allowWebClient and preferWebClient.

• One setting turns all web client features off. Application\IntegrateWebClient (DWORD, 1 = enabled, 0 = disabled) controls all web client features, including menu entries and the VBA functions. It replaces the 11.2 settings ShowEmeddedWebClient and SearchUsingWebClient, which are no longer read.

• The quick search mode setting has a new name. The text setting that selects the quick search method (Elastic, Jepardy, BeginsWith or SqlFullText) is now named QuickSearchMode. In 11.2 it was named SearchMode. Rename the setting if your solution uses it.

• The search bar on cards is opt-in. The search bar shows on inspector cards only when “Show super search on cards” (EnableInspectorFullTextSearch) is selected in Options > Misc. Global search runs only when the server has full-text search enabled. Users can hide the search bar with View > Bars > Search bar.

• Administrators can hide individual options. Settings under Application\Options\HiddenSettings hide single controls on the Misc and Explorers options pages. Each value is a DWORD where 1 hides the control. Administrators always see all controls. The release notes of 11.3.4362 list the available names.

• Relevance scoring for relation search is available and off by default. The option “Use relevance scoring for searching relations” in Options > Misc is stored per user.

Pay extra attention to these areas when you validate the upgrade:

• Filters. The filter engine has many changes in NULL handling, “not in” conditions, sub-filters, multi-link relations and query optimisation. Check important saved filters, especially filters with sub-filters and negated conditions. The filter validation report helps to compare the expected and the actual result.

• Inspector layout. Check cards with many fields, multi-line notes, hidden sections and custom layouts. Check that the splitter between fields and tabs starts in a usable position.

• Relation fields. Check search, autocomplete and option lists in relation fields, especially fields with option queries that depend on other fields.

• Document handling. Check that documents lock and unlock as expected, that check-in works and that the Unsent documents dialog is empty in normal use.

• Custom VBA and add-ins. Check customizations that use Application.Shell, show message boxes, run unattended, save records in BeforeSave or AfterSave, or copy records with Record.Copy. Check old VBA forms that use VB6 controls.

• Action pads and web bars. Check that action pads show the correct values and that VBA calls from an action pad act on the correct card.

• Embedded web client. If you turn it on, check the settings above and the pages that open in it.

• Login. Check single sign-on, the database selection dialog and servers that use http or a non-standard port.

• Deployment. Check automatic updates through the Lime Maintenance Service, installations where Lime or Office is running, computers with Smart App Control, and scripts that pass arguments to the installer.

• Splitter between fields and tabs. A splitter separates the fields from the tabs on a card. You can drag it, and its position is remembered per inspector layout. Double-click toggles between maximised tabs and the previous position. The Fields tab keeps its state when you move between records.

• Field layout with variable heights. Multi-line fields such as notes, history and description grow and shrink with their content. A multi-line field at the bottom fills the remaining space. When space is small, it keeps at least three lines. Rows that mix a multi-line field with single-line fields no longer leave empty space.

• Clearer pane dividers. Each divider shows a grip that follows the pointer and highlights when the pointer is over it. The tab strip of a card shows the resize cursor where it can resize the pane below it.

• New entries in the tab menu. The tab menu has the new entries “Close other tabs” and “Open in WebClient”. The second entry shows only when the web client is enabled.

• Open your own record from the Tools menu. The entry “Edit current” followed by your record type opens your own user record. If it is already open, it is brought to the front.

• Multi-value option fields work with the keyboard. Arrow keys, Home, End, Page Up and Page Down move the highlight, and Space checks or unchecks an option. Typing jumps to the first matching option. A single click now toggles exactly one option.

• Translated placeholder texts. “[Click to edit]” and “[Type to filter]” are translated for all supported languages.

• Faster and clearer relation field search. The search waits briefly while you type, so fast typing does not start one search per key. It suggests the longest common start of the matching values. Matches at the start of a value are listed before matches inside a value. Lists that the search does not narrow are sorted in natural order, so “File 2” comes before “File 10”.

• Match count and result source in the dropdown. A footer shows how many records match and whether the results come from the option list, the local cache or the server. Shift+Enter searches the server when the cache has no match. Ctrl+Enter ignores the cache and searches the server.

• Menu on dropdown rows. Right-click on a row offers Select, Cancel, Open in desktop and Open in web client. Middle-click opens the record without changing the link. Tab on “No matches” cancels and does not link a hidden row.

• Find a record by its id. Typing a record id pins that record at the top of the dropdown. When two visible rows have the same description, each row shows its id.

• More shortcuts in the field menu. The “Recent” shortcut is also available on option fields. The menu lists values from all relations on your own user record that point to the field's target. A record is never offered as a link to itself. Right-click on a field always opens this menu.

• Option fields offer only valid values. A field limited to a fixed list of options no longer shows “Search…” or “New…”. A relation that is narrowed by an option query keeps them, and its search applies the option query.

• Search settings dialog. The dialog is renamed “Search settings”. You can choose the sort order of search results for each record type, or keep the order of the view. Each list offers “New…” and an edit button to create or change views and filters. The “[Search]” entry creates a view for search results.

• Smaller search corrections. Relation search for a record type that points to its own type no longer filters candidates through coworker relations. Numeric search no longer matches Yes/No fields.

• Filter validation report. The command “Validate filter…” shows the filter as written, the filter after optimisation and the number of records at each step. It marks conditions that remove each other, such as two “not in” conditions joined with OR. It also checks negated conditions by a second, independent method.

• Copy a filter as text or XML. In the filter dialogs, Ctrl+C copies a readable summary of the filter and Ctrl+Shift+C copies the full XML. The same commands are in the menu.

• Extended column filters. The filter dialog supports linked records and pools. Hold Shift when you open a column filter to include fields that are not visible. A column filter loads the list again from the server, which reduces the risk of old data.

• Cache for nested filters. The advanced settings of a filter have the new setting “Cache nested filter at most (seconds)”.

• Faster formula favorites. The favorites menu for formulas in the filter dialog is built in the background. It no longer freezes the client in solutions with many filters.

• Faster filter queries. Some filter patterns now produce SQL that can use database indexes.

• Clearer error when a view cannot load. When the database refuses the query of a view, the message names the field and its expression. It suggests a way to load the view at once.

• “Reload list after update” in Mass update. A new checkbox, on by default, loads the list again when the mass update is complete.

• Filter corrections. Many filter results are corrected. The corrections cover “not in” conditions, multi-link relations, repeated sub-filters and filters that refer to themselves. They also cover decimal values, renamed or removed option values, values in another language and counts over to-many relations. Conditions that use your own user record follow changes to it. See the release notes of 11.3.4362, 11.3.4483 and 11.3.4747 for the full list.

• Find and release locked documents. Each record type with a document field has filters for locked documents. “Locked - mine” is available to all users. “Locked - all” and “Locked - stale” are available to administrators. You can release your own lock from the Document menu. An administrator can release the lock of another user after a confirmation.

• Locks stay active and old locks are released. While you edit a document, the client confirms the lock to the server at regular intervals. At login and at exit, it releases your own locks that have no local copy. Saving the record no longer releases the lock on a document that you edit.

• Unsent documents dialog. The client records each document that could not be saved to Lime CRM. A notification appears after login and at exit. Tools > Unsent documents… lists these documents with the state and the reason. You can open the document or its folder, save a copy, retry, discard the local changes or, as an administrator, replace the version on the server. Application\UnsentDocumentsScanDelay sets the delay before the first check after login (default 20 seconds).

• Save selected documents. “Save selected documents…” saves the documents of the selected records to a folder. The work runs in the background and can be cancelled. Users who are not administrators can save at most 25 documents at a time. The command follows the policy that turns off export.

• Clear message when a document opens read-only because of its size. The message says that changes cannot be saved to Lime CRM and states the size when it is known.

• Outlook Redemption 6.8. The Outlook integration uses Outlook Redemption 6.8. It corrects intermittent sign-in errors against Exchange Online and no longer writes passwords or tokens to its log.

• Document corrections. “Save as…” works under a strict Windows attachment policy. File names no longer repeat the extension. Lock and unlock no longer make a document impossible to open. Closing the database no longer becomes slower over time. A maximum document size published in an unexpected format no longer blocks every check-in.

• Faster cards with web-based action pads. Cards share the browser engine, so the second and later cards open faster. The browser starts at the same time as the record loads. The action pane appears in one step instead of row by row.

• Action pads recover without a restart. The client detects a browser process that does not respond, ends it and loads the page again. The web bar refreshes even when a busy pointer stays set.

• Action pad VBA calls act on their own card. A VBA call from an action pad runs against the card that the action pad belongs to. Values from VBA functions during data binding are correct.

• Clear errors from the browser engine. When the engine does not start within ten seconds, the client reports the likely cause. Engine processes are closed in order when Lime exits.

• Embedded web client. When it is enabled, records can open in the embedded web client, and menus offer “Open in web client”. See “Before you upgrade” for the settings.

• Priority for asynchronous VBA work. Work started by a click runs before background work. Application.RunEx accepts an optional priority argument. Positive values mean foreground, 0 is normal, negative values mean background and -10 or lower means idle. Existing scripts use normal priority.

• Description format per record type. IClass::DescriptionFormat sets an expression that controls Record.Description for a record type, for example [firstname] & “ ” & [lastname]. When the expression returns an empty string, the normal description is used.

• Readable filter descriptions. IFilter::BuildDescription returns a readable summary or formatted XML of a filter.

• SVG icons. Class.ImportIcon can import icons from SVG files, with an optional color.

• Old VBA forms load again. VBA forms that refer to old ActiveX control ids now load. The client replaces these ids when the VBA project loads. The change is saved the next time the VBA project is saved.

• VBScript dialogs are modal. InputBox and MsgBox from VBScript block the main window. This prevents crashes from input behind the dialog.

• Clearer errors for refused updates. When the server refuses an update because of access rights, the error names the record type and the access rules that apply.

• Loading records. Loading a record by id reports the record type and id when two rows have the same id. Opening a record through a filter that matches several records returns the first match.

• Automation corrections. BeforeSave and AfterSave handlers that write to the record or refresh controls no longer make the client hang. Record.Copy and Record.CopyTo no longer move or duplicate related records and copy fields named like system columns. Explorer.Class no longer returns an error when the list is empty.

• Database selection without freezes. The dialog connects in the background and waits until you have entered the server and port. A pasted server address keeps its protocol and can include a database= parameter.

• Login dialog corrections. The dialog checks the server again when the network connection returns. It shows the correct login form after you change the server. During web sign-in, it keeps showing which server and database you sign in to.

• Better handling of server overload. Clients wait different, random times before they try again. A “Retry-After” answer is limited to two minutes. Server errors (5xx) that were not handled before are now retried.

• Clear messages for gateway errors. For 502 and 503, the message says that the server is not available. For 504, it says that the server did not answer in time and asks you to check the result before you try again.

• Diagnostic output for single sign-on. For Microsoft Entra ID conditional access cases, the client writes the device and runtime details to the Windows debug output. No user name or e-mail address is written.

• The installer shows its version. Every page shows the version and the build date. The first and the last page link to the release notes of that version.

• “Check for updates” can offer the released build. A manual check also looks at the build on the official download page, up to the version that your administrator allows. Automatic background checks are unchanged.

• Clearer manual installation. When Lime or an Office application with a Lime add-in is running, the setup lists the applications and asks you to close them. The old Abort, Retry, Ignore box is removed.

• Lime starts after the whole update is complete. After an automatic update, Lime starts when all components, including VBA, are installed. It comes to the front unless you have moved to another window.

• Better reports of failed installations. A failed installation report names the package, its result code and the version it replaced, and it includes the setup logs.

• Updated third-party components. log4net 3.5.0, NodaTime 3.3.5, TimeZoneConverter 8.0.0, WebView2 SDK 1.0.4258.31 and sentry-native 0.17.3.

• Update service and installer. See “Installation and the update service” above.

• Opening links and files. See the item about Application.Shell in “Changed behaviour and changed defaults” above.

• Safer content in action pads. Content from CRM customizations is cleaned before it is shown in more places. Integration links and custom address schemes still work.

• Faster start. Solutions with many VBA references start faster. Options are loaded in background threads.

• Fewer freezes. The client no longer stops responding because of record locks between operations or a large favorites cache. The database selection dialog no longer freezes. A progress dialog no longer stays open after the work is complete.

• Fewer crashes. Crashes are corrected when tabs are closed or dragged, and when you switch away with a field dropdown open. Lime no longer crashes at Windows sign-out after the VBA editor was used. Several limecrm: links that arrive at the same time no longer cause a crash. Exit with Outlook integration is more stable. A background operation can no longer damage memory while its progress window updates.

• Other corrections. The mouse pointer no longer disappears over Lime windows. Lime keeps running when a Windows logoff or shutdown is cancelled. A mail from a template and a duplicated card contain the values that are on screen, also when they are not saved. Error messages name the real source location and the limecrm: link that failed. The release notes of each 11.3 version list all corrections.