NorthScope 2021.11.05
(Software Version: 2021.11.05 Database Version: 2021.11.05)
Release Date: November 5th, 2021
Improvements
Fisherman Accounting
NS-5703 Converted the Ticket Line Stat Area History inquiry to NS 3.0 Framework and improve performance
It’s no question that this inquiry needed help. We gave it the help it needed by converting it to the new NS 3.0 Framework and have drastically improved performance.
Sales
NS-9086 Added Freight Terms to the Sales Transaction list view and Sales Transaction History inquiry
Freight Terms was added to both the Sales Transaction list view and the Sales Transaction History inquiry. This column is not displayed by default.
Note: Any custom layouts should be recreated for these pages, otherwise the column will not be available.
NS-8984 & NS-6503 Updated the Address tab in the Customer record view to contain both outside and inside salesperson columns and update salesperson labels across all Customer Address pages
It can be said that there are two types of salespeople in the world, inside sales and outside sales. NorthScope agrees with this line of thinking and as such, supports both a property for inside salesperson and outside salesperson. Except when it doesn’t… This was the case with the Address tab in the Customer record view, but no longer is this a problem because we went ahead and made sure that everything is consistent. Now the Customer Address record view Properties tab has both “Salesperson – Outside” and “Salesperson – Inside”. We didn’t stop there though, we updated the Addresses tab on the Customer record view to match, along with the Addresses list view.
Bug Fixes
Fisherman Accounting
NS-8426 Splitting Fish Tickets did not split taxes with fixed rates
When splitting a fish ticket, part of the expectation is that fixed rate taxes applied to lines that are being split will split along with the line percentage. This is now working as expected. If you split a fish ticket line for 50% then the weight and the fixed rate tax will both be split between the original and newly split ticket by 50%. This bug had no impact on repricing or correcting tickets.
NS-9078 Fish Tickets with multiple of the same item were causing duplicates on the Fish Ticket Item inquiry
Fixed a bug where Fish Tickets that had multiple of the same item and were corrected/repriced would display twice.
NS-9090 Opening Process Payments would not open to the correct user’s batch
When clicking the Process Payments button from the Fisherman Balances screen it will once again open the most recent batch that you created.
Inventory
NS-8952 Item Copy page had unfriendly message
When users attempted to copy an item and they filled everything correctly they were greeted with an unfriendly message stating that “XMLFormat” was not a parameter. We don’t expect anyone to know what that means, so we went ahead and fixed things up in order for you to copy items to your hearts content.
NS-8992 Users were unable to activate / inactivate items
Updating an item to be active or inactive should be an easy task. However, it was found that changing and item to inactive / active, would revert to the original state. This was no good, so now you can go back to activating and inactivating items as you once were able to.
Purchasing
NS-9090 Opening Process Payments would not open to the correct user’s batch
When clicking the Process Payments button from the Vendor Balances screen it will once again open the most recent batch that you created.
Sales
NS-8948 Added back the Auto Allocate By? preference
With the release of Sales Order, we removed the Auto Allocate By? preference which seemed to be a safe thing to do given the Auto Allocate button’s demise. It turns out we were wrong, and this broke the Allocate by Warehouse Lot page. So, we went ahead and added it back.
NS-8948 Quick Sales Lines Inquiry displayed incorrect item description
Previous to this week’s release, the Item Description column was displaying the inventory item Description and not the Description saved by the user on the transaction’s line item.
NS-9119 Creating a new Sales Order with a transaction class that had special characters in the name would not work properly
Sales Transactions are easier to create than ever before… unless you have a special character in the transaction class name. This was causing issues when navigating to the select ship to page. However, we have tracked down this pesky bug and squashed it so you can have as many special characters as you’d like in your transaction classes.
NS-8964 Fixed the Purchase Order validation on Sales Orders to only display once
In Sales, there is a preference on how to handle duplicate PO Numbers. This preference gives you the ability to allow them, warn about it, or not allow it. When this was set to warn, users would see an error message displaying that a previous order has the same PO Number for the customer. This was displaying multiple times based on however many orders had the same PO Number and it would display every time you saved. This has been resolved and will only display the message one time.
NS-9136 Changing the Customer on Sales Orders then immediately saving the Sales Order would hide items
If you opened the change customer page, selected a new address, clicked Save & Close, then clicked the Save button on the Sales Order record view, items would appear to disappear. This was due to a bug where the address would revert to the previous address while maintaining the new customer. Now that we have tracked this down, we have fixed the problem and you can confidently change customers again. Additionally, while we were there, we noticed that error messages weren’t being displayed correctly on the Change Customer page, we fixed this too.
NS-9144 Missing Price UOM error was displaying incorrectly on the Find Items screen
In specific circumstances, when adding an item from the Find Items and Find Items with Balances pages, you would see a Price UOM filled in and yet still receive an error stating that the Price UOM was missing. This was due to not using price lists and customer favorites, which should be something you can do. We have fixed this issue and if you don’t have price lists or customer favorites, the page will default the item’s price uom and the error message will no longer display incorrectly.
Technical Changes
- No schema changes.
- No config file changes.