HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
>> see also NTS-I-1453
And also, let the importer understand ...
... valid ICS files
... the previously exported ICS files from an Notes Calendar entry
... ICS files with recurring meeting series
... timezones, that are specified in the ICS files
This is one of the numerous stupid bugs I stumbled upon this year in this tinkered product. And I am losing faith that this will change any day.
Beginning with the unfinished terror-ware called AppDev-Pack, the never working LotusScript-Objects for reading JSON, the stoneage problems with 64k limitations, the breaking formatting on collecting RT-Items into one, the does-not-work-with-this-version of the REST-API implementation for calendars, the implementation of DXL exporting / importing (by destroying documents), ... and now this one on importing valid ICS files (by strict using the given documentation here: https://www.rfc-editor.org/rfc/rfc5545) - either with the NotesCalendar object, or the import function via the Notes Cient (File > Import > ICS file).
This problem was reported two and a half years ago. Nothing has changed. HCL keeps the focus to bloat the product with more of the same unfinished tool box accessories.
But the problem isn't only with HCL. It is also with the most developers in this universe. No impetus to question and improve existing program parts. "That has worked for the last transillion years, why should we change it."
No insight that performance, usability, accessibility, user acceptance are also part of success. Instead, users and developers continue to be tortured with an old-fashioned system landscape and more of the already existing festering heads are added to it.
It is ludicrous to state basic essential functions as "under consideration", when they are not implemented correctly.
Dito!