Affects team adoption of Salesforce apps if data is:
- Inaccurate
- Lack of usability (e.g., unable to select an account or tally revenue due to duplicate accounts) Ultimately this affects the credibility of data and data teams.
- Lead: Represents a prospect or lead.
- Account: Represents an individual account, which is an organization or person involved with your business (such as customers, competitors, and partners).
- Contact: Represents a contact, which is a person associated with an account.
- Product2: Represents a product that your company sells. This object has several fields that are used only for quantity and revenue schedules (for example, annuities). Schedules are available only for orgs that have enabled the products and schedules features. If these features aren’t enabled, the schedule fields don’t appear , and you can’t query, create, or update the fields.
- Custom Object: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_custom_objects_list.htm
- Duplicates in fields used as unique identifier
- Missing Values (Nulls & N/A)
- Incompatible email addresses
- Phone Number/Country Code formatting
- Country not matching the phone country code
- Duplicates that aren't exact (e.g., Account Name)
- United Gas & Oil, UK
- United Gas & Oil, Singapore
- Leads that haven't been closed for an unreasonable amount of time
- Correct Spelling and Punctuation
- Incomplete records
Import Salesforce object definitions from Salesforce Metatada API
Bulk 2.0 API vs salesforce api
- CSV import?
- External Table Import?
- Get the Saleforce CLi
- Follow the instructions to gain access to a Salesforce Instance: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/quickstart_dev_org.htm
- Get authentication token for your user:
sf org display --target-org <username>