# Salesforce - Data Export error when selecting all fields

**URL:** <https://connective.celigo.com/t/salesforce-data-export-error-when-selecting-all-fields/280>\
**Category:** Integrator.io\
**Tags:** error-handling, export, salesforce\
**Created:** [November 30, 2023, 9:56pm UTC](https://connective.celigo.com/t/salesforce-data-export-error-when-selecting-all-fields/280 "2023-11-30T21:56:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![daveguderian](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@daveguderian](https://connective.celigo.com/u/daveguderian)\
**Post date:** [November 30, 2023, 9:56pm UTC](https://connective.celigo.com/t/salesforce-data-export-error-when-selecting-all-fields/280/1 "2023-11-30T21:56:35Z")

</div>

I am receiving an error that looks to be related to selecting "all fields" from an object when exporting from Salesforce and using the "Delta" export. Is this not supported, or perhaps do I need to change something in my configuration/flow.

 ![5301043caa20740200000001-26333ae1ab914ce8b3231d47cc362ebf.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/f/fa95ac2e8709da1305690b7a579be210392c91ba.png)

 ![5301043caa20740200000001-02dd84e13105437b8e2d00a06f4bbf21.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/1/10a8592df104650ef434845df062bec6970657c0.png)

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [November 30, 2023, 10:18pm UTC](https://connective.celigo.com/t/salesforce-data-export-error-when-selecting-all-fields/280/2 "2023-11-30T22:18:56Z")

</div>

@daveguderian the fields(all) option in Salesforce is pretty limiting. Even if you had this working, then the limit requirement forces only 200 returned results and there isn't a way to get the next 200 results without having another query. I would suggest generating a query that explicitly has every field in the SOQL query itself to avoid this issue and to be able to pull more than 200 results. Something like below:

```
SELECT ID,ISDELETED,MASTERRECORDID,NAME,TYPE,RECORDTYPEID,PARENTID,BILLINGSTREET,BILLINGCITY,BILLINGSTATE,BILLINGPOSTALCODE,BILLINGCOUNTRY,BILLINGLATITUDE,BILLINGLONGITUDE,BILLINGGEOCODEACCURACY,BILLINGADDRESS,SHIPPINGSTREET,SHIPPINGCITY,SHIPPINGSTATE,SHIPPINGPOSTALCODE,SHIPPINGCOUNTRY,SHIPPINGLATITUDE,SHIPPINGLONGITUDE,SHIPPINGGEOCODEACCURACY,SHIPPINGADDRESS,PHONE,FAX,ACCOUNTNUMBER,WEBSITE,PHOTOURL,SIC,INDUSTRY,ANNUALREVENUE,NUMBEROFEMPLOYEES,OWNERSHIP,TICKERSYMBOL,DESCRIPTION,RATING,SITE,OWNERID,CREATEDDATE,CREATEDBYID,LASTMODIFIEDDATE,LASTMODIFIEDBYID,SYSTEMMODSTAMP,LASTACTIVITYDATE,LASTVIEWEDDATE,LASTREFERENCEDDATE,JIGSAW,JIGSAWCOMPANYID,CLEANSTATUS,ACCOUNTSOURCE,DUNSNUMBER,TRADESTYLE,NAICSCODE,NAICSDESC,YEARSTARTED,SICDESC,DANDBCOMPANYID,CUSTOMERPRIORITY __C,SLA__ C,ACTIVE __C,NUMBEROFLOCATIONS__ C,UPSELLOPPORTUNITY __C,SLASERIALNUMBER__ C,SLAEXPIRATIONDATE __C,CELIGO_SFNSIO__ CHANNEL_TIER __C,CELIGO_SFNSIO__ TEST_MODE_RECORD __C,YTD_SALES__ C,X18_DIGIT_SF_ID __C,SBQQ__ ASSETQUANTITIESCOMBINED __C,SBQQ__ COTERMEDCONTRACTSCOMBINED __C,SBQQ__ COTERMINATIONEVENT __C,SBQQ__ CONTRACTCOTERMINATION __C,CELIGO_SFNSIO__ ACCOUNT_BALANCE __C,CELIGO_SFNSIO__ CREDIT_HOLD __C,CELIGO_SFNSIO__ CREDIT_LIMIT __C,CELIGO_SFNSIO__ DAYS_OVERDUE __C,CELIGO_SFNSIO__ NETSUITE_ID __C,CELIGO_SFNSIO__ NETSUITE_RECORD __C,CELIGO_SFNSIO__ NETSUITE_SYNC_ERROR __C,CELIGO_SFNSIO__ OVERDUE_BALANCE __C,CELIGO_SFNSIO__ SKIP_EXPORT_TO_NETSUITE __C,CELIGO_SFNSIO__ UNBILLED_ORDERS __C,SBQQ__ DEFAULTOPPORTUNITY __C,SBQQ__ IGNOREPARENTCONTRACTEDPRICES __C,SBQQ__ PRESERVEBUNDLE __C,SBQQ__ PRICEHOLDEND __C,SBQQ__ RENEWALMODEL __C,SBQQ__ RENEWALPRICINGMETHOD __C,SBQQ__ TAXEXEMPT __C,PRICE_LEVEL__ C,SHOPIFY_ID __C,HUBSPOT_ID__ C,ACUMATICA_CUSTOMER_ID __C,CELIGO_MSBC__ BUSINESS_CENTRAL_ID __C,ACTIVE_OPPORTUNITIES__ C,ACTIVE_OPPORTUNITY_AMOUNT __C,IS_ADVISOR__ C,CELIGO_MSBC __SKIP_EXPORT_TO_BUSINESS_CENTRAL__ C,SALESFORCE_URL __C,EXTERNAL_SYSTEM_ID__ C,STRIPE_CUSTOMER_LINK __C,REPORTING_LOCATION__ C,BRANCH __C,CELIGO_BYD__ ACCOUNT_ID __C,CELIGO_BYD__ SKIP_EXPORT_TO_SAP_BYD__C FROM ACCOUNT
```

 ![5301043caa20740200000001-54e3db30171d4b0e90cf6a25d5a5cc5d.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/c/c572b7f04baa88157f81f44a7e254384fe4a9eb6.png)

To get the list of fields available, you could download from object manager, build a SOQL query such as the one below, or use [Salesforce api to describe the object](https://docs.celigo.com/hc/en-us/articles/19906581226779-Connect-to-Salesforce-REST-relative-URIs-via-proxy).

```
SELECT EntityDefinition.QualifiedApiName, QualifiedApiName, DataTypeFROM FieldDefinitionWHERE EntityDefinition.QualifiedApiName IN ('Account')
```

 ![5301043caa20740200000001-8f84595b1c504888b1d08075551f7f2a.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/0/05c2cdbe8e0df364a9acfbc5d013247006f9998d.png)

---

<div class="post-metadata">

**Author:** ![daveguderian](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@daveguderian](https://connective.celigo.com/u/daveguderian)\
**Post date:** [December 1, 2023, 5:08pm UTC](https://connective.celigo.com/t/salesforce-data-export-error-when-selecting-all-fields/280/3 "2023-12-01T17:08:04Z")

</div>

Thanks Tyler! I went with exporting the object fields and then putting them in a massive query like you have and it worked perfectly! It would be nice if there wasn't the limitation when selecting all fields, but I realize that is a Salesforce constraint and not Celigo.

Thanks again!