> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/dataloader/single-dataloader/extract-salesforce-data-1.md). # Copy of Extracting Salesforce Data #### **Data Extraction Overview** Basic DataLoader offers a convenient feature to extract data from Salesforce by defining filter criteria using queries during job creation. The query specified at this stage determines which records are retrieved when the job is executed. This ensures that only the relevant dataset is fetched based on the configured query conditions, enabling targeted and efficient data extraction. **Step-By-Step Guide:** 1. Open the Basic application by logging in to the application. 2. Expand the "Dataloader" option to click on the "Basic" option. 3. This will open the basic dataloader application.
4. Click on the "Create new job" button to initiate the creation of an "Extract" job. 5. On clicking on the "Extract" job, the flow will navigate to the "Login and select object" step. 6. Select an object from the available list of objects.
7. The workflow opens at the initial step, where the Salesforce connection and object selection context are available. Selecting Next moves the process to the Add Filters step, where the query is configured.

Login and select object step

8. The selected object defines the available field list, filters, order-by options, and base query structure in the Add Filters step.
*Add Filters step with the generated query* 9. **Building the Query from Fields** The Fields panel lists the fields available for the selected object. Selecting fields adds them to the generated query. The query editor updates automatically as selections are made.

Fields panel in the Add Filters step

The Search option narrows the field list and helps locate the required field. The Select all option selects the displayed fields in the list.

Field search and field selection

The Show API Names option displays each field with its API name. This helps confirm the exact field reference used in the generated query.
*API names displayed for selected fields* 10. **Adding and Managing Filter Conditions** The Filters section limits records returned by the query. A condition is configured by selecting the reference object, field, operator, and value. The Add Condition icon adds the condition to the filter grid.

Filter condition configuration

After a condition is added, the filter grid displays the condition details. The generated query updates to include the filter logic.

Filter condition added to the grid

Multiple filters can be added to the grid. Brackets and logical operators support grouped filter conditions when needed.

Multiple filter conditions added

A filter condition can be removed from the grid. Removing a condition updates the query and reflects the remaining filter logic only.

11. **Applying Order By and Record Count** The Order By section controls the sorting of extracted records. Selecting the object, field, and direction adds the order-by clause to the generated query.

Order By configuration

The Record Count field limits the number of records returned by the query. After a count is entered, the query updates with the corresponding limit.

Record Count applied to the query

12. **Including Deleted Records** The Include deleted records option controls whether deleted records are considered during extraction. When enabled, the setting remains part of the query validation context.

Include deleted records option enabled

13. **Validating the Query** Selecting Validate checks whether the generated query is valid. During validation, the screen displays a processing state while the query is evaluated.

Query validation in progress

After successful validation, a confirmation notification appears and indicates that records are available for extraction. The validated query is ready for the next step in the extract process.

Query validation successful

14. **Editing the Query Manually** Selecting Edit query starts manual query editing. Before switching to manual editing, the system displays a confirmation message explaining that query builder options will be disabled and the current query will remain available in the editor.

Edit query action

Selecting Ok confirms manual editing. The current query remains in the editor and can be updated directly. Query builder options are disabled to prevent conflicts between dynamic query generation and manual query changes.

Edit query confirmation message

In manual query mode, the query editor remains active for direct updates. The available actions are Switch to query builder and Validate.

Manual query editing mode

After the manual query is updated, selecting Validate validates the edited query. The query builder options remain disabled during manual query validation.

Manual query validation

15. **Switching Back to Query Builder** Selecting Switch to query builder returns the workflow to field-based query creation. Before switching, the system displays a confirmation message explaining that the existing query will be cleared and query builder options will be enabled.

Switch to query builder confirmation

After the switch is confirmed, the existing query is cleared. Fields, filters, and order-by options are enabled again, and the Add Filters section returns to a blank query-building state.

Query builder options enabled after switching

16. Multiple schedule options are available to schedule the job
17. On completing the scheduling, click "Next" to move to the "Process Details".
18. Select a "Job Group" to assign the job to a group.
19. Click on "Save" to save the extract job created.
20. Clicking "Save" will redirect to the job list screen of the dataloader basic.
21. Click on "Save" to run the job. 22. Clicking save will redirect to the "Run Configuration" screen.
23. Clicking "Run" on the configuration sceen will redirect to the job list screen with the job "in-progress" and the "Abort" options on the job.
24. Click on the Eclipse icon to observe the options 25. Click on the "Edit" option to initiate the edit flow of the job
26. Click the **Schedule** option to view any existing schedule configured during job creation. A new schedule can also be set at this stage, which will apply specifically to the current job.
27. To delete the job, click on the "Delete" option.
28. A confirmation prompt is displayed to ensure the deletion action is intentional and acknowledged, helping prevent accidental removal of the process.
29. Click on the "Clone" option to initiate the clone operation of the job.
30. Once the clone operation is completed, a cloned job can be observed on the job list page.
31. Click on the "Log" option to observe the job details of the job.
32. The success and the failure of the records can be observed under the "Result of Last Run".
33. Click on the "Success" icon to observe the success records
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/dataloader/single-dataloader/extract-salesforce-data-1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.