This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 18%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFI%3C/text%3E%3C/svg%3E)
Type: Outlook Add-In
Generated by: Yo Office
Affected Manifest: Unified
Affected version of Outlook: Web, Desktop (new)
Unaffected version of Manifest: XML
Unaffected version of Outlook: Desktop (classic)
An attempt is being made to create an Add-In that allows users to add a required attendee to a meeting. However, the default template does not seem to work well with the ribbon ActionButton "Perform an Action" when using a Unified Manifest. The Task Pane ribbon button and its functionality work fine across platforms.
It is noted that the default behaviour works from an opened email message and not from the calendar, but the default Action ribbon button seems to do nothing in the new desktop client or the web client.
In Outlook (classic), the "perform an action" ribbon button functions correctly:
XML Manifest also performs action correctly in Web version of Outlook:
However, in Outlook (new) and Web, clicking the "Perform an Action" button appears to have no effect, as "Performed action." does not appear, and added logging to the console is also absent.
This is all configured with the default setup of Yo Office for Outlook using JavaScript. The intention is to use the Unified Manifest to support the Teams Calendar in the future, but it seems that the old XML manifest is the only option that is currently working.
Is there a way to modify the Unified Manifest to resolve the issue with the action button from the ribbon?
I ended up solving this by using the XML Manifest instead of the Unified Manifest. There are quite a few issues with documentation for both manifests, the links in the XML manifest for instance does not provide any schema, where the json manifest provides information. It seems quite a few people have reported similar issues going a few years back in time...