Thread Starter
osix25
(@osix25)
I’ve partially diagnosed this for you in that the .ics files you are producting don’t have a TZID parameter in them which they should and they specify UTC by adding a Z on the end of the date/time info but don’t manipulate the entered info correctly to match this.
Is there an email address I can upload the file you produced which sets an calendar event 22 hours too late and the modified version from me which works correctly so you can see what needs changing??
It sounds to me like you’re trying to make a generalised product fit exactly how you’ve always worked rather than coming at the problem from a different angle. My take would be to define a service period and let the user string service periods together to make long or short service slots which with a resource of one would automatically ensure you couldn’t be double booked.
