FaVa 1.0.20240612.6 and FaVa Delogue 1.0.20240612.2 has been released on AppSource

Release note june

About this release

Released – 12 of June 2024

The release is build on:

  • Microsoft Dynamics 365 Business Central, 24.1 (min. release 24.0)
  • LS Central, 24.0 (min. release 24.0)

FaVa 1.0.20240612.6

Content

 
Excel export from sales order/invoice has been extended to handle assortments:

When selecting the “Export Order to Excel” function from a sales order, or the “Export Invoice to Excel” function from a sales invoice, it is now configured so that the assortments are “unpacked” and thus displayed with their real content at the variant level in the exported Excel file.

This way, the recipient of the sales order/invoice gets a better basis for creating the variants (items) contained in the ordered assortments.

Improved handling of warehouse shipments:

Until now, we have always generated one warehouse shipment per sales order from the FaVa Pick Worksheet. This is still possible, but now it is also possible to generate warehouse shipments in several ways.

This has been made possible by:

  • In FaVa Core Setup under the “Pick” overview panel, we have created a new field called “One customer per Warehouse Shipment”.
  • On the customer card under the “Shipping” overview panel, we have created a new field called “One sales order per Warehouse Shipment”.

The combination of these two new fields will result in generating Warehouse Shipments in the following ways:

  1. One sales order per Warehouse Shipment (as before)
    a) The “One customer per Warehouse Shipment” field in FaVa Core Setup must be activated.
    b) The “One sales order per Warehouse Shipment” field on the customer card must be activated.

 

  1. One customer per Warehouse Shipment
    a) The “One customer per Warehouse Shipment” field in FaVa Core Setup must be activated.
    b) The “One sales order per Warehouse Shipment” field on the customer card must not be activated.

 

  1. Multiple customers per Warehouse Shipment
    a) The “One customer per Warehouse Shipment” field in FaVa Core Setup must not be activated.
    b) The “One sales order per Warehouse Shipment” field on the customer card is hidden and thus cannot be activated.

Additionally, through the new field on the sales order header called “Must be picked and delivered separately,” you can control whether the sales order should be on its own warehouse shipment and thus picked separately. When creating a new sales order, the following will occur:

  • If the “One sales order per Warehouse Shipment” field on the customer card is not activated, the “Must be picked and delivered separately” field on the sales order header will be editable and by default not activated.
  • If the “One sales order per Warehouse Shipment” field on the customer card is activated, the “Must be picked and delivered separately” field on the sales order header will not be editable and by default activated.

Moreover, the fields shown below on the warehouse shipment header will be automatically filled in depending on whether the warehouse shipment contains one sales order, multiple sales orders from the same customer, or multiple sales orders from different customers:

  • Sales Order No.
  • External Document No.
  • Order Type
  • Sales Season
  • Brand
  • Customer No.
  • Customer Name
  • Customer Priority
  • Ship-to Name
  • Ship-to Address
  • Ship-to Country/Region
  • Quantity (flowfield)
No availability check and split on sales orders with “Drop Shipment” or “Special Order”:

If a sales order line is marked as “Drop Shipment” or “Special Order,” availability checks and splits have so far been performed on an equal basis with other “regular” sales order lines. Logic has now been implemented in the Dimension Matrix on sales orders to ensure that no availability check and split is performed if the sales order line is marked as one of the aforementioned.

Moreover, the displayed statistic values in the Dimension Matrix will not include sales order lines and purchase order lines marked for either “Drop Shipment” or “Special Order.”

Improvement to Shopify Item Export filter:

Changes have been made in the Item Export Setup under Shopify administration (LS). It involves how items are enrolled in the distribution group based on new filter fields. It is also new that only items within the filter are enrolled, and items outside the filter will no longer have the web distribution group removed.

Fixes

  • Changed validation sequence when importing sales orders:

    Issue: In connection with the update to BC24/LS24, we found that there was an apparent change in the validation sequence, which could result in the line discount percentage being lost during the sales order import.

    Solution: This has now been fixed.

  • Error message when opening Dimension Matrix after deleting variants:

    Issue: Opening the Dimension Matrix (for example, from a sales order line) has until now required that all sizes within a color exist. Otherwise, this resulted in an error message in situations, where some sizes (variants) had been deleted.

    Solution: This has now been fixed.

  • Printing Sales Credit Memo containing only financial lines:

    Issue: When printing a Sales Credit Memo containing only financial lines, the system entered an apparently infinite loop, causing the print to fail.

    Solution: This has now been fixed.

  • Changing FaVa Item Status directly on the item card:

    Issue: In the context of improved handling of item status in FaVa Item Sales Seasons, included in the latest FaVa release (1.0.20240514.8), there was an issue when changing the FaVa Item Status directly on the item card. The issue was a dialog box informing that there are underlying variants with a higher sorting value than the one being changed to, and these would not be changed automatically. Instead, there should have been a confirmation dialog stating that the item status would automatically change for all underlying levels.

    Solution: This has now been fixed.

  • Proforma Invoice with one-dimensional items missing content:

    Issue: Following the introduction of correct display of variant-specific prices on FaVa reports, included in the latest FaVa release (1.0.20240514.8), an unintended issue arose with printing Proforma Invoices. The problem was that items with only one dimension were printed without quantity and price.

    Solution: This has already been fixed and released in a FaVa hotfix (1.0.20240530.2), which was released on AppSource on May 30, 2024.

  • Display of variant-specific prices on FaVa reports:

    Issue: Following the introduction of correct display of variant-specific prices on FaVa reports, included in the latest FaVa release (1.0.20240514.8), there were minor adjustments needed, primarily related to consistent logo placement, right alignment of quantity fields, and spacing between lines.

    Solution: This has now been fixed.

FaVa Delogue 1.0.20240612.2

Content

 
Import from Custom Fields in Delogue to BC item attributes:

Just as it has been possible to import from Custom Fields in Delogue to LS attributes, it is now also possible to import these into BC item attributes.

At the same time, the number of options in the “Map to Type” field in Delogue Field Mapping in FaVa has been reduced to the following:

  • Blank value
  • Item
  • Item Attribute
  • Assortment
  • LS Attribute
Naming of fields under Delogue Price Type Mappings:

The “Price Type” field in Delogue Price Type Mappings in FaVa has so far included the following values, among others:

  • Supplier Cost
  • Cost

As there could have been confusion about which fields these referred to, the values have now been changed to the following:

  • From “Supplier Cost” to “Vendor Purchase Price”
  • From “Cost” to “Item Cost Price”