Zoho CRM bad request

Status
Not open for further replies.

omadrid

Customer
Joined
Apr 1, 2020
Messages
3
Reaction score
0
When we perform the test, this error appear:
Server returned a non successful status code - HTTPStatusCode=BadRequest - Reason= - Content={"code":"INVALID_QUERY","details":{"reason":"the field is not available for search","api_name":"Home_Phone"},"message":"invalid query formed","status":"error"}

Logs:

Finished Auth
Request text: https://www.zohoapis.com/crm/v2/Contacts/search?criteria=((Phone:equals:551234) or (Mobile:equals:551234) or (Home_Phone:equals:551234) or (Other_Phone:equals:551234) or (Fax:equals:551234))&fields=Account_Name,id,First_Name,Last_Name,Phone,Mobile,Home_Phone,Asst_Phone,Other_Phone,Email,Fax
System.Exception: Server returned a non successful status code - HTTPStatusCode=BadRequest - Reason= - Content={"code":"INVALID_QUERY","details":{"reason":"the field is not available for search","api_name":"Home_Phone"},"message":"invalid query formed","status":"error"}

at CrmIntegration.ScenarioProcessorBase.ProcessRequest(ScenarioRequest request, IValueManager customManager, HttpClient client, CancellationToken token)
at CrmIntegration.ScenarioProcessorBase.ProcessScenario(ProtocolScenario scenario, IValueManager customManager, CancellationToken token)
at CrmIntegration.ScenarioProcessorBase.Execute(ProtocolScenario scenario, CancellationToken token)
at CrmIntegration.CrmProcessor.GetContactInfoFromCrm(String contactNumber, Boolean isInboundCall, String destinationEmail, Boolean createIfNotFound, CancellationToken token)


Problems
- The test phone was 555-1234 and the query only have 551234
- The integration is requesting a bad field name.
 
The integration requires that all phone fields are visible in Zoho. Otherwise you would need to edit the template, which is not recommended, because you would end up with a custom template, and lose any update or fix that we release...
 
  • Like
Reactions: Evolute IT
The integration requires that all phone fields are visible in Zoho. Otherwise you would need to edit the template, which is not recommended, because you would end up with a custom template, and lose any update or fix that we release...
Maybe add a note in the docs for Zoho Integration about those fields... I see that question A LOT.
 
  • Like
Reactions: edossantos
The integration requires that all phone fields are visible in Zoho. Otherwise you would need to edit the template, which is not recommended, because you would end up with a custom template, and lose any update or fix that we release...
Hi Edossantos
I enable all phone fields in lead, account and contacts, now there is no errors, but the problem is somehow 3cx is removing digits in the request contains 555-1234 and the result of the request show 551234

1631289935784.png

1631289962048.png
 
Hi Edossantos
I enable all phone fields in lead, account and contacts, now there is no errors, but the problem is somehow 3cx is removing digits in the request contains 555-1234 and the result of the request show 551234

View attachment 24351

View attachment 24352
Go to the 3CX Console > Advanced > Contacts > Options, and select "Exact match" there.
 
Al culminar la integracion 3CX - Zoho CRM, realizo la prueba de test y me aparec el siguiente error. Que hay que hacer?Error.PNG
 
  • Like
Reactions: Evolute IT
Que es campo Home-Phone?
The Contact entity in Zoho has many fields. The "Home_Phone" field is the placeholder to store that value for the contact. In your installation, this field is hidden by Zoho, and you need to enable it, because 3CX needs to query it and see if the contact has the caller's number in the Home_Phone field.
 
  • Like
Reactions: Evolute IT
Status
Not open for further replies.