Salesforce Error

[contoured]

I followed the 3CX Salesforce integration guide and am trying to run the test but get the following error. It seems that authentication is working as it should but something about the request is off. Any suggestions would be appreciated. 3CX v15.5 and Salesforce Classic Enterprise.

Server returned a non successful status code - HTTPStatusCode=BadRequest - Reason=Bad Request - Content=[{"message":"\nAccountId),Lead(Id,FirstName,LastName,Fax,MobilePhone,Phone,Email,Company)\n ^\nERROR at Row:1:Column:174\nNo such column 'Fax' on entity 'Lead'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.","errorCode":"INVALID_FIELD"}]

 

[contoured]

Is Salesforce Classic still supported with 3CX?

 

[francoismartinez]

Hello it may be a salesforce FLS issue : Please check to see if the user configured in 3cx app has access to the field FAX in object Field : check the profile to see the FLS setting for this object field or add a permission set

 

[edossantos]

Server returned a non successful status code - HTTPStatusCode=BadRequest - Reason=Bad Request - Content=[{"message":"\nAccountId),Lead(Id,FirstName,LastName,Fax,MobilePhone,Phone,Email,Company)\n ^\nERROR at Row:1:Column:174\nNo such column 'Fax' on entity 'Lead'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.","errorCode":"INVALID_FIELD"}]

The query is failing because the standard field Fax on entity Lead is missing. You just need to edit the Salesforce configuration to make this field visible to the query, not necessarily visible in the layout. This way the query will succeed.

In order to do this change:

• Go to “Setup Home > Objects and Fields > Object Manager > Lead > Fields.”
• Click on the field that you want to make visible, for example “Fax”.
• Press the “View Field Accessibility” button on the upper right side of the screen.
• Click on the “Hidden” label on the right of “Standard User”.
• Under the “Field-Level Security” check the “Visible” option.

After you do this, repeat the test and check if it succeeds or if Salesforce complains about a different field. Salesforce might complain for a new field after you fix this.

Is Salesforce Classic still supported with 3CX?

Yes, classic and Lightning interfaces are supported, the layout is irrelevant as our integration works with the web service.

 

[contoured]

The query is failing because the standard field Fax on entity Lead is missing. You just need to edit the Salesforce configuration to make this field visible to the query, not necessarily visible in the layout. This way the query will succeed.

In order to do this change:

• Go to “Setup Home > Objects and Fields > Object Manager > Lead > Fields.”
• Click on the field that you want to make visible, for example “Fax”.
• Press the “View Field Accessibility” button on the upper right side of the screen.
• Click on the “Hidden” label on the right of “Standard User”.
• Under the “Field-Level Security” check the “Visible” option.

After you do this, repeat the test and check if it succeeds or if Salesforce complains about a different field. Salesforce might complain for a new field after you fix this.


Yes, classic and Lightning interfaces are supported, the layout is irrelevant as our integration works with the web service.

Thank you this worked.