Skip to content

fix: naming error on aad_object_id for TeamsChannelAccount#300

Merged
lilyydu merged 3 commits intomainfrom
lilyydu/fix-organizer
Mar 3, 2026
Merged

fix: naming error on aad_object_id for TeamsChannelAccount#300
lilyydu merged 3 commits intomainfrom
lilyydu/fix-organizer

Conversation

@lilyydu
Copy link
Collaborator

@lilyydu lilyydu commented Feb 27, 2026

Copilot AI review requested due to automatic review settings February 27, 2026 22:01
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a field naming error in TeamsChannelAccount, renaming object_id to aad_object_id to correctly match the Microsoft Teams Bot Framework API's aadObjectId JSON field. The CustomBaseModel alias generator converts aad_object_id (snake_case) to aadObjectId (camelCase) for JSON deserialization/serialization, which aligns with the official .NET SDK documentation.

Changes:

  • TeamsChannelAccount.object_id renamed to aad_object_id, aligning it with the aadObjectId Teams API field and matching the existing Account.aad_object_id field naming convention.

@lilyydu lilyydu merged commit 691fb10 into main Mar 3, 2026
7 checks passed
@lilyydu lilyydu deleted the lilyydu/fix-organizer branch March 3, 2026 22:10
lilyydu added a commit to microsoft/teams.ts that referenced this pull request Mar 17, 2026
- property was incorrectly named `objectId` instead of `aadObjectId`,
field was being dropped during serialization when the `meetingEnd` event
was triggered

- schema that we are using:

https://learn.microsoft.com/en-us/dotnet/api/microsoft.bot.schema.teams.teamschannelaccount?view=botbuilder-dotnet-stable

- equivalent python fix: microsoft/teams.py#300
- dotnet has it correctly set

Co-authored-by: lilydu <lilydu+odspmdb@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants