NorthScope 2019.04.19

(Software Version: 2019.04.19 Database Version: 2019.04.19)

Release Date: April 19, 2019


New Features

Fisherman Accounting

NS-4381 Added functionality to apply a Chum % to mixed salmon tickets - used for Chum / Red split

Users can now apply a Chum % to Mixed Salmon tickets using the Ticket Mass Update. The split will only update tickets that are a Landing Type of B (Salmon) that contain either a mixed salmon item (specie of 460) or a matched set of Chum (specie of 450) and Red (specie of 420) ticket items. 

When the split is processed for a mixed salmon ticket item, the mixed salmon item is replaced with a matched Chum and Red item.

  • The # of fish (units) and the net weight of the Chum item is obtained by multiplying the number of fish and the net weight of the mixed fish ticket item to the Chum % and rounding each to the nearest whole number.
  • The # of fish (units) and the net weight of the Red item is obtained by subtracting the number of fish and the net weight of the Chum item from the mixed salmon item.

When the split is processed or re-processed for a ticket that no longer contains a mixed salmon item but contains a matched set of Chum and Red items, the chum and red items are added together, and the split is re-applied using the same logic from above.


NS-4381 Added ability to change a Fish Ticket Item

Previously, users could not change the Ticket Item ID on a saved ticket, they had to delete the line and add a new one. Ticket items, on tickets in a status of new, can now be changed. If they are changed on a ticket with a price list assigned, users will be prompted to update the price for that item. If they click OK, only that item will be updated, if they click Cancel, the price will not be updated.


NS-4381 Added more properties to the Ticket Mass Update

The following new properties were added to Mass Update:

  • GL Date – a date picker to allow entry of a new GL Date
  • Manual Premiums – a multi select combo box to add one or more active manual premiums.
  • Season - a lookup containing all active Seasons
  • Stat Area (for single Stat Area Tickets only) - a lookup containing all active Stat Areas


Improvements 

Fisherman Accounting

NS-4356 Allow edit of Fisherman, Tender, and Loan ID’s 

For NorthScope companies that do not integrate to a Host Database, or where the Vendor, Vendor Address, and Vendor Class integration is set to None, users can now edit Fisherman, Tender, and Loan ID’s, Address ID’s, and Fisherman Class ID’s. 


NS-4356 Allow delete of Fisherman, Tender, and Loan records 

For NorthScope companies that do not integrate to a Host Database, or where the Vendor, Vendor Address, and Vendor Class integration is set to None, users can now delete Fisherman, Tender, and Loan accounts, Addresses, and Fisherman Classes, provided they are not assigned to any transactions or other master files.

 

NS-4394 Updated error Message when importing tickets that do not contain a Grade

When Tickets were imported from eLandings, with ticket lines that did not contain a ‘Grade’ (e.g. Personal use Fish), and the NorthScope default Grade preference was not setup, the error message displayed was not descriptive enough to direct users how to fix the issue. This error message has been updated to display as “Ticket: [TicketNumber] - Missing ID value for Grade from the eLandings data and a Default Grade ID is not set up in the Fisherman Accounting Preferences. Please set up a Default Grade ID or set the Grade ID for the ticket line in eLandings.”

Purchasing

NS-4356 Allow edit of Vendor ID’s 

For NorthScope companies that do not integrate to a Host Database, or where the Vendor, Vendor Address, and Vendor Class integration is set to None, users can now edit Vendor ID’s, Vendor Address ID’s, and Vendor Class ID’s. 

NS-4356 Allow delete of Vendor records 

For NorthScope companies that do not integrate to a Host Database, or where the Vendor, Vendor Address, and Vendor Class integration is set to None, users can now delete Vendors, Vendor Addresses, and Vendor Classes, provided they are not assigned to any transactions or other master files.

Sales

NS-4291 Updated the Sales Order Notes

Customer notes that contained special formatting (e.g. Bold, Italic, bullet points etc.) and that were auto added to sales transactions, did not include the special formatting when they were added. The framework has been updated so Sales Transaction Notes support special formatting.


NS-4342 Updated the Sub Items column on the Sales Transaction Items List View

Previously, every line item for a sales transaction was displaying a value of “Yes” in the ‘Sub. Items’ column on the Sales Transaction Items List View if any of the transaction’s items contained a substitute item. This column now only displays a “Yes” for the specific items that have a substitute item(s).


NS-4375 Added Created Date to the Sales Transaction Shipment List View and Shipment History Inquiry

A new column containing the Created Date was added to the Sales Transaction Shipments List View and the Shipment History Inquiry. The column was not added to the System View but can be added to custom views.


Bug Fixes

Framework

NS-4297 Record View errors when columns were sorted, and new lines added

Previously if a record view was using a ‘Saved grid layout’ that contained a sorted column, the page would crash when the New button on the grid toolbar was clicked.

Load Management

NS-4383 Attributes not displaying on New Loads

When Loads were manually created or transactions were moved from an existing Load to a new Load, the Shipment/Load attributes were not displayed as expected.

Sales

NS-4056 Updated Allocation message

When users allocate Sales Order items using the “Allocate by Warehouse Lot” page and there is not enough quantity of the item in that warehouse lot, the message displayed to the user was confusing and has been updated to “Based upon the available quantities for the Warehouse Lot, auto allocation was unable to be completed and has resulted in an under allocation of product.  Please change the Allocate By to Inventory Lot to complete the allocations”.

System

NS-4420 Fixed an issue with Reports not printing

Previously, reports where the ‘Report Name’ and ‘Display Name’ were not identical caused an error when the report was printed. 

Note: Report Names are not allowed to contain special characters

Technical Changes

Please view cumulative schema changes here