📄️ Loading Data
Speediful provides data loading capabilties via SOAP, Bulk v1 and Bulk v2 APIs. A unified interface is provided by the procedure SLAMload which requires an @api parameter. Alternatively, users can directly call the various SLAMload. All operations are logged to SLAMActivity_Log
📄️ NULL and Blank Handling
Understanding how Speediful processes NULL values and empty strings is crucial for achieving the desired data outcomes in Salesforce. Speediful aims for compatibility with existing conventions across different Salesforce APIs.
📄️ SLAM_load
This generalized load method provides access to all three APIs and file loading through a single procedure. It delegates to the appropriate specific load procedure based on the @api parameter, making it a convenient choice when the API choice needs to be dynamic.
📄️ SLAM_load_bulk
Performance Tip: By default, Speediful enables parallel data loading with Bulk v1 API. This parallelizes the loading operation on the Salesforce server. It can lead to dramatic time reductions in loading operations vs serial loading. However, judicious use is advised, as this option can potentially be detrimental to overall throughput when loading to objects with lengthy triggered business process flows or to junction objects. To disable parallel loading, set @bulkparallel = 0 or consider using SLAMlockbuster
📄️ SLAM_load_bulkv2
Note: For Bulk v2 operations, the @externalId is mandatory and must be a real Salesforce field. This is essential to correlate the Salesforce result with the original input table.
📄️ SLAM_load_soap
Parameters:
📄️ SLAM_lockbuster
Specialized data loading procedure that eliminates lock issues associated with bulk loading while also optimizing for speed.
📄️ SOAP Headers
SOAP API operations support optional headers that control Salesforce behavior during data operations. Headers are specified using the @soap_options parameter