Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.withampersand.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Read Action: No such column error

A read fails with an error similar to: 
bad request:
field_one__c,field_two__c,example_field__c,field_three__c,field_four__c
                          ^
ERROR at Row:1:Column:26
No such column 'example_field__c' on entity 'Opportunity'. 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.
Which case is this?
  • Reads work for other customers but fail for this one → almost always a field-level visibility issue. Even System Administrators do not automatically receive visibility for every field.
  • Reads fail for every customer → the field name itself is more likely the problem.

​
Resolve a field-level visibility issue

Share the field visibility instructions in the Salesforce customer guide with your customer. That user must be granted Visible field-level visibility for the field, either through their profile or via a permission set. Ampersand pauses reads automatically after repeated failures to avoid overloading Salesforce APIs, so once the field is visible you’ll need to explicitly resume. Call the Unpause Reads endpoint, or reach out to Ampersand support and we can unpause it for you.

​
Verify the field name

  1. Look up the field in the Salesforce Object Reference. If it’s listed, the field is standard and this is a field-level visibility issue.
  2. If it’s not listed, it’s a custom field. Custom field API names must end with __c — if your read object configuration is missing the suffix, fix it.
  3. If the suffix is already correct, this is a field-level visibility issue.

​
Write Action: No such column error

A write fails with an error similar to: 
{
  "operationId": "00000000-0000-0000-0000-000000000000",
  "errors": [
    {
      "message": "error writing account: bad request: No such column 'Testing__c' on sobject of type Account"
    }
  ]
}
Which case is this? Call Get object metadata via installation for the object you’re writing to.

​
Field doesn’t exist in the customer’s org

Remove the field from your write payload for this customer — for example, by checking object metadata before writing, or by falling back to a default. Longer-term, update your application to handle per-customer schema differences.

​
Connected user lacks field-level visibility

If the field exists in the org but isn’t visible to the connected user’s profile, Salesforce returns the same No such column error. Follow the steps in Resolve a field-level visibility issue.