pixi 22.08 is available from 2 August 2022. It includes several bug fixes, new features, enhancements and optimizations.
API
🟨 New Feature: A new API call was created: pixiGetInvoicePackageLines. It returns invoice package lines based on the provided filter parameters. This call can be used together with the new messaging event pixiEXShipOutStarted, which is sent when an invoice/box is scanned in pixi Web. (488172)
Parameters:
@PackageID
@InvocieID
@InvoiceNr
🟨 New Feature: A new API call was created: pixiReturnCaseUpdate. It can be used when a return is announced by a customer and the return costs need to be updated (Note: The API call can only update the costs before the credit is created! Only return costs of returns in status REC = received can be updated using this call). (631046)
Parameters:
@ReturnId
@ReturnCost
@UserName
🟨 New Feature: A new API call was created: pixiCanConvertBundle. The call is used to identify whether items can be converted to/from (result = 1) bundles or not (result = 0). The call returns the validated item/bundle in the field CanConvert. (634450)
Parameters:
@ItemKey
@ItemNrInt
@EAN
🟩 Bug fix: The bin group could not be set to an empty string via API call pixiBinUpdate. It can now be set to an empty value by sending an empty value in the <Group> tag. If the XML file does not contain a <Group> tag, the BinGroup value will not be updated. (642852)
🟩 Bug fix: The procedure behind API call pixiGetRemindersCA calculated and returned dates for reminders, although no reminders were sent. (643839)
🟩 Bug fix: The parameter @RowCount did not work for API call pixiGetInvoiceLinesExtended. (639037)
🟦 Optimization: The procedure behind the API call pixiGetChangedOrders was improved for better performance. (565200)
pixi Messaging
🟨 New Feature: A new messaging event was implemented: ShipOutStarted. By default, this messaging event is disabled. The message contains the following data: (472312)
invoiceKey
boxNr This data is sent only if a box or invoice is scanned for an invoice that was either created manually or automatically.
stationId The station ID of the shipping station where ship-out was done.
-
"1SS" This represents the invoice creation mode and can contain one of the following:
1SS
Direct
Manual
Automatic
When the messaging event is disabled (OFF) and the message is not sent, the ship-out is working as usual. When the message event is enabled (ON), the message is sent when Ship-Out in pixi Web is used. In Multiple Packages, the message is sent only when the box or invoice number is scanned. Additionally, if 1-Scan-Shipping Automatic Ship-Out is ON, the message will be sent at Scan-In. But if 1-Scan-Shipping Automatic Ship-Out: OFF then the message will be sent only at ship-out. The message event for ShipOutStarted is not sent when an error ocurrs and when the Shipping client is used. This messaging event can be used together with the new API call pixiInvoicePackageLines that returns information about package and invoice details.
pixi Mobile
Bin Info, Item Info
🟩 Bug fix: In the Bin Info program, the item code scanned last was not removed from the input field when Back was pressed. The code had to be removed manually, using the virtual keyboard. (650378)
Pick-to-box, Scan in (Assigning boxes)
🟪 Enhancement: The error messages for not assignable boxes were improved and enhanced. They will be displayed when either Add or Finish is pressed. The messages can contain the following: (549302)
The box does not exist.
The box is not empty.
The box is assigned to another picklist.
Web Application
Administration (Tags - New Order Tag Creation)
🟩 Bug fix: The tag type Orders could not be selected in the tag creation drop down menu. (660437)
Customer Service (Order Details Pages)
🟩 Bug fix: Editing customer addresses was not possible for orders that were partially shipped. (649851)
🟩 Bug fix: After columns that were not activated by default were selected and Apply was pressed, the columns were still not shown in the grid. (647541)
General
🟩 Bug fix: The icon (X) to close a multi-select drop-down menu was only visible when the cursor was placed on the position of the icon. (654270)
🟪 Enhancement: Enhanced logging was implemented and can be activated for direct invoice printing. (604589)
Items (Item Management - Suppliers Tab)
🟩 Bug fix: When the permission Tab: Suppliers was enabled for a user, the Suppliers tab was still not visible in the item details. (641741)
Logistics (Goods Receipt - Item Labels/Change of Time Received)
🟩 Bug fix: Item labels could not be created from goods receipts, because of a false request URL. (514502)
🟩 Bug fix: Editing and saving a goods receipt would change the time the order was received after saving. (651271)
Logistics (Picklists/Sequences)
🟪 Enhancement: Picklists can be created manually from sequences. This feature is available via Add > Select sequence, (437584)
🟩 Bug fix: After a new picklist sequence was created, the buttons Edit, Delete and Disable did not work when the picklist sequence was enabled. (660437)
Logistics (Scan-In - Box Ranges/Item Data Date Format)
🟩 Bug fix: The box range could not be changed for existing picklists and express boxes could not be included. Please note that the scan-in of orders without a shipping date is still not possible for express boxes. (636501)
🟩 Bug fix: The time was removed from the date/time field for best before dates. (659839)
Logistics (Ship-Out - (External) New Label Creation/Multiple Packages Overview)
🟩 Bug fix: New labels could not be created when an external provider was used. The issue has been resolved. Additionally, a timestamp functionality was implemented and the external label URL is deleted when a new label is created in pixi Web. (656903)
Known Issue: If a new label is created using an external service on shipping station 2, the shipping label will still be printed on shipping station 1 (where the label was created at ship-out).
🟩 Bug fix: When direct invoices were created in the Shipping client, and scanned in via pixi Web, the package overview was empty. (655869)
Desktop Applications
Connector (Import - Return Tracking IDs)
🟩 Bug fix: When tracking import files did not contain a return tracking ID, their import failed. (635496)
Control Center
Auto Emails/Mail Integration Service
🟩 Bug fix: The auto email type EIN was not available on all databases. (640521)
🟪 Enhancement: Enhanced logging was implemented for emails in status ERROR or in folder Not Sent e-mails. (611623)
Channel Settings (Amazon via DHL - Amazon Prime)
🟨 New Feature: There is a new Amazon Prime Shipping Label integration service that supports setting prime shipping operations via the channel settings to retrieve different shipping vendor offers for Amazon Prime orders. When DHL shipping methods should be set up for Amazon Prime shipping business, DHL needs to be selected on the Manage Shipping Services page the of Seller Central in the marketplace where the orders are placed. If DHL is not available, we recommend trying a different channel setting combination for: PrimeShippingOptionCarrierWillPickUp and PrimeShippingOptionDeliveryExperience. In a test case, PrimeShippingOptionCarrierWillPickUp set to false has returned positive results. (658422)
Amazon channel settings to set Prime Shipping Options when requesting the prime label:
-
PrimeShippingOptionCarrierWillPickUp
Values: true, false
Default: true
-
PrimeShippingOptionDeliveryExperience
Values: DeliveryConfirmationWithoutSignature, DeliveryConfirmationWithAdultSignature
Default: DeliveryConfirmationWithoutSignature
-
PrimeShippingOptionPrimeLabelFormat
Values: ZPL203 (pixi supports only this one!)
Default: ZPL203
-
Notes:
For DHL, the label was retrieved with PrimeShippingOptionCarrierWillPickUp, with both true and false. It depends on customer setup in the seller central. In this case, the DHL was selected on the Manage Shipping Services page of Seller Central in the marketplace that the orders are placed.
pixi will, if more providers are returned by Amazon, choose the cheapest provider.
Databases (Daily Jobs/EDD Calculation/Item Code Data Checks)
🟩 Bug fix: The daily restart of some services did not work. (645637)
🟩 Bug fix: In some cases, the estimated delivery date (EDD) could not be calculated and an error was returned. (647477)
🟦 Optimization: Data checks for item codes were optimized. (647525)
Item Export (XML Files/Plentymarkets 7)
🟩 Bug fix: The batch export of XML files that contained at least 1000 items failed. (650131)
🟩 Bug fix: An issue was resolved that prevented orders being imported from plentymarkets 7. (659362)
Customer Service (Invoices and Credits - Special Characters)
🟩 Bug fix: Invoices and credits could not be created when the name of a shipping vendor included a special character. (650498)
Payments (Swiss QR Codes)
🟩 Bug fix: Wrong reference numbers were generated for Swiss QR payment slips. (649332)
Reports (Turnover by Supplier/Gross Profit Hist.)
🟩 Bug fix: The report Turnover by Supplier was enhanced with an additional description on how to set the time frames to have the correct delta calculated. The first time frame must be more recent (e.g. in 2022) than the second time frame (e.g. in 2021). (650360)
Updates, New Client Versions and Installer
Contact our support team for an update appointment
Via email: Click the following link, fill out the email template and send it to servicedesk@descartes.com.
Via the portal: Log in to the Portal and open a Ticket.
Updates can either be done from Monday to Friday between 7:00 am and 5:00 pm or overnight. Ask the pixi Support team for an appointment.