Pipedrive Integration V18

[ITB_CH]

Hi all

we have used the pipedrive custom integration by mark philips for long time with v16 at it was working perfectly.

Since the update to V18 the call journaling is NOT working anymore!

can anybody assist?
I saw that many have this problem but no solution is around until now! Would be great to have it also working with the new V18!

thanks in advance and BR

 

[LEAD]

We are having the same issue but with Dynamice On-Premise. It is not passing certain variables as they have changed something on the backend

 

[edossantos]

Hello @ITB_CH, @LEAD,

The adjustments that need to be done to the template to make it work with v18 are very simple:
1) The contact lookup (empty Id) and contact creation (Id="CreateContactRecord") scenarios MUST return 2 new outputs: EntityId and EntityType. For example:

<Output Type="EntityId" Value="[ContactId]" />
<Output Type="EntityType" Value="Contacts" />

These values will be stored in the 3CX Contact created in the global phonebook when the contact is synchronized from the CRM to 3CX.

2) In the Call Journaling (Id="ReportCall") and Chat Journaling (Id="ReportChat") scenarios, you can't use the old [Contact::XXXXXX] variables. You have 2 variables [EntityId] and [EntityType] which you can use to create the call or chat activity associated to the matched contact. These variables will contain the value returned during contact lookup or contact creation.

Just doing these 2 changes should be enough to get the integration working again.

 

[LEAD]

Hello @ITB_CH, @LEAD,

The adjustments that need to be done to the template to make it work with v18 are very simple:
1) The contact lookup (empty Id) and contact creation (Id="CreateContactRecord") scenarios MUST return 2 new outputs: EntityId and EntityType. For example:

<Output Type="EntityId" Value="[ContactId]" />
<Output Type="EntityType" Value="Contacts" />

These values will be stored in the 3CX Contact created in the global phonebook when the contact is synchronized from the CRM to 3CX.

2) In the Call Journaling (Id="ReportCall") and Chat Journaling (Id="ReportChat") scenarios, you can't use the old [Contact::XXXXXX] variables. You have 2 variables [EntityId] and [EntityType] which you can use to create the call or chat activity associated to the matched contact. These variables will contain the value returned during contact lookup or contact creation.

Just doing these 2 changes should be enough to get the integration working again.

I have tried this.
I set this up in both SQL and custom integration jobs.
I cleared all contacts in 3CX so there would be no residual data
When running the test in the CRM Integration, the output includes the correct EntityId and EntityType
When trying to put those variables during Call Journaling (Id="ReportCall") those spit out blank values

 

[edossantos]

I have tried this.
I set this up in both SQL and custom integration jobs.
I cleared all contacts in 3CX so there would be no residual data
When running the test in the CRM Integration, the output includes the correct EntityId and EntityType
When trying to put those variables during Call Journaling (Id="ReportCall") those spit out blank values

We will need to see the 3cxSystemService.log file in verbose mode to understand what's going on...

 

[LEAD]

@ITB_CH please take a look at this post and let me know if this works for you. Make sure that phone number in CRM is exact match to incoming number, including country code.

https://www.3cx.com/community/threa...itytype-to-sql-during-call-reporting-2.86277/