microsoft / microsoft/PowerPlatformConnectors

[BUG] Microsoft Bookings Connector Trigger - Dropdown Custom Question: No 'Answer' Field

Open
#2,918 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Certified Connector

Name of Connector

Microsoft Bookings

Describe the bug

When an appointment is made in bookings, the trigger no longer provides the 'Answer' value for multiple choice questions. It passes a 'selected option' integer and an array of the choice options, however up until now we have used the more convenient 'Answer' string without issue.

Was this an intentional change or a bug? I need to know whether I need to rework all of our bookings flows to accommodate this.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 3 - Minor issue

To Reproduce

Create an appointment with a custom multiple choice field, the trigger will no longer have an 'Answer' for that field.

Expected behavior

An 'Answer' string that gives the selected value.

Environment summary

Power Automate Cloud Flow

Additional context

I can't find documented changes for this connector.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is named. Start by reproducing the Microsoft Bookings trigger with a custom multiple-choice question and inspect the connector definition and related tests; done means the trigger again exposes the selected value as an Answer string, or the documented behavior is confirmed as intentional.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.