When a meeting type is updated it also resets the meeting description, even though the description does not appear to change. The reset in the meeting description can cause a meeting update to be sent to the meeting invitees.
This seems like a bug and that the system should not perform in this manner. Simply editing a meeting type should not trigger an update to the meeting attendees.
In the interest of maintaining the accuracy of reporting of meetings, meeting types, and outcomes, I would suggest that changing those values should not result in a change to the description, which as mentioned, could result in a re-notification to the attendee, even for a meeting that occurred in the past.
Same goes for updating other meeting info like title, attendees and others! I can't understand that we can't do it without sending external update communication to all attendees....
This is a clearly going to impact adoption here. The inability to change these - INTERNAL - properties (our clients never see it) is counter intuitive. It creates a poor experience for the client.
I hadn't realized this nonsensical setting existing. Updating the deal records and wanted to clarify / update the meetings. Didn't think anything of send update and save button, till I realized it actually was modifying the invite and sending it to invitees. What the heck?
Hi @VCL001 - i should have closed off my comment. On my platform, the setting has changed: if my users edit a "non invite" item like the meeting category or the association, the button will say "save" and no update is sent, AFAIK. Changing attendees or the content of the invite, OTOH, will make the button say "Save and update"
I'm not sure if the change is general or if there is a rollout, or a beta ...? You may want to check and then maybe ask your CSM?
