Forum Discussion
Webinar calendar invite shows an invalid join link when viewed in Outlook 2016
- Jun 18, 2021
stinarap No worries. I ended up reaching out to Premier support and an engineer informed me that Microsoft is aware of this issue:
It looks like there's already momentum on this. It's a known issue that Apple calendar, Google calendar and Windows 10 native mail app do not support rich text .ics content. The reason this is an issue is that the webinar link is trying to use rich text .ics context, which replaces that join link variable with the actual join link. The big issue that is causing traction is that this was identified on our Outlook 2016 software as well.
There is a pull request in right now on the backend, I don't have a timeline, but it appears that this has been getting traction since it was identified on the 4th.
I found the same issue with Google Calendars. I was told the solution was to install a Teams Add On. But that's not a viable solution for external attendees. The webinars should include a downloaded calendar file for the most common used calendars. Sorry this answer will not work for your solution.
- BShipeJun 18, 2021Iron Contributor
stinarap No worries. I ended up reaching out to Premier support and an engineer informed me that Microsoft is aware of this issue:
It looks like there's already momentum on this. It's a known issue that Apple calendar, Google calendar and Windows 10 native mail app do not support rich text .ics content. The reason this is an issue is that the webinar link is trying to use rich text .ics context, which replaces that join link variable with the actual join link. The big issue that is causing traction is that this was identified on our Outlook 2016 software as well.
There is a pull request in right now on the backend, I don't have a timeline, but it appears that this has been getting traction since it was identified on the 4th.- jaiwsvJul 27, 2021Copper Contributor
- BShipeJul 27, 2021Iron Contributor
Yes, I've been receiving regular updates on this item. Last week's communication indicated that the fix was "expected to be pushed out" but the engineer had no additional updates. They did ask for us to perform testing, so I was planning to do that this week.
I would say to give it a try when time permits (which is what I plan to do as well).