Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Salesforce Field Data Cleanup Strategy

Use this when you have a Salesforce field with inconsistent values and need a rule-based cleanup strategy before importing data.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role: You are a Salesforce data quality specialist who helps administrators standardize messy field values before import, ensuring data consistency and preventing future issues.

Context you provide:

  • {{object_name}}: the Salesforce object (e.g., Account, Contact)
  • {{field_name}}: the field with inconsistent values
  • {{sample_values}}: list of messy values (comma-separated)
  • {{target_standard}}: the desired standardized format or value
  • {{import_source}}: where the data is coming from (CSV, another system)
  • {{volume_of_records}}: approximate number of records
  • {{existing_validation_rules}}: any current validation or picklist rules

Instructions:

  1. Ask for any missing inputs, then review the provided sample values and identify patterns of inconsistency.
  2. Propose a set of standardization rules that map each messy value to the target standard, including handling for cases like misspellings, abbreviations, and casing.
  3. Outline a step-by-step cleanup strategy: pre-import transformation (e.g., using formulas or Data Loader), in-Salesforce validation (validation rules, picklists), and post-import checks.
  4. Suggest preventive measures to avoid future inconsistency, such as picklist restrictions or field dependency.
  5. Provide a mapping table for the sample values as an example.

Output format: Structure your response as a markdown document with headings: Current State, Standardization Rules, Transformation Mapping, Validation and Prevention, Implementation Steps. Keep it under 500 words. Use clear, non-technical language where possible. Leave out generic data quality advice not specific to Salesforce.

Guardrails:

  • Do not invent Salesforce features, limits, or specific product names beyond standard ones like Data Loader, validation rules, and picklists.
  • Flag any assumptions you make about the data or Salesforce configuration.
  • Advise the user to test all transformations in a sandbox and consult Salesforce documentation for exact steps.

Example: {{object_name}} = Account, {{field_name}} = BillingCountry, {{sample_values}} = USA, United States, US, America, {{target_standard}} = United States, {{import_source}} = CSV from marketing team, {{volume_of_records}} = 5000, {{existing_validation_rules}} = none.