pixi 24.04 is available from 2 April 2024. It includes several bug fixes, new features, enhancements and optimizations. Reference the numbers in parentheses if you have any questions for support. You can download the latest full installer after the database update on pixi Web under Administration > Downloads.

Important information on the pixi Accounting Export App 2.0:
- End of Life (30 April 2024):
The pixi Accounting Export App 2.0 will be officially discontinued on 30 April 2024.

The functionalities of the app have already been migrated to pixi Web with the recent releases.

Hotfixes

Hotfix 1

We released a hotfix on 15 April 2024.

General

🟩 Bug fix: Various issues have been resolved: (1018073)

Email Adresses in User Management and Profile Settings: The number of allowed characters for top level email domains has been increased from 4 to 20 characters.
Purchase Orders: Editing order lines in status NEW was not possible.
ShipRush: In some cases, incorrect credentials were used for the connection to ShipRush.

Controlling (Accounting Export)

🟪 Enhancement: The file encoding (ANSI or UTF-8) can now be set in the Options section of the Profile details page. (996530)

Hotfix 2

We released a second hotfix on 22 April 2024.

ShipRush

🟪 Enhancement: pixi-ShipRush integration improvements: (1020689)

Automation rules can now be created for each shipping vendor
Improved mapping for exchanged data

API

🟪 Enhancement: The API call pixiUpdateOrder was modified to allow the removal of the ShipDate value. An empty value for the ShipDate parameter (ShipDate = '') now removes the shipping date for the order. If the value of the ShipDate parameter is null or the parameter is not specified, the existing shipping date is retained. (990064)

🟪 Enhancement: The following parameters were modified for API call pixiUpdateDelivery: (988691)

@SupplNr was changed from VARCHAR(10) to VARCHAR(4)
@extInvoiceNr was changed from VARCHAR(100) to VARCHAR(25)
@extOrderNr was changed from VARCHAR(100) to VARCHAR(8000)
@UserName was changed from VARCHAR(100) to VARCHAR(50)

pixi Mobile

General

🟩 Bug fix: The request to confirm the bin (user permission Enable bin confirmation) did not work. Now, when scanning the bin/entering the bin name, the confirmation popup is displayed if the authorization is enabled and not if the authorization is disabled. This fix applies to the Goods Receipt, Relocate Put to Stock and Take from Stock programs. (955627, 991158, 991159, 991160)

🟪 Enhancement: If the box range is changed for the original picklist, it also changes for the linked picklists (for programs Pick-to-Box and Scan-In). (958717)

Picklist

🟪 Enhancement: The location on the web has no influence on the assignment of the transport bin to the picklist on the web if the mobile pick location is used. The picklist location, the transport bin and the user's Mobile location must be the same. (996569)

Pick to Box

🟩 Bug fix: pixi Mobile crashed when boxes were assigned. (996507)

🟪 Enhancement: Boxes are now always marked as physically full when the last item of a picklist was scanned. (998830)

🟪 Enhancement: If the Box confirmation needed setting is disabled, the next item can be scanned directly. Therefore, the box information and next item information are on the same screen, along with the field to enter the next item and the Continue button. (962801)

Replenishment

🟩 Bug fix: The option All items to target bin was not available in the three-dots menu. (983976)

Scan-In

🟩 Bug fix: If a shortage was reported in the Scan-In program, pixi flagged all items in the box and the missing items as a shortage. This problem only occurred when transport bins were used. (989130)

🟩 Bug fix: In some cases no box confirmation was displayed. (1003191)

Web Application

Administration (User administration)

🟩 Bug fix: When editing the password expiration frequency of several profiles, the email address of the edited users was removed. (964958)

🟪 Enhancement: The Expires on field cannot be edited.

Note: The expiration date is calculated when the user changes the password. The current date and the expiry interval are critical. (966006)

🟪 Enhancement: If an auto-generated password is created, pixi sends the password with the email address in PixiMail e-mail address database setting as sender address. (986264)

Controlling (Accounting Export)

🟩 Bug fix: Accounting exports failed for POS invoices. The export of POS invoices and payments now works. (999407)

Controlling (Dashboards)

🟩 Bug fix: Loading the tiles could take up to one minute. Performance was optimized. (976058)

Customer Service (Customers)

🟩 Bug fix: The TAGS parameter changed its value to AND after refreshing the page. It now keeps the same value that was set during the last search as the other parameters. (1005705)

Customer Service (Invoices and Credits)

🟪 Enhancement: The allowed number of characters for the Tracking ID and Returns Tracking ID fields has been increased to 8,000 characters. (988681)

General

🟦 Optimization: Handling of sessions when users are logged in from different servers (load balancer configuration) has been improved. (991141)

Items (Item Management)

🟩 Bug fix: In some cases the item export did not work. (982236, 976249)

Logistics (Goods Receipt)

🟩 Bug fix: Upon entering the date in the Receipt Date field, the system allowed exit without inputting four numbers as required by the default format (e.g., 1/18/2024). (975073)

Logistics (Picklists)

🟩 Bug fix: The parameter Only for single item (EAN) did not work if the item code started with zeros. (975512)

🟩 Bug fix: Bug fixes for picklist profiles: (991966)

The validation of the values Min. and Max. for the parameter Number of Orders was missing
If Box physically full was enabled for Pick to Box and then disabled again, the number of orders Min and Max was not editable. From now on it remains at 1 for both (as for Box full)

Logistics (Scan-In)

🟩 Bug fix: If the Do not print option is selected for Invoices and Credits, no delivery bill was printed when scanning the 1SS picklist. (980153)

🟩 Bug fix: The naming of a German UI element was fixed. (1001532)

Logistics (Ship-Out)

🟩 Bug fix: The issue with printing return labels for external labels has been resolved. For shipping vendors who have selected ‘PDF Download from URL (ExternalPDF)’ as the shipping label option, the return label will now be printed alongside the shipping label if the ‘Print return label’ setting is enabled. (995124)

🟪 Enhancement: The total weight of the items is now displayed on the Multiple Packages page on the right-hand side of the page. This helps prevent the shipping vendor's weight limit from being exceeded. In addition, a summary has been added to the footer of the overview with the number and total weight of the items in the parcel. Each time a new item is scanned/entered into the parcel, the summarized quantity and total weight will change/calculate, regardless of the DB setting for the weight. (926623)

🟪 Enhancement: A new functionality is available: Change Shipping Vendor. This is supported alongside the automatic confirmation for selecting the Shipping Vendor. The shipping labels will be printed automatically if the option is enabled after the last item from the invoice has been added to the package. (936514)

🟪 Enhancement: A procedure for preparing the data for the shipping label has been optimized to prevent the same automatically generated tracking ID from being assigned to two invoices/packages if they are created at the same time (two users perform shipping at the same time). (959193)

Logistics (Stock)

🟪 Enhancement If the setting No warning at picklist is enabled, it is possible to take an item that is on a picklist from stock. If this setting is disabled, the error message appears and the item cannot be taken from stock. (1001160)

Purchasing (Purchase Orders)

🟩 Bug fix: Email templates could not be saved after the .xlsx attachment option was disabled. (990522)

🟪 Enhancement: A functionality is available: Set discount. It allows you to select the order lines to which a discount should be applied. To do this, one or more order lines of an order must have the status NEW. Once the changes have been saved, the total of the order lines and the amount to be paid are recalculated on the basis of the discount type and value entered. (990522, 921628)

🟪 Enhancement: pixi now uses new SMTP mail components for Purchase Orders and Offers. (952858)

Desktop Applications

Control Center

🟩 Bug fix: In some cases, credit notes for partial refunds could not be deleted. As part of the bug fix, the database setting Returns, status change of order to RET has been removed. (965518)

Import & Export

🟪 Enhancement: If an item is re-imported without a value for the EAN code and the database setting BMECat, keep supplier data on import is enabled, no new data records are created for suppliers with a new EAN. (985764)

🟪 Enhancement: If an item is provided with 3 characters in the database field CustomsCountryOfOrigin, it remains as it is if the item import has no information about CustomsCountryOfOrigin (empty in XML). If the item import provides information about CustomsCountryOfOrigin, it is changed to the country code of the ISO2 standard. (1007400)

🟦 Optimization: The cleanup of old XMLs has been improved. Previously, only XMLs in the OK and ERROR status that were older than X days were deleted. Now all XMLs older than X days are removed, regardless of their status. (904871)

🟦 Optimization: The processing of XML files with the status RTE (Ready to export) has been improved. Previously, the oldest XML file was skipped and the others were reprocessed. Now the oldest non-expired XML is also processed. (996051)

Plentymarkets 7

🟩 Bug fix: Orders could not be imported from plentymarkets to pixi without the error "Attempted to divide by zero" if the order had order lines with a discount. (913212)

Invoices

🟪 Enhancement: If different locations are set on the order lines of an order, the automatic invoice creation now also checks the location of the order line and creates the invoice as soon as all order lines of a location have been scanned into the box.
Example: A customer order consists of three order lines. Two are in location 001, the third is in 002. During automatic invoice creation, each location is checked individually. The invoice to location 001 is created when the first two order lines are scanned into the box, regardless of the status of the third order line. The invoice to location 002 is created when the order line is scanned into the box, regardless of the status of the order lines at another location. (965600)

🟩 Bug fix: Print rules did not work in some cases. (976822)

🟪 Enhancement: Changes to the Invoices desktop app: (989541)

If two or more orders of a customer are completely on one picklist, the automatic invoice creation waits for all items to be scanned into (the same) box and only then starts the invoice creation. Previously, the invoice was already created when all items of the first order that were placed in the box were scanned.
It'll only work with automatic invoice creation via the Invoices desktop application.
All the conditions that are used at scan-in for combining orders into boxes are considered:
- Addresses on all orders are 100% the same.
- in Shops table, setting "Address or Order" must be set to A or empty
- in Payments table, setting "Separate orders in boxes" must be OFF
- Orders can be put into separate boxes when they include vouchers
- For orders that are partially on picklist, SHIP NOW must be enabled otherwise invoice creation waits for the missing items

Payments

🟩 Bug fix: As many rows were exported as there were matches if the refund to PayPal matched two or more other events. Now only one line is exported. (993357)

Updates

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.