NorthScope 2020.03.06
(Software Version: 2020.02.14 Database Version: 2020.03.06)
Release Date: March 6, 2020
Improvements
Fisherman Accounting
NS-5894 Added Ticket Taxes by GL Period Report
Have you dreamed of viewing Fish Ticket Taxes by GL Period? With our new report, you can do just that. Navigate to Fisherman Accounting > Reports to make your dream a reality.
NS-5997 Added Ticket Number to the Fish Ticket History and Fish Ticket Item History Inquiry Criteria
We thought it would be helpful to add Ticket Number to the Inquiry Criteria on the Fish Ticket History Inquiry and Fish Ticket Item History Inquiry so that you may quickly filter on a specific Fish Ticket Number. Done and done.
System
NS-5993 Added new "NorthScope Base URL for Report Hyperlinks" System Preference
Reports are complicated enough without having to think about creating custom versions to navigate to a specific URL. We added a new System Preference for Reports called “NorthScope Base URL for Report Hyperlinks". Use this preference to stipulate the absolute URL for your reports and show 'em who’s boss.
Note: Don’t fret about setting this, we will take care of that for you when we upgrade your system.
Bug Fixes
Inventory
NS-5604 Fixed issue for Transfers posting multiple times to the lot cost history table if duplicate lines exist on the transaction
If a Production Lot is set up with a Base Cost or Cost Layer, posting a transfer transaction creates the same cost structure for the ‘To Site’. However, on transfers that contain two identical line items with different quantities, we were inadvertently creating two identical rows in the Cost History Inquiry. We’ve updated the code to create one and only one row on the Cost History Inquiry regardless of the number of identical lines on a given Transfer transaction.
Note: A datafix is included to Void any duplicate rows that may have previously been inserted into the lot cost history table.
Additional Note: Voiding and/or correcting Transfer transactions will not affect the Base Cost or Cost Layers that were added for the associated Production Lots on either the ‘From Site’ or the ‘To Site’. Once a Base Cost or Cost Layer has been added for a Production Lot, we will not remove any costs on the Production Lot regardless if the Transfer transactions that created the costs are voided or corrected. For example, if ‘From Site’ Production Lot ABC has a base cost of $100 and a Transfer transaction is posted to a ‘To Site’ Production Lot DEF, then the ‘To Site’ Production Lot DEF would now have the same base cost of $100. If the Transfer transaction is subsequently voided or corrected, we will not remove the base cost of Production Lot ABC or Production Lot DEF.
Purchasing
NS-5251 Vendor Checks displayed wrong Journal Line Type and Account Source
Vendor check’s journals were displaying a fisherman related Account Source and “Settlement” Line Type on the Journal Details page. This was strictly a display issue that didn’t affect any financials. Nevertheless, we updated the Journal Details page to display the Vendor Accounts Payable Account for the Account Source and “Payable” for the Line Type.
Sales
NS-5858 Sales Order Ship To lookup failed to support Inactive Address Types
Previously when an address used on a sales order was inactivated, we were no longer displaying it in the ‘Ship To’ field on the sales order record view. We’ve now made it so that once a ‘Ship To’ address is saved on a sales order, it will always display regardless if the status is subsequently set to inactive.
NS-5874 Removed ability to delete Workflow step assigned to a sales order
We were allowing users to delete workflow steps that were assigned to a sales order. Occasionally, this caused the orders to not display in the list view or the header fields to be disabled in the record view. While it’s sometimes fun to pull the rug out from under something and see if anyone notices, NorthScope will now be prompt users with a friendly error message when attempting to delete a workflow step that is assigned to a sales order.
Note: A datafix is also included to identify orders that exist without a valid workflow step so that these can be updated to a valid step or removed from the workflow before processing.
Technical Changes
Please view cumulative schema changes here.