Closed tanjoht closed 3 years ago
Rick-Kirkham
commented
3 years ago A Control element can have only one Action child element. I will create an internal bug to make sure this is stated clearly in the documentation. Since this is being tracked internally, I'll close this issue.
tanjoht
commented
3 years ago Thanks for the quick response. For clarity, is this only referring to outlook addins? Or all products? If so, how is the "taskpaneid" used?
<Action xsi:type="ShowTaskpane">
<TaskpaneId>MyTaskPaneID1</TaskpaneId>
<SourceLocation resid="Contoso.Taskpane1.Url" />
</Action>
<Action xsi:type="ShowTaskpane">
<TaskpaneId>MyTaskPaneID2</TaskpaneId>
<SourceLocation resid="Contoso.Taskpane2.Url" />
</Action>That documentation is misleading. Each of those Action elements must be in different Control parents (or different menu Item parents). You can't have 2 different actions in the same button or menu item.
Within a control element block in an office plugin, trying to associate 2 action elements associated with it results in a schema error.
Code:
`
`
Error: This app can't be installed. The manifest file doesn't conform to the schema definition. The element 'Control' in namespace has invalid child element 'Action' in namespace.
Based on the actions element documentation, under the taskpaneId section, it seems to imply that you can have 2 action elements. Although it says that the taskpanid element isn't supported in outlook, are multiple action elements supported in general? I'm trying to have it so that when I click the add in button, it triggers both a "ShowTaskpane" and an "ExecuteFunction" action?
The use case I have is to combine 2 custom vendor add-ins in outlook to support our transition from 1 product to another. Since the web apps behind the plugins are built and supported by the vendor, I have no access to change/update the code
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.