------------------------------------------------------------------------ pset2025_4: # 91536 (BDUX90342): when using select * or select table.* do not where use columns Date: Tue, 20 Jan 2026 15:33:53 +0100 Created on: pset2025_4 Type: bugfix _Problem Description (Customer terms)_ Not able to delete CDF fields anymore since Enhancement "Extension usage check for customer defined fields before deletion" got active New 2025.10 Enhancement "Extension usage check for customer defined fields before deletion" implementation prevents plausible CDF delete actions. A CDF not being explicitly referred to in the program script source code of an own tx session should be allowed getting deleted. _Test Procedure_ Regtests _Affected Executables_ bic6.2 _Motive source_ JIRA:LNW-23295 ------------------------------------------------------------------------ pset2025_4: # 91463 (BDUX90232): LNW-23638: error 522 not passed to the bshell correctly Date: Wed, 10 Dec 2025 13:47:24 +0100 Created on: pset2025_3 Type: bugfix _Problem Description (Customer terms)_ Starting in the last hour, we have had users notifying us in all manufacturing and production departments that they are unable to use Mobile Scanning or Shop Floor due to the following error that occurs when they try to complete any inventory transaction like reporting or shipping. We have asked them to clear their history and cache for all time which sometimes temporarily works but is not permanent. This is critically affecting our ability to report. Error message: "ResourceException during doBdeCall" _Workaround_ Kill the bshell manually _Test Procedure_ N.A. error was not reproducible, also error IMC06 was not reproducible to test this situation _Affected Executables_ msql driver _Motive source_ CustomDefect:LNW-23638 ------------------------------------------------------------------------ pset2025_4: # 91403 (BDUX90143): CGP commit.transaction numbers are rolled up incorrectly Date: Fri, 14 Nov 2025 14:00:27 +0100 Created on: pset2025_4 Type: bugfix _Problem Description (Customer terms)_ commit.transaction show only database server abort when using staging is used when running with the Call Graph Profiler _Affected Executables_ bshell6.2 ------------------------------------------------------------------------ pset2025_4: # 91387 (BDUX90063): LNW-19553: Update rest service header key. Date: Wed, 12 Nov 2025 08:29:25 +0100 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ PIs defined in REST Service Management ttmtm6620m000 can be called by any company. _Affected Executables_ bshell _Motive source_ JIRA:LNW-19553 ------------------------------------------------------------------------ pset2025_4: # 91310 (BDUX90070): LNW-23075: libcurl functon was giving bad argument, buffer size to small Date: Tue, 21 Oct 2025 14:38:03 +0200 Created on: pset2025_3 Type: bugfix _Problem Description (Customer terms)_ Users attempting to refresh or retrieve a new access token by clicking the Get new access token button within the OAuth 2.0 parameter sets. Session are encountering the following error message: A libcurl function was gien a bad argument _Affected Executables_ bshell _Motive source_ CustomDefect:LNW-23075 ------------------------------------------------------------------------ pset2025_4: # 91273 (BDUX89772): LNW-18690: Remove invalid dd file. Date: Thu, 09 Oct 2025 13:12:57 +0200 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ bdbpost importing a bigdump should not create missing runtime table DD files as it could cause "error 513" _Workaround_ N/A _Test Procedure_ Import new dd with corrupted data. After the error, reimport the same dd after fixing the corruption. _Affected Executables_ bdbpost _Motive source_ JIRA:LNW-18690 ------------------------------------------------------------------------ pset2025_4: # 91254 (BDUX90017): DBS log Plan enablement issue due to limited connection string buffer. Date: Mon, 06 Oct 2025 16:26:49 +0200 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ Bshell fails to start if -set DBSLOG=04 is enabled to get the execution plan. _Workaround_ N/A _Test Procedure_ Sporadic issue - Starting bshell with DBSLOG=04 enabled reproduces the scenario. _Affected Executables_ bshell ------------------------------------------------------------------------