Form Studio and Agility 360 Printer Definition can Display Duplicate Document Names
Form Studio and Agility 360 display duplicate documents under the Printer Definition when a document is referenced in multiple times in the Form’s definition. Setting the printer on one, sets it on all duplicated documents.
SAP User setup - Remove requirement to add SAP password when creating WiSys user.
Enhancements have been made to simplify SAP user configuration and password management within WiSys.,When creating a new WiSys user, the system no longer requires entry of the SAP password during setup. Additionally, the password change process has been updated so that users are no longer prompted to enter their previous password when setting a new one.
Production Issue Preload is storing incorrect BaseLine Data
Fixed a regression issue where Production Issue Preload stored incorrect BaseLine data, introduced while adding support for AR Returns without a base document using SAPDocument.v6.0.dll. The logic was corrected and validated for both Production Issue and AR Return scenarios with no base document
Intermittent application crashes caused by COM object disposal in Wisys.SapInventory
Code was added to ,Wisys.SAPInventory.cStockTransferBatch.Dispose(), to address a COM memory leak. SAP Business One inconsistently disposes its COM objects, and in some cases disposes the ,Lines, object before our code attempts to clean it up.,This results in a ,System.AccessViolationException, at ,SAPbobsCOM.IStockTransfer.get_Lines(),, causing a hard crash with no user-facing error.,Impact,Mitigation,The added disposal code has been removed to restore stability.,Next Steps,Plan a refactor to safely manage SAP COM object lifecycles and resolve memory leak concerns without triggering access violations.
SQL Editor in Design Studio Will not format any SQL Query nor return data
I,ssue:,The SQL Editor in SAP HANA Design Studio was not formatting SQL queries, returning data, or allowing queries to be saved. In certain scenarios, queries were unintentionally erased or overwritten during validation.,Root Cause:,When a component contained an invalid SQL query, the Query Builder could erase the existing query during validation. In other cases, the editor would overwrite the current query with the last known “good” query, even if that query was blank. The system also did not provide clear error feedback to the user.,Resolution:,The validation process has been corrected so that invalid saved SQL no longer causes the Query Builder to erase existing queries. The editor will no longer overwrite the current query with the last known good query when a validation error occurs. Clear popup error messages are now displayed to inform users of SQL validation issues. In some cases, actions that trigger validation, such as proceeding to the next step, may be prevented until the
FedEx Collect Payment Type should not require a consignee account number
Previously, Agility Shipping incorrectly required users to enter a ,consignee account number, when selecting the ,FedEx Collect, payment type. This behavior did not align with FedEx’s Collect billing rules and caused unnecessary validation errors during shipment processing.
Sales Return Request Batch Lookup has a syntax error in HANA environments
HANA users were encountering a SQL syntax error when using the Batch field lookup because the query was empty. A valid query has now been added to return available batch numbers, allowing users to successfully select a batch number.
HANA syntax errors when using the Kit Delivery form
When executing the ,Kit Delivery, form from ,Sales Order Delivery,, users previously encountered ,SAP HANA syntax errors, due to incompatible SQL statements. The underlying queries have been refactored for full ,HANA and SQL Server compatibility,, resolving these errors.
Sales BOM Components in SO Delivery not relieved from the Sales Order warehouse
Previously, when creating a delivery from a ,Sales Order, containing a ,Sales BOM, using the ,SO Delivery (Kit Delivery), form, inventory for component items was incorrectly relieved from the ,parent item’s warehouse, instead of the ,component warehouse, defined on the sales order line.,This behavior has been corrected — inventory is now properly relieved from the ,component’s designated warehouse, on the sales order
SAP Document Preload Issues when No Base Document
The SAP Preload method was not correctly determining whether a header or line record already existed, which caused updates to occur when new records should have been inserted. The underlying queries have been updated to accurately detect record existence and properly handle all scenarios to ensure correct insert/update behavior.
Added 64-Bit Compatibility for Agility Product Suite
Agility Products have been updated to support 64-bit architecture. This upgrade enhances performance, stability, and compatibility with modern operating systems and environments. It also enables larger memory utilization for improved scalability and prepares the platform for future enhancements.
Im PickList Add Preload Object Requires passing Batch/serial or Bin number
When using the IM PickList Add Preload object, users were receiving a SQL error when the item was not batched. This SQL syntax error has been resolved to allow non batched items to be selected in the pick list creation process.
Package Transfer - SAP DiAPI Object Cleanup
Resolved an issue where SAP Business One DI API objects were not being properly released during a package transfer transaction. The cleanup process has been improved to ensure all SAP B1 objects are properly disposed of, reducing memory usage and preventing potential connection locking.
SAP Document SAP DiAPI Object Cleanup
Resolved an issue where SAP Business One DI API objects were not being properly released after document transactions. The cleanup process has been improved to ensure all SAP B1 objects are properly disposed of, reducing memory usage and preventing potential connection locking.
Agility Shipping FedEx International Broker Country Code error when no broker
When shipping internationally with FedEx, some users received an error BROKER.COUNTRY.INVALID if no broker information was provided. This has been corrected so that blank broker requests are no longer sent to the FedEx API.
Serial number preload fails with incorrect error when Unique By setting is not a supported setting.
Previously, when the ,Unique Serial Numbers By, setting was not configured to a supported ,Serial Numbers, option, users received an unclear error message referencing ,SAPGetDataTable,. This message has been updated to clearly indicate that the selected serial number setting is not supported.