page_type | description | products | languages | extensions | contentType | createdDate | ||||
---|---|---|---|---|---|---|---|---|---|---|
sample |
Demonstrating the feature of typeahead search (static and dynamic) control in Adaptive Cards. |
|
|
samples |
24-12-2021 23:30:17 |
This sample shows the feature of typeahead search (static and dynamic) control in Adaptive Cards.
Use the bot command staticsearch
to get the card with static typeahead search control and use bot command dynamicsearch
to get the card with dynamic typeahead search control.
Static search:
Static typeahead search allows users to search from values specified within input.choiceset
in the Adaptive Card payload.
Dynamic search:
Dynamic typeahead search is useful to search and select data from large data sets. The data sets are loaded dynamically from the dataset specified in the card payload.
Dynamic search results:
On Submit
button click, the bot will return the choice that we have selected.
In Azure portal, create a Azure Bot resource.
- Ensure that you've enabled the Teams Channel
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
In the folder where repository is cloned navigate to
samples/bot-type-ahead-search-adaptive-cards/nodejs
-
Install node modules
Inside node js folder, open your local terminal and run the below command to install node modules. You can do the same in Visual Studio code terminal by opening the project in Visual Studio code.
npm install
-
Run ngrok - point to port 3978
ngrok http -host-header=rewrite 3978
-
Open the
.env
configuration file in your project folder (or in Visual Studio Code) and update theMicrosoftAppId
andMicrosoftAppPassword
with your app's base url. (Note the ClientId is the AppId created in step 1 (Setup for Bot), the ClientSecret is referred to as the "client secret" in step 1 (Setup for Bot) and you can always create a new client secret anytime.) -
Run your app
npm start
-
Manually update the manifest.json
- Edit the
manifest.json
contained in theappPackage/
folder to replace with your MicrosoftAppId (that was created in step1.1 and is the same value of MicrosoftAppId in.env
file) everywhere you see the place holder string{MicrosoftAppId}
(depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json
) - Zip up the contents of the
appPackage/
folder to create amanifest.zip
- Upload the
manifest.zip
to Teams (in the left-bottom Apps view, click "Upload a custom app")
- Edit the