hiphopamus

"Recorded by" is an available field in the reporting engine, you could report on the attendance marks to see which user recorded the original mark.

They have probably picked the address from the matched list rather than creating a new one, if you edit one and the other one changes this is what happened. To resolve it you will have to delete the address from one record and add the address again making sure that you pick "New" to create a new record.

It can be due to you logging in with a different account to the one that installed SOLUS 3 originally, you have to make sure that the user has full rights to all files in C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys

There are KS2 fine level calculator templates available from Capita via your SIMS support team, this allows you to import the CTF from NCA tools or Key to Success and then calculate in SIMS.net.

That sounds like quite a large number of columns, does all the data need to be on one template? would it be better served across different marksheets? when the marksheet loads it is having to retrieve the results from the background database for all columns so you will find it take a while, especially if you are pulling data for the whole year.

How many columns (including hidden columns) are there on the template?

If you want a pure csv output you could create the report from the Groups focus and filter a sub report count of students by PP and filter the groups by group type equals Year Group.

Try using the analysis report output with Year Group and PP as the rows and columns.

A quick report on attendance/lesson marks with adjustable filters does the trick.

"Recorded By" is an available field in the SIMS reporting area if you wanted to create your own report to investigate.

You could make them inactive if you want to tidy your group list.

We have noticed a lot of 3rd party software in our schools are extracting more information than required, schools will have to query this with the companies involved to establish what is being extracted and for what reason. This is also an issue with the permissions granted to 3rd party user accounts created in SIMS, I have raised the issue with schools numerous times where they are asked to give personnel officer access to software that doesn't need contract information. With GDPR looming schools really need to get an understanding about who has what access to their data through user accounts and extracted data.

Might be an obvious thing to check but is their inbox full? sometimes this can stop staff receiving messages.

The easiest way to do this is to edit the font on the result tag to be "hidden" and then the text will not appear but the background will be coloured in.

@lukefrost you should be able to get help from your Sims support team, I know that we've been moving our schools to 2012/2014 for a while now..

You could make use of SIMS discover to create Discover groups which can message members of staff as the pupils hit certain points boundaries. It will also allow you to use the group for reports and homepage widgets.

I am not aware of this fix, I know the patches have worked at our schools.

Your support team need to release the patches on Solus 3, if you are with us I think we have released them already. Check your update library.

As far as I am aware the Summer release is the first upgrade which no longer supports SQL 2008.

There is the following from Capita: "05/07/2017 - (England, Wales and Northern Ireland) On demand Patch 23172 and 23173 released We have received some calls from customers who have experienced some issues when upgrading their SIMS database to the Summer release. The error message presented is: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation. To overcome this problem, customers are advised to apply patch 23172 to change the properties of the tables affected, then apply the Summer upgrade. Once the upgrade to Summer has been successfully applied, customers are then advised to apply patch 23173 to set the properties back to ensure the related applications work. Steps have been taken to ensure this does not happen in the Autumn upgrade." Not sure if this is relevant for you or not...

It's worth waiting, re-registering will establish whether you are connecting to the SOLUS servers.

It can help re-registering your site in the SOLUS 3 console, you will need to know your SOLUS 3 site password to do that though.

05/07/2017 - (England, Wales and Northern Ireland) On demand Patch 23172 and 23173 released We have received some calls from customers who have experienced some issues when upgrading their SIMS database to the Summer release. The error message presented is: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation. To overcome this problem, customers are advised to apply patch 23172 to change the properties of the tables affected, then apply the Summer upgrade. Once the upgrade to Summer has been successfully applied, customers are then advised to apply patch 23173 to set the properties back to ensure the related applications work. Steps have been taken to ensure this does not happen in the Autumn upgrade.

There is an issue that is apparently very rare, the upgrade fails and should roll back to the Spring upgrade, although the one school we have had with it went into restricted user mode in SQL. There is a patch to run before the upgrade and one to run after to avoid the issue.

The attendance panel on the homepage can show absences for today if you click on the toggle option in the panel.