Microsoft Bookings connector doesn't pull across 'CancelReason' information
Hi, When using the "When an appointment is cancelled" trigger in the MS Bookings connector (https://learn.microsoft.com/en-gb/connectors/microsoftbookings/#when-an-appointment-is-cancelled), the 'CancelReason' information does not come across as documented in the Appointment data. Can this please be fixed.
Enable Flow Connector to listen for multiple SMTP addresses
Hi, We have a Bookings page per Sales rep, as they cover territories (US States) which are hard to explain to the customer. However, we found that the flow only works on one SMTP address, meaning that I need to make as many flows as the Bookings pages we have. My idea is to be able to semi-comma separate the addresses in order to bundle the trigger to more pages than one... Or something to that extend. Thanks, Mikkel BellingChange the "Name field" to "First Name" and "Last Name"
Hi, We find it hard to use the new Flow Connector, as "Name" doesn't split the first and last name, which is required by a model-driven app in PowerPlatform. Therefore my idea is to split the field to enable external systems (i.e. Dynamics Marketing) to better handle names. Thanks, Mikkel Belling