I have noticed that the Last Meeting Booked property or ‘engagements_last_meeting_booked’ (Which is used by the meetings calendar to record when a user selects a time and date in the calendar) is still locked through the API and cannot be read or wrote to.
We use multiple calendars within our company and require this property to be accessible through the api so external code can check when a meeting has been booked and create a callback event.
I asked a similar question to this a year ago and I was told that this property would be unlocked soon and be available.
As a simple work around I created a property through the contacts API with the same date object type as the Last Meeting Booked property. I then created a workflow which listens to Last Meeting Booked and copies its value to this property.
But this custom property, created through the API, is also inaccessible.
So my question is: Is the last meetings book property still locked? Is there a way around this? Are custom properties created through the API also unreadable through the Contacts API? Or is it because both properties are of the same date type.
Thanks for any help you can provide,