SalesForceV2 Integration

[jonathanarcher]

Followed the steps here https://www.3cx.com/docs/salesforce-crm-integration/ to Integrate our Salesforce. Got the below error:

Server returned a non successful status code - HTTPStatusCode=BadRequest - Reason=Bad Request - Content=[{"message":"\nContact(Id,FirstName,LastName,AssistantPhone,Fax,HomePhone,MobilePhone\n ^\nERROR at Row:1:Column:71\nNo such column 'AssistantPhone' on entity 'Contact'. 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"}]

Found the exact same error on this locked thread here https://www.3cx.com/community/threads/salesforce-integration-testing.65979/

Did the steps offered by edossantos. Still getting the same above error message unfortunately. Anybody know what other steps we need to do? The other guy in that thread said he did some tweaking on the Saleforce side, but we don't know what needs to be done. Relevant link https://xkcd.com/979/

 

[Evolute IT]

Pretty sure the field require has been removed from your Salesforce so you'll need to make a custom version of the XML CRM template to change the lookup fields.

 

[jonathanarcher]

We got with Salesforce support. Instead of pressing "View Field Accessibility", we update the permissions in the "Set Field-Level Security ". Once we did that it starting working. Just an FYI for anybody else that comes across this

 

[TheodorosG_3CX]

Your issue is related with hidden fields in the CRM. The steps you need to follow are:

- Go to “Setup Home > Objects and Fields > Object Manager > Contact > Fields.”
- Click on the field that you want to make visible, for example “AssistantPhone”.
- 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” (or the profile of the user configured for the integration).
- Under the “Field-Level Security” check the “Visible” option.
- Repeat the procedure for other fields or entities causing the same error.

You need also to ensure about the profile, if it is not the Standard User i would suggest to check other profiles as well.