Skip to main content

Hi all,

We were using the Description field on Events to document meeting notes with donors. However, we realized that this Description field gets updated in Google calendar b/c we are using the Google sync both ways. This means that donors are able to see meeting/post-interaction notes-which we obviously don't want. Here were my attempts at a solution-none of which have worked. I'd love to hear any recommendations for how you have handled this use case.

1) Create a new long text field on event to move the data-Can't do this b/c SF doesn't allow creation of a custom long text field on the object.

2) Use Notes-difficult to report off of. Hard to see a full list of all interaction notes on an account. Difficult to export/move if needed in the future.

3) Use tasks for the meeting notes using the "comments" field-we can't use tasks as a replacement for events b/c they don't work with the sync/on the calendar. we also can't relate a task to an event record, so the notes would stand alone and basically duplicate each event record.

4) Use a custom object for events or for notes-I can't relate a custom object in a master-detail way on events. This prevents being able to use related lists. The only option was to create a lookup on the event itself. No easy way to link back to the event record from the notes (except perhaps a URL). Impossible to report off of. If I tried to use the custom object for events, I can't use them in sync or add them to the activity timeline.

5) Turn off sync from SF to Google. This means that all notes added in SF wouldn't show back up in the Google calendar invite, preventing invitees/attendees from seeing notes. The only issue is that updates in the description in Google calendar would overwrite the description SF, so no updating the description in Google calendar once notes have been added.

Any thoughts? Recommendations? Help!

11 件の回答
  1. 2024年3月7日 14:33

    @Michael Wray Glad to hear it! I have wondered if, with the push to lighting record pages, we will get the ability to add fields to a smaller side component in addition to the main record detail section. That would of course obviate this workaround. Until then, this is a good one to have in the back pocket.

0/9000