NorthScope 2025.12.11
(Software Version: 2025.12.11 Database Version: 2025.12.11
Release Date: December 12th, 2025
Improvement
Financial, Fisherman Accounting, and Sales
NS-10596, NS-12073, NS-13457 - UI Upgrades: Key Sales and Financial Screens Got a Makeover (and Ditched Some Old Baggage)
A handful of NorthScope screens have been dragged—kicking and screaming—into the modern era. They’ve officially joined the NorthScope 3 Framework, which means they look better, run faster, and no longer rely on the dusty old XML clutter that’s been hanging around since who-knows-when.
Here’s who got the glow-up:
Quick Sales List View
Quick Sale Record View
Fisherman Sale and Tender Resale List View
Fisherman Sale and Tender Resale Record View
Journal Details
While upgrading, we tossed out extra layout junk, switched everything over to the shiny new APISave JSON format, and cleaned up a few weird behaviors along the way.
A few notable improvements from the Quick Sale Record View:
Field lengths have been fixed so your data stops getting awkwardly chopped in half.
New lines no longer assume a Quantity of 1 (NorthScope finally learned not to jump to conclusions).
Fields got rearranged for a more logical flow through the transaction screen.
You can now resequence transaction lines without the usual finger gymnastics.
In short: same screens, less nonsense. Faster loads, cleaner layouts, and fewer reasons to mutter at your monitor.
Fisherman Accounting & Grower Accounting
NS-13193 - Tickets: One Database Standard
Behind the scenes, NorthScope’s ticket pages were speaking slightly different dialects when it came to fetching header and line data. Some used old select procedures, some fired unnecessary drop-down events, and overall things weren’t as tidy (or efficient) as they could be.
We’ve standardized the process so we have a consistent approach for these types of database queries:
Grower Accounting Tickets now use the new SPx_CPSEL_GetTicketHeaders and SPx_CPSEL_GetTicketLines procedures. This also eliminates stray drop-down events, since all the needed info is returned up front.
Fisherman Accounting Tickets now use updated “Get” procedures for both header and line data, which are now used on the Fish Ticket List Views, Inquiries and Record View.
The end result: cleaner, standardized data retrieval across ticketing, fewer unnecessary events, and a framework that’s easier to maintain moving forward.
Framework
NS-13257 & NS-13265 - Making NorthScope Feel Faster (Without the Nerdy Details)
This one’s deep in the “you probably don’t need to know how it works” category. We did a bunch of behind-the-scenes cleanup to reduce how much work NorthScope’s pages do on the main thread—the part of the system that orchestrates everything moving on your screen. In addition to that work, we also optimized screens that have grids that don’t display any toolbars. The changes involve rethinking how pages refresh, save, and handle data updates, but the short version is this:
NorthScope should just feel faster now. Pages load more smoothly, buttons respond more quickly, and you’ll spend less time waiting for the user interface to catch up.
All the technical wizardry lives under the hood—you just get the benefit of a snappier, more responsive experience.
System
NS-11279 - System Logs: No More Space Hoarders
NorthScope’s web application had a habit of over-shar... err... logging. By default, it was generating mountains of logging data that almost nobody ever used—but that happily gobbled up server storage until you either took the system offline to purge it or managed to find more disk space. Not exactly a graceful setup.
We’ve reined it in:
Excessive error logging is no longer generated by default, though you can still re-enable it if needed.
The infamous Traces.svclog file will stop showing up on new installs and won’t be populated on existing ones (though we’re not deleting it automatically).
The system preference for “Number of days to purge save log after” has been updated to a more realistic 30 days instead of 3, so useful logs stick around just long enough to be useful without turning into squatters.
End result? Cleaner servers, fewer headaches, and logs that mind their manners.
NS-13048 - Logouts: From "What the Heck?!" to "Your Session Has Expired"
For too long, NorthScope had a habit of kicking users out without so much as a “goodbye.” One moment you’re working, the next you’re staring at a login screen, wondering if you clicked the wrong thing, broke the system, or just offended the server somehow. The root of the problem: NorthScope can’t know exactly when the web server underpinning everything will decide to expire a user’s authentication cookie, and the browser keeps that info locked up tighter than Fort Knox.
Here’s what’s new:
When your session actually expires, NorthScope now catches it cleanly, syncs up both sides (SQL and Web), and brings you back to the Login page in a tidy, predictable way.
You’ll get a clear “Your session has expired” message inside the normal UI, rather than an unexplained boot or a funky error message. Once you acknowledge it, the full login screen appears—no confusion, no mystery.
In short: sessions still expire (that’s life), but now NorthScope explains what happened, keeps your data safe when possible, and guides you back to the login page like a polite host instead of a trapdoor.
Bug
Financial
NS-13473 - Batch Posting: Journals That Reflect Reality (Not Ghosts or Old Dates)
Two gremlins, fixed at the same time:
First, if you delete a payment from a batch before posting, it was still sneaking into the journal entry like an uninvited guest. That’s over. The posted journal now includes only the payments that actually exist in the batch at the moment you post—no ghosts.
Second, the journal date sometimes clung to a temporary date you set earlier (end-of-month, anyone?), even if you changed the batch date before posting. Now the journal date always matches the active batch date at posting time. Interim date placeholders won’t leave fingerprints on the final journal.
Net effect: journals that reflect what you actually posted, when you posted it. Radical, we know.
Framework
NS-13429 – Grid Display: Banishing the Jumpy, Partial Scrolling
Some NorthScope grids had a bad habit of jumping and jittering while you scroll or, even worse, cutting off data before showing every item—like a magician who never finishes the trick. We dug into the issue and found the culprit buried deep in how page scrolling and grid rendering were handled.
Without dragging you through the technical weeds, here’s the simple takeaway:
Grids now smoothly displays all items on screen, no matter how long the list or if grid grouping is enabled.
The scrolling behavior has been refined so performance stays smooth while you navigate large datasets.
It’s a small, nerdy change with a big payoff—you’ll see all your data at once, without grids getting shy halfway through the list.
Technical Changes
Please view cumulative schema changes here.
No config file changes.