Bug fixes in Release 10.0.44.68 (July 2025) – Business Integration Solutions.
| Bug ID | Title |
|---|---|
| 216725 (CS00235689) | Incorrect SQL generation for GUID fields in document queries caused partial message processing |
| 221513 (CS00235815) | SQL trigger recreation did not validate existing state, causing incorrect or missing trigger updates |
| 217119 (CS0023815) | Recreating SQL triggers across multiple projects caused deadlocks and message failures |
| 220070 (CS00236786) | Records with 'ValidTo = Never' date excluded from SQL export using Direct SQL connector |
| 221796 / 221554 (CS00237389) | Azure Blob Storage connector failed in batch mode due to unsupported SDK constructor |
| 221971 | Clicking 'No' on SQL trigger confirmation dialog incorrectly completed the operation |
| 222057 (CS00237015 / CS00236979) | 10.0.43 issue with BIS project versions gives error and no descriptions |
| 220270 | NoExistsJoin causes SQL syntax error in ODBC document testing |
| 223928 | Azure Blob connector throws SAS credential conflict error during file upload |
| 211179 | BisEdiCheckAddressEanCode validation ignored customer account context |
| 215904 | Handler BisDocumentEdifactCounterTradaComm had incorrect naming and misleading description |
| 217349 | File Action history with records should not display when an export message is failing |
| 217396 | Cross-company filter in CustomQuery does not restrict child records based on root record range |
| 217982 | SQL trigger creation fails on BatchJob table due to reserved keyword |