Describe the problem/error/question
iCal after upgrade to 1.6.0 create ical with today’s date and 00:00 and day start time instead of the specified date and hour time
in my case
“start”: “2024-02-27T10:00:00”,
“end”: “2024-02-27T11:00:00”,
i got in iCal:
SUMMARY:Title
DTSTAMP:20240203T120000Z
DTSTART:20240203T000000Z
DTEND:20240227T110000Z
END:VEVENT
END:VCALENDAR
but 2024-02-03 is today’s date
Maybe it because of this fix(core): Allow Date/Luxon objects and additional formats in DateTime validation by elsmr · Pull Request #8525 · n8n-io/n8n · GitHub
What is the error message (if any)?
Please share your workflow
Share the output returned by the last node
Information on your n8n setup
**n8n version: 1.6.0.
**Database (default: SQLite):main
**n8n EXECUTIONS_PROCESS setting (default: own, main):default
**Running n8n via (Docker, npm, n8n cloud, desktop app):Docker
**Operating system:default
Update
[email protected] - not present works as expected
DTSTAMP:20240203T232000Z
DTSTART:20240229T110000Z
DTEND:20240229T130000Z
DTSTART is correct
after 1.30.0 and include [email protected] and with old iCalendar Node:
DTSTART is not correct
Thanks for reporting this @lightcom
I added an issue for the internal team to fix this
All the best
1 Like
update
latest next version 1.31
Convert to File node version 1.1 (Latest)
Screenshot time
DTSTART:20240229T180000Z
DTEND:20240229T200000Z
Real iCal time in result
DTSTAMP:20240229T074300Z
DTSTART:20240229T00 0000Z
DTEND:20240229T200000Z
Erroor is in DTSTART which equal to start of the date, but not particular time
formula is
Start:
{{ DateTime.fromISO($json.date + ‘T’ + $json.time, { zone: $json.tz }).toUTC().toFormat(“yyyyMMdd’T’HHmmss’Z’”)}}
End:
{{ DateTime.fromISO($json.date+ ‘T’ + $json.time, { zone: $json.tz }).plus({ hours: 2 }).toUTC().toFormat(“yyyyMMdd’T’HHmmss’Z’”)}}
update 2 MORE interesting
Event is from 20240305T120000Z to 20240305T140000Z
But in result DTSTART: is 20240229T00 0000Z today’s 00 start of date
DTSTAMP:20240229T074300Z
DTSTART:20240229T000000Z
DTEND:20240305T140000Z
Jon
February 29, 2024, 3:05pm
7
Hey @lightcom ,
I have just checked and this is still in our backlog to be picked up and fixed.
1 Like
It seems the data i get is from previous executions. One workaround is to change it with a code node (after ical creation)
I am doing a similar aproach to change “METHOD:PUBLISH” to “METHOD:CANCEL”. It would be great if the method option could be set on ical node
1 Like
This solution is better than the original because I adapted that solution, and created a unique .ics name generation now for each event, and of course the correct start time for the event