Release notes RetailVista 18.2 spring release 2018

General / miscellaneous

(Version 18.2.6659.20487) Task 17700 - Expand sales data export to suppliers with barcode text (follow-up to task 17698)

In the SLSRPT (Sales, sales) export file, a 2D barcode is now also exported, provided it was part of the original sales line.

(Version 17.27.6634.37588) Task 17699 - In 'Quick navigation' scan 2D barcode and go directly to receipt where this barcode appears

In 'Quick navigation' on the main page of RetailVista, a 2D barcode can now be scanned. This immediately opens the article receipt where this barcode appears. This makes it easy to quickly find the batch barcode (=ViridiCode) in a specific article receipt.

(Version 18.2.6659.20487) Task 17682 - Search for barcode text in article search screen

From now on, it is also possible to search for text barcodes in the article search. Previously, only numeric barcodes were supported.

(Version 17.26.6620.36549) Task 17361 - Add phone and email as placeholders in order email template

The following email templates have been added with the fields 'Phone', 'CellPhone', and 'Email'. These fields return the phone number, mobile number, and email address of the customer of the sales order.

- Supplier approval sales order

- Customer approval sales order

- Supplier expiration message sales order

- Customer expiration message sales order

(Version 18.2.6659.20487) Task 17697 - Adjust RetailVista Mobile license model

The applications that can be displayed on a scanner have been moved from the scanner to the security role. As a result, the applications are no longer tied to the physical device, but to the logged-in users. The connection to the user is made through the security role, but this is only done so that applications do not have to be selected per user. However, it is important to specify the correct security role for each user.

As part of the update installation, the applications are converted to the security role to which a user is linked, if possible. This only applies to scanners where a fixed user was set. For all scanners without a user, it is not known to which user the set applications should be converted. For this reason, it has been chosen to activate 'All' applications by default for all other security roles. Therefore, it is necessary to go through the security roles once after installing the update and activate the correct applications per role. If this is not done, it may happen that too many applications become active when logging in and that the license ultimately becomes insufficient.

Product maintenance

(Version 18.2.6659.20487) Task 17721 - Ability to set key field for export of product number or external code

In the settings per location for export to Wics and SlimStock, it is now possible to set whether the article number or the external code should be used as the 'key' field. By default, the article number is used (and recommended), but it is possible to use the external code of the articles instead.The same settings are automatically applied to all products that come back from SlimStock and Wics. If the external code is not specified for a product, that product will be ignored in the export.

(Version 17.27.6634.37588) Task 17693 - Creating a hash of 2D barcodes

A 'hash' of 10 characters is generated from a 2D barcode (2-dimensional). This hash essentially represents this barcode in a compressed form. The advantage of the hash is that it is relatively easy to find a specific 2D barcode in a list of barcodes (comparing about 50 characters is almost impossible, unlike a code of 10 characters). The hash of a barcode can of course be printed on a label, and it is recommended to do this as text below the 2D barcode.

(Version 17.27.6634.37588) Task 17692 - Ability to store text barcodes in article maintenance

In article maintenance, text barcodes can now also be stored. These must have the type 'Code 39'. In the article search screen, text barcodes can of course be searched for, this is done through the existing barcode search field. Just like numeric barcodes, text barcodes must be unique.

(Version 17.23.6564.40134) Task 16674 - Ability to deviate from the standard number of delivery days for the supplier per purchase information

In the purchase information of a product, it is now possible to indicate the number of delivery days. This deviates from the standard delivery days for the supplier.

Product lists

(Version 17.23.6564.40134) Task 17434 - Purchase prices missing in Excel export

In the product list Excel export, purchase prices were no longer exported. This issue has been resolved.

(Version 18.2.6659.38210) Task 16435 - When transferring a product list to a quote, ask for a customer if not specified in the list

When converting a product list to a quote, a customer will now be requested if no customer is specified in the product list. Product lists can work without customers, but quotes cannot.

Coding

(Version 18.1.6647.38210) Task 17755 - Generating ViridiCode according to settings

If RetailVista creates a ViridiCode itself, it will be based on the '2D barcode format' settings. These settings can be found under Extras -> Settings -> section Received products -> tab General -> '2D barcode format'. The intention is to specify the various components (Barcode Application Identifiers) here, separated by the | symbol.

Exchange Excel import

(Version 18.1.6647.38210) Task 17665 - Excel import accepts a purchase code with a comma, but these lines are not processed when booked in Exchange

From now on, the Excel import in Exchange will no longer accept , characters in purchase codes. This character is reserved internally and causes issues with certain export formats, so it should not be used.

Purchase orders

(Version 17.26.6620.36549) Task 16054 - Task Custom purchase order reports without purchase prices

From now on, custom purchase order reports created at the organization level will also be visible to underlying companies. By connecting with the report designer at the organization level, the custom reports will automatically become visible to underlying companies. The description of the report will indicate that it is a report from the organization.

Receipts

(Version 17.27.6634.38210) Task 17665 - Excel import accepts a purchase code with a comma, but these lines are not processed when booked in Exchange

37588) Task 17703 - Add column 'Standby product number' to the product receipt grid

In the product receipt grid, a new column 'Standby product number' can now be added. The standby product number is used when booking received plants.

(Version 17.27.6634.37588) Task 17702 - Ability to print 2D barcodes for receipts

In the product receipt, it is now possible to print 2D barcode stickers. If a receipt line does not have a 2D barcode yet, it will be created at that moment. The 2D barcodes are mainly intended for plants.

A 2D barcode requires a separate field on label layouts, the barcode does not appear in the same place where 'linear' barcodes (such as Ean13) are normally located. QA576 describes how Datamatrix codes can be printed on Sato thermal printers.

(Version 18.2.6659.20487) Task 17701 - Ability to import XML Desadv delivery note message with 2D barcodes

From now on, it is possible to import a NedFox XML Desadv delivery note message via RetailVista. This format contains a richer delivery note message in which, among other things, 2D barcodes can be recorded.

(Version 17.27.6634.37588) Task 17695 - Add TwoDimBarcode field to ReceivedProducts

In the product receipt line, the 2D barcode that is linked to the receipt line is now shown in the 'Advanced' tab, along with the found standby product number. This information is especially important when importing plant receipts.

POS

(Version 18.2.6659.20487) Task 17782 - Ability to set a product ready for a specific relationship via Retail3000 API call

In the Retail3000 API, a new method AdQueueBustingProduct has been created. This allows a specific product to be set up as a 'pre-scanning' rule. In POS terminal groups, it can now be indicated that all pre-scans should be loaded automatically when starting a transaction.This happens automatically after scanning a loyalty card. Only automatically pre-scanned data can be loaded from pre-scans that are linked to a specific loyalty card. All other pre-scans remain on the server and must be loaded 'manually'.

(Version 17.27.6634.37588) Task 17696 - Trying to determine purchase price via article receipt line when processing POS transaction

If a user has the '2D barcodes' license, the purchase price from the receipt line is searched when processing a POS transaction with a 2D barcode. This ensures a correct margin display for plant sales.

Promotions, discounts

(Version 18.2.6659.20487) Task 17465 - Add in/ex VAT to price agreement

RetailVista now also supports in and ex VAT prices. In the existing price agreements, it can now be indicated whether a price agreement is in or ex VAT. And for relationships, it can now be specified whether in or ex VAT prices apply. If, for example, it is specified for a relationship that an ex VAT price is desired, an ex VAT price will first be tried to be found in the price agreements. If it cannot be found, the regular sales price information will be used as a fallback.

Reports

(Version 17.25.6600.36895) Task 17464 - Sub-reports can be maintained

In the report designer, sub-reports can now also be maintained. The procedure is as follows:

- In the designer, 3 reports have been added, the current existing sub-reports. These can be copied and designed separately, just like all other reports. The sub-report number is important to remember.

- In the report (e.g. a sales order), a sub-report number can now be specified for the sub-report. Enter the sub-report number from the previous step here, and the layout of that sub-report will be used.

Statistics

(Version 18.1.6647.38210) Task 17706 - Creating a connection between RetailVista and Tamigo

From now on, it is possible to connect RetailVista with a check-in time registration. In this case, a connection has been made with Tamigo. Unfortunately, the connection itself is very basic, as only the daily turnover is exchanged from RetailVista to Tamigo. Technically, RetailVista is capable of much more, but at the moment, Tamigo seems to be unable to handle it. The connection can be set up once via the 'Staff Management Provider'. In addition, a task needs to be created in the task scheduler to export to Tamigo at a certain time interval. The export is a webservice connection, so data is directly exchanged between RetailVista and Tamigo.

(Version 18.1.6647.38210) Task 17705 - Adding country description to statistic 300

From now on, the country of the customer to whom the sale is made is also exported as a column in statistic 300.

Sales Orders

(Version 17.25.6600.36895) Task 17649 - Expanding Reports 110 and 112

In these two reports, warehouse information fields have been added to the datasets. This makes these reports useful as restocking lists from the warehouse to the store.

Inventory

(Version 18.2.6659.20487) Task 17155 - Ability to import inventory levels from external suppliers

Through Inventory -> Supplier inventory, the external inventory of articles from suppliers can now be viewed. The inventory is also displayed in the article statistics tab.

The inventory can be provided to RetailVista by external parties through the EDI message INVRPT (Inventory report).