Good morning, thanks for your question. This is an interesting scenario which we may not be able to answer today, but lets get a conversation going and see where it leads us.
There are a number of ways that this can be addressed, all with different benefits and tradeoffs. Most importantly the question must have a simple solution or it won’t work well in practice.
Does this scenario only relate to calls (and events) or would other activity types frequently fall into this situation too?
It is important to note that at the “top level” the contact is already related to the blog (there is an association/link between the two). So although the call data is not displayed on both pages it is only a click away currently.
Some ideas:
1) when entering a call from a blog ask for WHO and copy it to the contact record, when entering a call from a contact ask for WHAT and copy it to the blog (copying data is something we normally avoid, creates duplicates in some views e.g. calendar, inconsistent data when edited)
2) add an option to show related contact activities on the blog page (clunky design/interface, that’s what the related-to link is for)
3) add a “related to” feature to the activities which would keep the activity (call or event) attached to its parent e.g. in this case the blog, but have it appear in any related to items as well (makes the system much more complex and a bit slower)
Also, we always ask the question “is this a scenario where the technology should provide a response or is it best addressed by standardizing a process?“
