JQuinn

For anyone still interested or affected by this: Latest from Groupcall: "When an MIS makes changes to how data is displayed within their system we must release an update to support those changes. In this instance we weren’t made aware of the changes until affected schools reported them to us, however, I’m now pleased to confirm that the development work with iSAMS has been completed and the underlying issue has now been resolved and the data will automatically sync within the next 12 hours. Could you please review the data tomorrow once the sync has completed and let us know if you encounter any further issues or discrepancies? Thank you for your patience and understanding while we worked to resolve this matter with iSAMS." The latest fix is syncing data, but the weeks are out of sync if you have multiple week timetables, so not there yet. Groupcall still blaming iSAMS, iSAMS still blaming Groupcall...

Its interesting that schools with other MIS's are reporting the same issue, as GroupCall have been adamant that the fault lies with iSAMS and have actively encouraged schools to raise a support ticket with them (iSAMS). I cannot believe that a timetable sync issue has taken this long to (not) resolve, whoever the fault lies with! It's been over a half-term so far.

Just an update for any still affected by this. I have been assured that Groupcall and iSAMS dev teams are now talking to each other to fix the issue (Groupcall are blaming iSAMS). Groupcall are asking all affected iSAMS schools to raise an iSAMS support ticket, however when you do this it appears the iSAMS support team aren't aware of the broader problem and are asking for api details, etc before they'll investigate. It's only taken 6 weeks to come such a long way... 😐

Adding to this, 4 weeks in and still an outstanding issue. Groupcall are blaming iSAMS but there's no problem with the timetable data sync'd via Wonde... Our Frog (yes I know) and SatchelOne are affected.