- Joined
- Feb 6, 2018
- Messages
- 11,215
- Reaction score
- 7,047
Hi,
It seems that since v20 U6, the ReportCall in the CRM Integration is NOT triggered if a lookup scenario didn't provide any Outputs data. For example, a template that uses the ReportCall without an EntityId suddenly stops working. Apparently this is a known bug. Here's another thread with the same issue: https://www.3cx.com/community/threads/crm-integration-not-work-after-today-update.134174/
Same thing applies when trying to use the Call Script or CFD to attach the CRM data. Since now it's in the database, we cannot push it manually, and thus the ReportCall doesn't get triggered. More specifics here: https://www.3cx.com/community/threa...data-created-in-cfd-in-crm.132910/post-636997 The DB fields in question are "crm_contact_id" and "contact" (which probably holds the JSON.)
We use this to perform lookups with more than the number, aka the CallerName and CalledNumber (DID). If those could be available in the CRM Lookup scenario as [Name] and [DID], it would fix our problem as we wouldn't need the call script to attach any data, it would be done by the engine itself.
@nikolascx
It seems that since v20 U6, the ReportCall in the CRM Integration is NOT triggered if a lookup scenario didn't provide any Outputs data. For example, a template that uses the ReportCall without an EntityId suddenly stops working. Apparently this is a known bug. Here's another thread with the same issue: https://www.3cx.com/community/threads/crm-integration-not-work-after-today-update.134174/
Same thing applies when trying to use the Call Script or CFD to attach the CRM data. Since now it's in the database, we cannot push it manually, and thus the ReportCall doesn't get triggered. More specifics here: https://www.3cx.com/community/threa...data-created-in-cfd-in-crm.132910/post-636997 The DB fields in question are "crm_contact_id" and "contact" (which probably holds the JSON.)
We use this to perform lookups with more than the number, aka the CallerName and CalledNumber (DID). If those could be available in the CRM Lookup scenario as [Name] and [DID], it would fix our problem as we wouldn't need the call script to attach any data, it would be done by the engine itself.
@nikolascx
Last edited: