Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parameter MessagingExtensionQuery always returns just first CommandId from manifest #11727

Open
ChetanSharma-msft opened this issue Oct 25, 2024 · 4 comments
Assignees
Labels
bug teams-developer-support Question related to extensibility (Bot, ME, Tab) would be marked under this label

Comments

@ChetanSharma-msft
Copy link
Collaborator

Steps to reproduce

Copied from: microsoft/botbuilder-dotnet#6465
Posted by: @harald-thoenig

I'm using Microsoft Bot Framework V4 SDK to create a messaging extension bot.

I created two commands (searchQuery, processQuery). I would like to call up a configuration page for each command. The problem is that the MessagingExtensionQuery parameter in the OnTeamsMessagingExtensionConfigurationQuerySettingUrlAsync event always returns just the first command Id, I entered in the manifest.

I would have expected that when I click on the 3 dots to open the configuration page, the respective ID of the command would be passed to the event.
image

image

Messaging extension bot
ConfigurationPage
Manifest

Hope you can help.
regads

Expected behavior

I would have expected that when I click on the 3 dots to open the configuration page, the respective ID of the command would be passed to the event.

Actual behavior

I created two commands (searchQuery, processQuery). I would like to call up a configuration page for each command. The problem is that the MessagingExtensionQuery parameter in the OnTeamsMessagingExtensionConfigurationQuerySettingUrlAsync event always returns just the first command Id, I entered in the manifest.

Error details

No response

@ChetanSharma-msft ChetanSharma-msft added the teams-developer-support Question related to extensibility (Bot, ME, Tab) would be marked under this label label Oct 25, 2024
Copy link
Contributor

Hi ChetanSharma-msft! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

@sayali-MSFT
Copy link

@harald-thoenig-Thanks for reporting your issue.
We will check this at our end and will get back to you.

@sayali-MSFT
Copy link

@harald-thoenig-We are able to repro that issue, We have raised bug for the same. We will inform you once we get any update.

@sayali-MSFT
Copy link

@harald-thoenig- We received a response from the engineering team, who informed us that the canUpdateConfiguration property in the bot's manifest enables the settings menu. This property is applied at the bot level rather than on a per-command basis.
Reference document-https://learn.microsoft.com/en-us/microsoftteams/platform/resources/messaging-extension-v3/create-extensions?tabs=typescript#declare-your-message-extension

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug teams-developer-support Question related to extensibility (Bot, ME, Tab) would be marked under this label
Projects
None yet
Development

No branches or pull requests

3 participants