Skip to content
English
Sign in
Contact us
  • There are no suggestions because the search field is empty.

Release 17.10.16 DB Version 154

Receiving

  • The report menu on the receiving screen now include a quick report and PO form option.

Used Processing

  • An option was added to used processing to change how the default values for the product are entered
  • [i]merchant traditionally tries to match the product being entered to an existing item on file. When a match is found the item fields, department category, accounting category, book class, etc. default from the matching item.  
  • A session setting check box was added to disable this behavior and always use the values set in session settings.
  • Checking the “Always use Session Settings as defaults” box in session settings will:
    • Item fields for the product being entered will initially default from the values in session settings.
    • The defaulted items can be changed as needed.
    • Selecting an existing item from the list of items on the bottom of the processing screen will not alter the values already on the screen.
    • Department Category will always come from the session setting.  The BISAC category mapping, product authentication, and other default logic is disabled.

Store Properties

  • The Used Store settings for a store have new fields.
  • A default department category has been added. This becomes the default of the used processing session setting.
  • A check box for default state of the “Always use Session Settings as defaults” option.

Customer Reports

  • The barcode text for a customer or customer order did not include the [i]merchant identification characters, “CID” or “CO”.
  • These have been added for an accurate representation of the barcode information.

Finders

  • The F12 key has been added to the shortcut keys that can close the form.

Used Receiving

  • When adding an item the on hand quantity will default to 1.

Point Credit Cards

  • MAC counter is now being saved after a MAC error.

Sales

  • Ten user definable sales periods have been added to [i]merchant. These can be added to reports, grids, screens, and product searches
  • The sales periods can be configured under Tools > Administration > Designers > Custom Sales Periods.
  • A custom sales period must be added to a product property screen for it to be visible in the system.
  • Sales are accumulated from the weekly or monthly sales analysis information within [i]merchant.
  • Sales are accumulated dynamically looking back from the current date.
    • The starting Periods Back field tells [i]merchant the first period to use in the calculation.
    • The Ending Period Back indicates the last period to include.
  • Each custom sales period contains the following fields:
    • Caption the field name displayed in [i]merchant.
    • Short Caption  shortened version of the caption.
    • Period Toggle between week or month sales.
    • Starting Periods Back: The number of weeks or months from current that will be used as the starting sales date.
    • Ending Period Back: The number of weeks or months from current that will be used as the ending week or month.
  • Sales are calculated dynamically by [i]merchant.
  • Performance will vary based on the number of periods needed to accumulate and the number of custom sales fields added to a screen or report.

ODB Interface

  • Added a try/Catch to avoid Sticky Save error.

System Options

  • An Email test button was added.

DB Maintenance

  • The SQL Log file backup has been disabled. Since we use a simple recovery model for SQL the backup is not need. Attempting to run a log file backup on some systems causes the rest of the DB tasks to fail.