When highlighting a cell containing a result (not double-clicking to get the cursor) and pressing delete, rather than blanking out the cell it removes the pupil from the marksheet. If you close and re-open the marksheet the child reappears.
Where this causes a problem is if you have calculations on a marksheet. If you remove a pupil from the marksheet, then press calculate (or click save with the calculate on save functionality selected) I get a 'there is no position at row XX' error and get thrown out of SIMS .net. So it's something to do with the system trying to calculate on a row that has since been removed.
@HannahBuist - Good catch, i just replicated on my setup. It deletes the student and if you hit save, the student comes back but with no grade showing.
Have you reported it yet? I couldn't see it on supportnet, so it must be on your LA side only. Would be nice to have it patched before i go live.
Has anyone had an instance of their SQL database inflating itself to an unfeasible size after this update? One of my primaries SIMS database decided to try and bust out of it's 4GB holding cage and rendered the server unusable.
My test server seems fine. I did put it in simple mode before upgrading though as i did have a massive ldf and mdf. > 10Gb combined.
I might report it then, as need to have it fixed : it's my show stopper
I've logged it with Capita this morning so watch this space.
Ouch, I know staff like to press delete in their marksheets, and they are all set up to calculate on save, so will be waiting for a fix on this one before applying the update.
With a business analyst at Capita.....will keep this thread posted!
Nothing back from my logged call yet, but Chris Sherwood from Capita has updated my forum post with the following:
I am afraid that it cannot be patched.
We are working on a fix for the Summer release.
oh happy days.
Apparently so :-(
Although I haven't heard back from my support call yet so fingers crossed I get a different answer!
I foresee many support calls on this......
HannahBuist (13th March 2012)
Not Hurrah! Quite the opposite in fact!
This was a very minor irritiation compared to having the Upgrade withdrawn mid-deployment!
Neither issue merited a total withdrawal!
Last edited by Sivadam; 13th March 2012 at 01:24 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)