Symptom
It shows "Automatic new Contact" on Yeastar PBX and Salesforce despite the contact already exists in the Salesforce when you make an incoming call. Or pop-up feature doesn't work despite the contact already exists in the Salesforce.
In PBX System Log (thirdapp.log), we can see errors the log as below. Such as:
- No such column 'HomePhone' on entity 'Contact'.
- No such column 'Fax' on entity 'Account'
- No such column 'HomePhone' on entity 'Contact'
[Information 2022-12-08 10:51:28.408 3332335 231]salesforceclient.cpp:620 salesforce http responese result: 1 request_type: 10 response: [ {
"message" : "\nLastName,AccountId,Email,Phone,HomePhone,OtherPhone,MobilePhone\n ^\nERROR at Row:1:Column:60\nNo such column 'HomePhone' 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"
} ]
Reason
This is due to the filed invisibility for the "Account" and "Contact" Profiles on Salesforce.
Generally speaking, all the fields in the "Account" and "Contact" Profiles are visible by default.
If you have set the fields to invisible (probably it's set by the initial settings), you will meet this problem.
Solution
Set following fields to visible for "Account" and "Contact" Profiles on Salesforce:
- Name
- Account Name
- Phone
- Home Phone
- Mobile Phone
- Other Phone
- Assistant Phone
- Fax
- Mailing Address
- Description
Here is Salesforce official guide about this setting.
For example, for Home phone field.
Go to the menu path:
Find Object Manager> Contact> Fields&Relationships> Home Phone> Set Field-Level Security> Enable Visible
Click "Set Field-Level Security"
Tick the "Visible" option.
1 Comments