Jump to content

Recommended Posts

Posted

So I've had a look through here at the various methods through which people have been forcing SIMS timetables into Outlook.

 

And thought "I'm going to test PARS' diary export function instead". And it produces a usable .ics that imports fine into Outlook 2007.

 

However, when said Outlook/Exchange calendar is synced with an iPad, the timetable doesn't get pulled in. Events created in Outlook 2007 get pulled in fine and events created on the iPad get pushed back up to Exchange without issue.

 

So I suspect that the PARS/Microsoft-based .ics export is missing something that makes it iPad-friendly after reading around that in general the iPad chokes on Microsoft .ics files, but handles others fine.

 

Anyone know what the difference is?

 

(I'm well aware I've strayed outside the realm of MIS, but I'm hoping another PARS user has run into this).

Posted
Could you export from outlook to another format. Perhaps go out to google and back, or something intermediate. Or just do a straight export / copy to another calendar and test that.
Posted

Update: it copies items from the School Diary in SIMS (Y8 Hockey Trip in Wensleydale). But it doesn't copy timetabled lessons.

 

I'm reluctant to set a precedent of syncing MIS data (even one step removed) to Google and I'm waiting on a Tasc ticket. It appears to be a case of "known issue, needs to be shoved through something else to work (i.e Google)", but I'm hoping to just write a script to parse and fix the broken bits.

Posted (edited)

Right, got this sorted.

 

When PARS creates the UID: field for an event during the .ics export, it populates every UID as UID:-1. This isn't an issue in Outlook, but an iPad appears to assume (because UIDs are the same) that all events are the same and only imports the last event.

 

Searching and replacing the UID field so it increments/is unique for each event and then importing the modified .ics makes events go across without issue.

 

Vim method

 

:let i=1|g/UID:-1/s//\=”UID:1”.i/|let i=i+1 

 

Tested with a couple of hundred events across two calendars.

 

Fix will also be in PARS 5.561

Edited by pete
  • Thanks 1
Posted

It's worth noting that the RFC for the iCalendar spec strongly suggests UIDs should be unique (at least within the same file) and ideally fully unique (since if you were sharing calendars, you might get wierd UID clashes).

 

I suggested timestamp+randomnumber as the UID field to Tasc - since it takes very little time to generate, timestamp alone would lead to dupes.

 

If I has to scale this past 5 users, I'd amend my method to sling a randomly-generated hash into the UID. Something like [email protected] which would avoid issues for UID clashes.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...