Salesforce - CSV Header Validator
Overview
Before you begin, ensure you're equipped with the essentials: ### 1. **Inputs Ready** To use this blueprint, you'll need: - **Salesforce Credentials**: - Access token - Consumer key - Consumer secret - Username - Password - Security token - Domain - **CSV File**: Path to the CSV you want to validate. - **Object Type**: Salesforce object type (e.g., Account, Contact) to validate against. - **Field Names**: List of expected field names. ### 2. **Understanding the Blueprint Flow** - After providing the inputs, the blueprint authenticates with Salesforce. - It fetches properties of the Salesforce object type. - If a CSV is provided, it validates its headers against Salesforce properties. If any mismatches are found, it'll highlight them. - Without a CSV, it displays the Salesforce object type's properties. ### 3. **Salesforce Properties Insight** The blueprint offers insights into Salesforce properties. For each property, you get: - Name - Label - Data type - Attributes: Creatable, Updateable, Nillable, Unique status. ### 4. **Error Handling** The blueprint has built-in error handling. If issues arise (like authentication errors or file not found), it provides clear feedback. ### 5. **Maximizing Blueprint Utility** While its primary function is CSV header validation, it also helps you understand Salesforce properties. This understanding is key to structuring your CSVs effectively for future transfers. In short, this blueprint ensures your CSV data aligns with Salesforce, paving the way for smooth data transfers.
Variables
Name | Reference | Type | Required | Default | Options | Description |
---|---|---|---|---|---|---|
Domain URL | SALESFORCE_DOMAIN | Alphanumeric | ✅ | - | - | The domain used to access your Salesforce instance. |
Access Token | SALESFORCE_ACCESS_TOKEN | Password | ➖ | - | - | Token provided by Salesforce to securely authenticate and access their API. |
Consumer Key | SALESFORCE_CONSUMER_KEY | Alphanumeric | ➖ | - | - | Unique key to identify and authenticate your application's integration. |
Consumer Secret | SALESFORCE_CONSUMER_SECRET | Password | ➖ | - | - | Secret key used in tandem with the consumer key to authenticate your application. |
Username | SALESFORCE_USERNAME | Alphanumeric | ➖ | - | - | Your Salesforce account's username. |
Password | SALESFORCE_PASSWORD | Password | ➖ | - | - | Your Salesforce account's password. |
Security Token | SALESFORCE_SECURITY_TOKEN | Password | ➖ | - | - | Additional security token provided by Salesforce to enhance protection. |
CSV Filename | SALESFORCE_CSV_FILE | Alphanumeric | ➖ | - | - | The name/path of the CSV file you want to validate against Salesforce properties. |
Object Type | SALESFORCE_OBJECT_TYPE | Alphanumeric | ✅ | - | - | The specific Salesforce object type (e.g., Account, Customer) you want to validate against. This name must match Salesforce's API Name from their object manager view. |
YAML
Below is the YAML template
source:
template: Salesforce - CSV Header Validator
inputs:
SALESFORCE_DOMAIN:
SALESFORCE_ACCESS_TOKEN:
SALESFORCE_CONSUMER_KEY:
SALESFORCE_CONSUMER_SECRET:
SALESFORCE_USERNAME:
SALESFORCE_PASSWORD:
SALESFORCE_SECURITY_TOKEN:
SALESFORCE_CSV_FILE:
SALESFORCE_OBJECT_TYPE:
type: TEMPLATE
guardrails:
retry_count: 1
retry_wait: 0h0m0s
runtime_cutoff: 1h0m0s
exclude_exit_code_ranges:
- 102
- 103
- 201
- 202
- 206