This content has been marked as final. Show 1 reply
Generally not that way. We don't have any method for coping activity like that. However, sometimes you can have one primary record and duplicates without much activity used for that portal user- e.g. just creating that if you need it, not emailing it, and trying to mostly not put activity on that record.
At a high-level, I'd try not to implement this ;)
Failing that, I'd really recommend getting a consultant's (ours or someone independent) help in thinking through this- it gets pretty complex once you start trying to manage duplicates.