---
schema_version: "1"
id: 5ae13c0fc4855beca67afea2cbba38135cf51e03ffb09cf29d1399c9e6a3ab3a
title: Address Common Data Issues
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_edd_prep_data_issues.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_edd_prep_data_issues.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c6c4c5d05f44d1bb7755c0e0f72a772a9a40e7ea8c27be36a0298d31c756b776
description: Handle common issues that you encounter during data prep for Einstein Discovery.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Address Common Data Issues

Handle common issues that you encounter during data prep for Einstein Discovery.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png)

Note Einstein Discovery stories are now models. We wish we could snap our fingers to update the name everywhere, but you can expect to see the previous name in a few places until we replace it.

The following table describes some approaches for handling common data issues when preparing data for analysis.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png)

Note Einstein Discovery detects some of these issues for you during analysis. If found, Einstein prompts you to fix an issue in the model so that fixing it in the dataset is not required. For more information, see [Handle Quality Alerts](https://help.salesforce.com/s/articleView?id=analytics.bi_edd_quality_alert.htm&release=264.0.0&type=5 "Einstein Discovery displays quality alerts when it detects issues in your training data, your model’s quality metrics, or during cross-validation.").

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:16.10305958132045%">
          <col style="width:67.7938808373591%">
          <col style="width:16.10305958132045%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d125255e54">Issue</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d125255e57">Approach</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d125255e60">See Also</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">Extreme Values and Outliers</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">Einstein Discovery algorithms are sensitive to
              outliers because those values affect averages
              (means) and standard deviations in statistical
              significance calculations. If you find unusual
              values or outliers, confirm whether these data
              points are relevant and real. Often unusual values
              are errors. If the extreme data points are accurate,
              predictable, and reoccurring, do not remove them
              unless those points are unimportant. You can reduce
              outlier influence by using transformations or
              converting the numeric variable to a categorical
              value with binning.</td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">
              <ul>
                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_edd_data_alert_outliers.htm&amp;release=264.0.0&amp;type=5" title="Indicates the presence of uncommonly large or small numbers, potentially from data entry errors or rare events. Outliers influence averages, which can affect the accuracy of insights, predictions, and improvements.">Outliers Alert</a>
                </li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">Missing Values</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">
              <p>The most common repair for missing values is
                imputing a likely or expected value using a mean or
                computed value from a distribution. If you use a
                mean value, you could reduce your standard
                deviation. Thus, the distribution imputation
                approach is more reliable. Another approach is to
                remove records with missing values. Don’t get too
                ambitious with filtering out missing values.
                Sometimes the pattern is in the missing data. Also,
                if you delete too many records, you undermine the
                real-world aspects in your analysis.</p>
              <p style="margin-bottom:0;">Einstein
                Discovery orients its analysis around a particular
                outcome. If the value of the targeted outcome is
                missing from a particular row, then Einstein
                Discovery excludes that row from
                analysis.</p>
            </td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">
              <ul>
                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_edd_data_alert_values_missing.htm&amp;release=264.0.0&amp;type=5" title="Indicates that a variable is missing a high percentage of values, which can lower the quality of your insights or model.">Missing Values Alert</a>
                </li>

                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_missing_value_handling.htm&amp;release=264.0.0&amp;type=5" title="Gaps in your data can throw off analysis. Missing values are best fixed in the source application by, for example, making it a required field. However, if you can’t do that, you can use CRM Analytics to fill in missing data.">Handle Missing Values</a>
                </li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">Incorrect Values</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">Predictive algorithms assume that the input
              information is correct. If only a few rows have
              incorrect values, decide what to do. Remove those
              rows from the analysis, or replace the incorrect
              values with more correct or average values. If there
              are numerous inaccurate values, determine why the
              inaccuracies happened and whether it’s possible to
              repair them. Sometimes it’s better to remove a
              highly error-prone variable than include it in the
              analysis.</td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">Standardize Categorical Values</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">For category values, ensure consistent category
              names. Remove spelling variations (such as plurals
              or abbreviations). Fix typos and other errors. Use
              labels that are meaningful, recognizable, and easy
              to interpret.</td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">
              <ul>
                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_edd_story_fuzzy_matching.htm&amp;release=264.0.0&amp;type=5" title="Fuzzy matching adds uniformity to spelling variations in variables, resulting in smarter categorizations and better predictions. Einstein Discovery transforms the data at prediction time, enabling you to skip cleansing during data prep.">Apply Fuzzy Matching for Smarter Categorizations</a>
                </li>

                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_text_column_handling.htm&amp;release=264.0.0&amp;type=5" title="Confirm that text values in a column are uniform in formatting, spelling, and language. Inconsistencies can occur within data sources and after merging data from multiple data sources.">Handle Text Values</a>
                </li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">Skewed Data</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">For continuous variables, review the distributions,
              central tendency, and spread of the variable. These
              variables are measured using various statistical
              visualization methods. Confirm that continuous
              variables are normally distributed. If not, try to
              reduce skewness for optimal prediction. For
              categorical variables, use a frequency table, along
              with a bar chart, to understand distributions of
              each category. If variable values are skewed,
              Einstein Discovery could produce biased models. When
              a skewed distribution must be corrected, transform
              the variable using a function, such as the Box-Cox
              transformation. After applying the fix, a normal
              distribution for the variable is achieved. The newly
              prepared, transformed variable performs much better
              for predictive modeling purposes.</td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">High-Cardinality Fields</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">High-cardinality fields are categorical attributes
              that contain many distinct values. Examples include
              names, ZIP codes, or account numbers. Although these
              variables can be highly informative,
              high-cardinality attributes are rarely used in
              predictive modeling. Including these attributes
              vastly increases the dimensionality of the dataset,
              which can make it difficult for most algorithms to
              build accurate prediction models.</td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">
              <ul>
                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_edd_data_alert_cardinality.htm&amp;release=264.0.0&amp;type=5" title="Indicates that a variable contains more than 100 unique values.">High Cardinality Alert</a>
                </li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">Binary Outcomes and Boolean Variables</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">If a variable has a binary outcome (only two
              possible values), and those values are represented
              by numbers (for example, 1 and 0), then convert
              those numeric values to text values (for example,
              "TRUE" and "FALSE" or "NOTCHURNED" and "CHURNED").
              For solutions that implement the classification use
              case (binary outcomes), Einstein Discovery requires
              the outcome values to be represented as text values.
              For other variables in the dataset, converting these
              values to text can improve the interpretability of
              the charts and explanations in the resulting
              insights.</td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">Ordinal Variables</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">Ordinal variables are problematic for predictive
              models. Ordinal data consists of numerical scores on
              an arbitrary scale that is designed to show ranking
              in a set of data points. For example, Low, Medium,
              and High are ordinal. Predictive algorithms assume
              that the variable is an interval or ratio variable
              and therefore be misled or confused by the scale.
              Ordinal variables are treated as categorical. If you
              have ordinal values, transform them into continuous
              or categorical values.</td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Issue" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e54 ">Duplicate, Redundant, or Highly Correlated
              Variables</td>

            <td data-label="Approach" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e57 ">Minimize duplicate, redundant, or other highly
              correlated variables that carry the same
              information. Einstein Discovery algorithms perform
              better without these kinds of collinear variables.
              Collinearity occurs when two or more predictor
              variables are highly correlated. As a result, one
              can be linearly predicted from the others with a
              substantial degree of accuracy. To avoid
              collinearity, do not include multiple variables that
              are highly correlated or data that is from the same
              reporting hierarchy. For example, customers who live
              in the city of Tampa also live in the state of
              Florida. To identify high correlation between two
              continuous variables, review scatter plots. The
              pattern of a scatter plot indicates the relationship
              between variables. The relationship can be linear or
              nonlinear. To find the strength of the relationship,
              compute correlation. Correlation varies between –1
              and +1.</td>

            <td data-label="See Also" class="slds-cell-wrap" style="vertical-align:top;" headers="d125255e60 ">
              <ul>
                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_edd_data_alert_collinearity.htm&amp;release=264.0.0&amp;type=5" title="Indicates that two or more variables are highly correlated (for example, City and Postal Code). These variables can have a duplicate impact on the outcome. This condition is also known as multicollinearity.">Multicollinearity Alert</a>
                </li>

                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_edd_data_alert_values_dominant.htm&amp;release=264.0.0&amp;type=5" title="Indicates that most values in a variable are in the same category, which can limit its contribution to the analysis.">Dominant Values Alert</a>
                </li>

                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=analytics.bi_edd_data_alert_values_identical.htm&amp;release=264.0.0&amp;type=5" title="Indicates that all values in a variable are identical.">Identical Values Alert</a>
                </li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

#### See Also

- [Collect, Cleanse, and Optimize Your Data](https://help.salesforce.com/s/articleView?id=analytics.bi_edd_prep_cleanse.htm&release=264.0.0&type=5 "All data prep efforts are oriented toward providing the best data you can for the business outcome you want to examine or predict. CRM Analytics provides the tools you need to consolidate, clean, and prepare your data for analysis. This topic describes approaches to consider when preparing data for your solution.")
- [Handle Quality Alerts](https://help.salesforce.com/s/articleView?id=analytics.bi_edd_quality_alert.htm&release=264.0.0&type=5 "Einstein Discovery displays quality alerts when it detects issues in your training data, your model’s quality metrics, or during cross-validation.")