General

[Fixed] A change to the way the Query tool handles special formats caused a "Property NFIELDLEN is not found" error when a numerical value was part of a query expression on some queries.

FF&E Worksheet

[Fixed] The reference to the PO number on the Worksheet was being truncated to the original eight characters of the number's length instead of the new ten character size (only on newly created orders). This problem only applied to initial users of version 4.2.023. It did not affect the orders themselves, only the copy of the PO number.

[Fixed] The query field for PO numbers in the FF&E Worksheet was failing to find existing entries due to the PO number size adjustment made in version 4.2.023. The query field definition for PO numbers was corrected, the size of the "PO Number/Export ID" field was changed, and existing contents were reformatted to conform to the new size.

Objects

[Fixed] When a Tag was changed and its primary component had a matching Spec ID, the system was not asking if you wanted to change the Spec ID to match the new Tag value.

Specifications

[Enhanced] The Utilities> Pricing Tool command now includes the ability to set a new vendor "Discount" value and either adjust the resulting margin (keeping the same prices) or adjust the price to match. The interface has been modified to show the three basic operations you can now choose:

The original "Adjust prices" option is now the second of this first set of options you choose. The full description is in the Help system under Pricing Tool. The same utility continues to be available on the Object and FF&E Worksheet screens.

[New] For purchasing management projects, the Pricing Tool's "Apply a vendor discount" option is now available to apply a discount to the base cost to calculate a new "Net Cost." Other options are still disabled since no "price" is involved on this billing type.

[Enhanced] The Pricing Tool now allows you to use an active query in the "Scope" option that determines which specifications will be processed. Note that the "active query" option is only available on the Specifications screen. This is to avoid accidentally changing specs used as secondary components when working from the FF&E Worksheet or Objects screens.

[Fixed] When using a query, the system would sometimes produce the error "Function requires row or table buffering mode," typically when leaving a field that validated the contents for entry errors or conflicts.

[Fixed] Superimposed text issues in the "Specification Status" reports when both submittal notes and specification status notes were present.

Orders

[Enhanced] If you void an issued order, the automatic revision note is now updated with that information.

[Enhanced] The vendor "Payments" reports were updated to better standardize their formats and make highlighting of amounts owed more consistent. Also:

• The "PO Notes" option on the "Vendor Payment List" report was reinstated.
• If PO Notes are printed, the system analyzes the notes for the presence of "all caps" notes and adjusts the text wrapping parameter to minimize "orphaned" line segments that wrap incorrectly.
• On the "Vendor Payment Recap" report, the PO number was moved to a heading, along with the "Paid To Date" flag, to make room for adding the "Freight Quote" and "Tax Quote" values from the order.

[Fixed] When entering a "freight-only" or "tax-only" item, the "Pre-payment" section's "Check Date" field would cause an error if a date was entered manually (but not if the shortcut keys like "+" or "-" were used first).

[New] The Help System's "How to..." section for the Purchasing Module includes a new section named "Managing Freight-only and Logistics Vendor Orders." This discusses  techniques for creating and processing orders for freight services (that is, where there is normally no FF&E amount).

[Fixed] Some automatic revision tracking notes were using the "$" symbol instead of the correct currency for the project or system.

[Fixed] The Query tools needed modifications to properly handle the new PO numbering options. The "PO #" and "Order #" field selections (which refer to the same thing) now format simple numbers with the left padding that matches how PO numbers are saved and sorted, while search values that include alphabetic characters are treated as a prefixed PO number and handled as left-justified 10 character values.

This means that:

• You can still search for simple numbered POs with just the PO number (you don't need to "pad" the entry yourself).
• As you might expect, a PO that uses a prefix must be entered exactly, with all characters to find an exact match with "is equal to" type comparisons.
• If you are on the Orders screen or the Expediting screen and using the "PO #" sort order, you can enter a prefix and still use "Starts with" to locate the beginning of the orders prefixed with that value.

Processing

[Enhanced] The "Enter Vendor Final Invoices" option includes some interface improvements.

Expediting

[Fixed] Query and Find tools handling of the new PO numbering options (see notes under "Orders" above).