I need to know if anyone in forum has been able to do dynamics screen pop to the activities/timelines created activity (activitypointer) view instead of contacts?
A clients requirement is that on call connect to agent we need to screen pop a phonecall activity, populated with the callers ANI, agent call routed to ,callers contact, creating this activity and binding to both agent and caller is working fine its trying to pop that activity to agent on call connect that seems to be the issue.
This works fine if I’m screen popping to the contacts or any of the standard listed e.g case,invoice, contract but cannot seem to get it to work for activities
I create a phonecal activity, this I bind to both agent and the caller, this works fine and I can see it in CRM
On my BP screen pop I then do my pop to activitypointer and pass the activity id to the object identifier
Dynamics shows this error instead of the screen pop:
This is a system entity that does not have a main form. Opening a record form for this entity is not supported.
I think this might be a dyamics restriction as error says. But if anyone has had success to screen pop to an activity/timeline, assistance on how it was done would be appreciated
Workaround for now is we create the activity under timeline, we screen pop the contact to the agent, on agent connect the agent will then open the last activity in timeline, update and resolve as that would be the one we created for their current interaction
I was able to find a fix to this, it appears that the activitypointers as described in MSD365 is storage as array as such you cannot create records directly in it, instead you need to create records against related entity view e.g. phonecall, emails, task, appointment, not
Changing my screenpop object type to phonecall instead of activitypointers sorted out my screenpop issue
Client dials CC
On call answer by agent we then present a 365 screenpop
Screen pop to be binded to agent as to and caller as from/regarding as contacts
The screenpop must be directly on the entity view e.g phonecall, so agent just completes rest of the non populated fields, with rest auto populated by BP e.g Subject,from, to,ANI,direction,GUID,InteractionID
I will try to provide the sceanrio/workflow once finalized, but the script below should give you an idea.
This you passing the callers and agents contact id after lookup in D365, this you can use as part of your create or update
-Scenario: Create a phonecall record and pop the record to agent on call answer for them to finalize and resolve
-Workflow: Create a phonecall record when agent resolves/finalise interaction and writeback to D365 the phonecall record, BP follows this approach but they don’t bind the agent from/to instead makes use of the bpattern_agent field to refence the agent that received/dialed the call.
I will provide scenarios for you once done, busy with some changes on my design