Salesforce - Resolve error "No such column 'X' on entity 'X'.

[Jayaram_Shanaiah]

Issue: 

Endpoint requests using the Salesforce connector fail with: 

No such column 'Billingstreet' on entity 'Account'.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

The column and object in the error message may vary.

Connector: 

Salesforce connector

 

Resolution

The column/field isn’t accessible (this is called ‘Field Level Access’ in SFDC), due to user permissions, or a required Salesforce module isn't enabled.

The List Accounts block in the background just uses a SOQL query which pulls out some basic standard fields from the Account object. In very rare circumstances, access to these fields has been disabled in a specific account (maybe the field is not in use, or the specific user doesn’t have the correct permissions).

If that’s the case, the alternative is to build your own SOQL query using the "custom query" block in Salesforce.

To Resolve the permission issue:

1. Specify a SOQL query to get customized data from the account using the "Custom Query" block.
   
   OR
   
   
2. Verify if all necessary permissions are set: 
   1. Make sure that this field is actually visible to your user via Field Level Security.
      1. Click the field name in your Setup UI to view the field definition detail.
      2. On this detail view, there will be a Set Field-Level Security button.
      3. Make sure Visible is selected for your Profile.
         
         OR 
         
         
   2. To check field-level security, navigate to Customize > Account > Fields then click on Account Number.
      1. Click the button "Set Field-level Security". You'll see all of your profiles listed and which profiles have access to the field.
      2. By default, Account Number is hidden via FLS. You can also check on field accessibility from a profile.
      3. In any profile, type "Account" in the search box and open the Account object.
      4. Review each field to see if the profile has edit and read access.

Related Content 

https://salesforce.stackexchange.com/questions/218950/no-such-column-on-entity-error-for-an-existing...
https://salesforce.stackexchange.com/questions/53558/why-do-i-get-this-error-no-such-column-accountn...