Apex Bulk
The Bulk test step is designed for loading or deleting large data sets via the Salesforce Bulk API. You can modify many records asynchronously by submitting batches from an Excel sheet. Salesforce will process these batches in the background until they are all complete.
Locate this test step in the Test Palette and click and drag it into the test case.
Then complete the following steps:
- Add a Parameter Value Source to read the Excel/CSV file and specify the variable to store the data, e.g., ExcelData.
- In the Object section, specify the target object in the Object field (e.g., Account).
- Select the Operation: Insert, Update, Delete, Upsert, or Hard Delete. (Note: To perform a Hard Delete operation, the Salesforce Connection user must have the Bulk API Hard Delete permission enabled.)
- Specify an Assignment Rule (if the ownership of the records should be defined using existing Salesforce Assignment Rules).
- In the Data section, enter the variable in which the Excel data is stored (e.g., ExcelData).
- In the Result section, specify the Result Name and Result Scope. (Refer to Common Test Step Parameters for more information on Scope.)
Notes on data
When preparing your Excel file, please consider the following:
- Column-field matching: The Column headers in the Excel/CSV file must match the Field Name (i.e., API Name) of the relevant field in Salesforce.
- Required fields: When inserting data into an object, all required fields must be populated. For example, to insert Account records, the Name must be a column header in the Excel file and populated for all rows.
- Salesforce IDs: To operate on existing records, the unique Salesforce ID of the record must be specified. This applies to Update, Upsert, Delete, or Hard Delete operations.
Documentation library
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Functions
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Override auto-retry for Test Step
- Managing test steps
- Namespace org testing
- NitroX
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI license Check
- Reload Org Cache
- Reporting
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript locator support
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- ProvarX™
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines Using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team Foundation Server
- Version control
- Provar Automation trial guide and extensions
- Salesforce Testing
- Provar Manager
- Best Practices
- Troubleshooting
- Release Notes