Updating an activity in BotFramework v4 on Teams platform

The key to this is making sure that when you use updateActivity(), you use the right activity ID that is created by the Teams Channel. You also need to make sure that the updated activity gets all of the Teams data set to it.

In onTurn, capture outgoing activities so that you can easily save all of the necessary Teams Channel data:

public onTurn = async (turnContext: TurnContext) => {

    turnContext.onSendActivities(async (ctx, activities, nextSend) => {
        activities.forEach(async (activity) => {
            if (activity.channelData.saveMe) {
                this.savedActivity = activity;
            }
        });
        return await nextSend();
    });

• Note: There might be another way to do this. I just found this to be the easiest, since you need to save all of the channelData, conversation info, and activity.id, at a minimum
• How you store that activity to be used later is up to you. If you store it in the constructor, it will either be re-instantiated on every message (C# SDK) or any user has the ability to change it (JS SDK). You might consider writing custom storage.
• Activities keep all channelData. By specifying a saveMe flag, we ensure we save the right activity

Instantiate some key variables:

const teamsChannel="19:[email protected]";
const serviceUrl="https://smba.trafficmanager.net/amer/";

• Note: the easiest way to get these variables is to send a message from Teams to the bot while putting a breakpoint on the incoming activity
• serviceUrl likely varies by geo region

Send the first activity and store the ID:

// This ensures that your bot can send to Teams
turnContext.activity.conversation.id = teamsChannel;
turnContext.activity.serviceUrl = serviceUrl;
MicrosoftAppCredentials.trustServiceUrl(serviceUrl);

// Add the saveMe flag
yourActivity.channelData = { saveMe: true };

const response = await turnContext.sendActivity(yourActivity);
this.activityToUpdateId = response.id;

• How you store that ID to be used later is up to you. If you store it in the constructor, it will either be re-instantiated on every message (C# SDK) or any user has the ability to change it (JS SDK). You might consider writing custom storage.

Update your saved activity:

// New data
const card2 = CardFactory.adaptiveCard(adaptiveCard2);

// Set the saved activity.id and new activity data (an adaptiveCard, in this example)
this.savedActivity.id = this.activityToUpdateId;
this.savedActivity.attachments = [card2];

Send the update:

await turnContext.updateActivity(this.savedActivity);

• Note: you can update the activity with anything. I swapped out entirely different Adaptive Cards

Before:

After: