Issue -

When reporting from the phone call exported data the to and from fields contain the same guid as the phone call itself instead of the guids of the chosen lookup records.

Ask -

Yes we ultimately did use activity pointers as a workaround but it is extremely slow and taxing sql operation. Is there any reason the To and From fields on the phone call entity are designed this way? In future we should think about storing phone call recipient information in phone call entity table along/instead of activityparty base table.