FaVa 1.0.20240514.8 and FaVa Delogue 1.0.20240514.3 has been released on AppSource

FaVa release note

About this release

Released – 15 of May 2024

The release is build on:

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

FaVa 1.0.20240514.8

Content

 
Display of quantity in assortment on the “FaVa Item Variants” page:

On the “FaVa Item Variants” page, a new field called “Qty. in Assort” has been added, which is intended to enhance the “readability” in relation to the quantity in stock. The field will contain the value “0” (zero) if it’s a regular variant. If it’s an assortment variant, the field will display the quantity of items in the assortment.

FaVa release variants

When looking up the “Qty. in Assort” field, the assortment content will be displayed assuming that the “Qty. in Assort” contains a value greater than “0” (zero), otherwise, a message will appear stating that this is not an assortment.

FaVa release collection
Improved handling of item status on FaVa Item Sales Seasons:

Previously, it was necessary to manually change the item status for all underlying variants if the item status at a higher level was changed to an item status with a lower sorting value.

FaVa Release Coilor season

This has now been improved so that the item status is automatically changed, ensuring that there cannot be a situation where an underlying variant has an item status with a lower sorting value than the one found at the higher level.

At the same time, it is ensured that underlying variants with an item status with a higher sorting value than the one being changed to will not be affected by the change, and thus will retain their original item status.

The above applies to the following pages:

  • Item Card
  • FaVa Item Sales Seasons
  • FaVa Item Color Sales Season
Direct lookup from quantity fields to underlying tables:

Lookups to underlying tables have now been made directly from the following pages and fields:

  • Page “Sales Order”:

Field “Qty. Shipped Not Invoiced”: Lookup to Posted Sales Shipment Lines

Field “Qty. Invoiced”: Lookup to Posted Sales Invoice Lines

Field “Whse. Qutstanding Qty.”: Lookup to Whse. Shipment Lines

  • Page “Sales Return Order”:

Field “Ret. Qty. Received Not Invoiced”: Lookup to Posted Return Order Receipt Lines

Field “Qty. Invoiced”: Lookup to Posted Sales Credit Memo Lines

  • Page “Purchase Order”:

Field “Qty. Received Not Invoiced”: Lookup to Posted Purchase Receipt Lines

Field “Qty. Invoiced”: Lookup to Posted Purchase Invoice Lines

  • Page “Purchase Return Order”:

Field “Ret. Qty. Shipped Not Invoiced”: Lookup to Posted Return Shipment Lines

Field “Qty. Invoiced”: Lookup to Posted Purchase Cr. Memo Lines

Possibility of using bank details on non-FaVa sales reports:

It is now possible to utilize currency-specific bank information on customer’s own reports in cases where the customer does not want to use FaVa standard reports. Which printouts this applies to is still controlled from the “FaVa Report Setup” page (Sales Order Confirmation, Sales Shipment, Sales Invoice, Sales Credit Memo and Customer Statement), and it is now combined with the report selection made from the “Report Selection – Sales” page.

FaVa report setup
Improvements to “Copy Sales Document” and “Copy Purchase Document” functions:

Several improvements have previously been made to the “Copy Sales Document” function when copying to a Sales Order. Relevant changes have now also been implemented in relation to the following documents:

  • Sales Return Orders
  • Sales Invoices
  • Sales Credit Memos
  • Purchase Orders
  • Purchase Return Orders
  • Purchase Invoices
  • Purchase Credit Memos

Changes have primarily been made to ensure that FaVa fields are correctly transferred to matrix lines and item lines, and that the lines are correctly recalculated and filled in when selecting “Recalculate Lines”. This applies to both regular lines and assortment lines.

Improvements to changing customer number or vendor number on documents:

Similar changes as mentioned above in relation to “Recalculate Lines” have also been made in relation to changing customer number on sales documents and vendor number on purchase documents.

Display of variant-specific prices on FaVa reports:

New functionality has been implemented for displaying variant-specific prices on FaVa sales reports and FaVa purchase reports, ensuring “coherence” between quantity, unit price and line amount.

To ensure that the reports correctly display the variant-specific prices, lines and matrices on the reports are now sorted and divided according to the number of combinations of unit price and indicative price.

This means that one matrix line on the document may result in several lines with associated matrices on the printout.

This applies to the following FaVa reports:

  • Sales – Quote (report 71170586)
  • Sales – Confirmation (report 71170585)
  • Sales – Invoice (report 71170584)
  • Sales – Credit Memo (report 71170583)
  • Purchase – Order (report 71170582)

At the same time, it has also been implemented to the sales order confirmation, that the indicative price is retrieved from the sales prices (and not from the document line), ensuring that it always shows the currently applicable indicative price. Posted documents will always print the indicative price from the document line, as we do not want to change “historical” documents.

Export to Excel function on sales orders and sales invoices:

The file has now been expanded with the columns “Customer No.” and “Customer name”.

New field on the item table called “Picture imported from”:

The item table has been expanded with a new hidden field called “Picture imported from”, which can have the values “” (blank) and “Manual”.

Fixes

  • Issue with entering item number with one sales season on purchase order line:

    Issue: When entering (validating) an item number with only one associated sales season on a purchase order line, an error message appeared stating that the sales season contained a value that was not found as an item sales season.
    Solution: This has now been fixed.

  • Issue with transferring lines from requisition worksheet to purchase order:

    Issue: When transferring lines from requisition worksheet to purchase order, an error message appeared stating that the sales season contained a value that was not found as an item sales season, but only in cases where the item number was only associated with one sales season. Furthermore, the season was not applied as a dimension on purchase order item lines.
    Solution: This has now been fixed.

  • Issue with transferring assortment lines from requisition worksheet to purchase order:

    Issue: When transferring assortment lines from requisition worksheet to purchase order, an error message appeared stating that the sales season needed a value, but only in cases where the item number was associated with multiple sales seasons. Furthermore, the season was not applied as a dimension on purchase order assortment lines.
    Solution: This has now been fixed.

  • Purchase order with expected receipt after sales and before delivery:

    Issue: In the situation where there is a purchase order with an expected receipt date after the sales period and before the delivery period, the split functionality in FaVa found that the sales order line could be delivered before the start date of the delivery period, which was not correct.
    Solution: This has now been fixed so that the split functionality ensures that the shipment date on the sales order line can never have a date before the start of delivery.

  • Standardization of pages regarding the fields “Type”, “Variant Code”, and “Description 2”:

    Issue: Previously, the fields “Type”, “Variant Code”, and “Description 2” were not consistently displayed primarily on posted document lines.
    Solution: This has now been fixed.

  • Issue with invoicing fully delivered sales order with existing freight amount:

    Issue: Previously, there was an issue where the system attempted to insert a new freight line without an amount if the sales order was already fully delivered and had an existing freight line before invoicing.
    Solution: This has now been fixed.

  • Standardization of FaVa reports:

    Issue: Previously, there was an issue where, for example, the letter “g” would have the bottom of the letter “clipped off” if it was part of the address lines at the top left of the FaVa reports. Furthermore, there has not been consistent placement of the logo at the top right of the FaVa reports across the documents.
    Solution: Both these issues have now been fixed.

  • Export to Excel function on sales orders and sales invoices:

    Issue: Previously, there was an issue where the sales season (labeled “Collection” in the file) was retrieved from the item delivery sales season and not from the sales line itself.
    Solution: This has now been fixed.

FaVa Delogue 1.0.20240514.3

Content

 
Import of picture URL from Delogue:

New functionality has been implemented for importing pictures from picture URL in Delogue, which will be placed as a picture in the fact box on the item card and in the item list.

  • The field “Picture imported from” on the item table has been expanded:

    The field has been expanded with the value “Delogue”.

  • The field “Picture imported from” on the item table has been expanded:

    The fact box “Picture” on the item card and in the item list has been replaced by a separate FaVa fact box.

  • In Delogue Setup, a new overview panel called “Picture” has been added:
    • Field “Import Pictures”:
      If the field is activated, the picture from the style in Delogue will be imported to the item picture in FaVa and will thus be displayed in the fact box.
    • Field “Allow Update Pictures”:
      If the field is activated, it allows the picture from the style in Delogue to be updated on items that already have a picture from Delogue, but only on the condition that the field “Picture imported from” has the value “” (blank) or “Delogue”.
    • Field “Picture Max Width”:
      Here, the pixel width of the pictures imported from Delogue is specified.
Delogue release setup