3CX Call Lookups are Failing

Jeff Dodge

SOHO User
Advanced Certified
Joined
Oct 3, 2018
Messages
25
Reaction score
7
We have been using 3CX with Zoho for quite awhile and all of a sudden our call lookups are now failing with this error:

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":"Fax"},"message":"Invalid query formed","status":"error"}

Why would this all of a sudden start happening? We are using the default Zoho Template with no modifications.

Thanks!
 
In some Zoho installations where customers have hidden phone fields, Zoho returns the following error when we try to perform the lookup:

SServer returned a non successful status code - HTTPStatusCode=BadRequest - Reason= - Content={"code":"INVALID_QUERY","details":{"reason":"the field is not available for search","api_name":"Fax"},"message":"Invalid query formed","status":"error"}

The error in the log above is related to the field FAX on entity Accounts. However, this error might also happen for other fields or entities. To resolve this issue, please follow the steps below:


By default, all the standard fields are displayed in each module's page layout. However, to show or hide fields, you can follow the steps given below:

To show fields

• Log in to Zoho CRM with Administrator privileges.
• Click Setup > Customization > Modules and Fields.
• Select a specific module and click Layout.
• In the Layout page, drag and drop the Field label from the New Fields List.
• Click Save Layout.
 
I checked on the field status and they are all visible, so I am not sure why this is still happening. Any ideas?
 
I checked on the field status and they are all visible, so I am not sure why this is still happening. Any ideas?
Post the updated error message, maybe there is something else now.
 
ystem.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":"Fax"},"message":"Invalid query formed","status":"error"}

at Integration.Crm.Engine.ScenarioProcessorBase.ProcessRequest(Boolean authScenario, ScenarioRequest request, IValueManager customManager, HttpClient client, Boolean retry, CancellationToken token)
at Integration.Crm.Engine.ScenarioProcessorBase.ProcessScenario(ProtocolScenario scenario, IValueManager customManager, SqlQueryParameter[] sqlQueryParameter, CancellationToken token)
at Integration.Crm.Engine.ScenarioProcessorBase.Execute(ProtocolScenario scenario, SqlQueryParameter[] sqlQueryParameter, CancellationToken token)
at Integration.Crm.Engine.CrmProcessor.GetContactInfoFromCrm(List`1 result, IEnumerable`1 scenariosToProcess, IValueManager customManager, SqlQueryParameter[] sqlQueryParameters, Func`2 filterResultsFunctor, Boolean exactMatch, CancellationToken token)
at Integration.Crm.Engine.CrmProcessor.GetContactInfo(String contactNumber, InteractionTypes interactionType, CancellationToken token)
 

Members Online Now

No members online now.

Forum statistics

Threads
111,832
Messages
589,285
Members
164,662
Latest member
DejanMDS