...
SetLoyaltyIncart returns the coupon information for the cart with in the new field "Type" to indicate what type of coupon it is. Possible returned values are: Unknown, CouponId, CustomerId, Bonus, BonusReward, BonusAmount, BonusCheck, StampCard, TenderCoupon.
RemoveItemFromCart should fail if the item is already removed
Removing item which is previously/already removed will fail with an error
Improved error handling for import of orders/sales
When the order/sale received by the BatchToPosApi package fails with an InvalidQuantityFault, CartItemNotFoundFault or CartIsCancelledFault - it no longer retries after the initial fail.
Error message regarding coupons improvement
When an invalid or expired coupon is added or used, proper error message is displayed.
Released 19.09.2024
Customer-specific transaction details in POS API
Structured notes for 'ExternalTypeCode', 'CountryCode', 'ExternalLineTypeCode', and 'TaxGroupID' are included in all EG POSLogs from the POS API. Even if a receipt is converted to a lower POSLog version that doesn't support these fields, the information is retained in the POSlog as long as the version supports structured notes. The structured notes correctly translate to ARTS extensions during conversion in ReceiptService, ensuring consistent handling of transaction data across different versions and sources.
| Expand | ||
|---|---|---|
| ||
|
Update in fault handling for invalid discounts
...
GeneralFault is returned for scenarios wherein an invalid discount is added to cart (ItemSale/SetCartItemDiscount endpoint). This replaces InvalidDiscountFault since it is not in the list of possible faults in the contract.
Improved error handling for import of orders/sales
When the order/sale received by the BatchToPosApi package fails with an InvalidQuantityFault, CartItemNotFoundFault or CartIsCancelledFault - it no longer retries after the initial fail.
Error message regarding coupons improvement
When an invalid or expired coupon is added or used, proper error message is displayed.
InvalidCastException in POSAPI resulting in 500 error code
...
We're encountering an Invalid Cast Exception on certain endpoints related to POSLog, which is causing the POS API to return a 500 error. This issue has been resolved by updating the error code to 400 and providing a valid failure message.
RemoveItemFromCart should fail if the item is already removed
Removing item which is previously/already removed will fail with an error
...
Released 05.09.2024
Post-registration of members through NewCartForTransactions
...