OfficeDev / OfficeDev/outlook-dev-docs
Action.InvokeAddInCommand does not open add-ins from browsers
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 99
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
This is a code part, which should open the add-in by its ID.
{
"type": "Action.InvokeAddInCommand",
"title": "${replyWithOutlookAddInButton.label}",
"addInId": "${replyWithOutlookAddInButton.addInId}",
"desktopCommandId": "msgReadOpenPaneButton",
"isEnabled": true,
"isPrimary": false,
"tooltip": "${replyWithOutlookAddInButton.tooltip}"
}
Add-In gets opened via Outlook Desktop only, but nothing happens on button click via Outlook Web (tested in Chrome and Edge).
The example is made by this article.
Expectation: should open the relevant Add-In from browsers and the desktop client.
Please, advise
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: b948883f-055a-1e6a-791d-84338fc437a5
- Version Independent ID: 62b37158-dc1a-bfbe-d7ff-ba1963de950c
- Content: Invoke an Outlook add-in from an actionable message - Outlook Developer
- Content Source: docs/actionable-messages/invoke-add-in.md
- Service: outlook
- Sub-service: o365-connectors
- GitHub Login: @jasonjoh
- Microsoft Alias: jasonjoh
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/actionable-messages/invoke-add-in.md and compare its documented behavior with the linked Invoke an Outlook add-in article. Reproduce the example in Outlook Web using Chrome or Edge and in Outlook Desktop, then determine whether the documented browser behavior or the Outlook product behavior needs correction; done means the expected support is clearly established and reflected in the issue or documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100