Salesforce Frequently Asked Questions

Frequently Asked Questions

The Data8 Data Validation package is installed from Salesforce AppExchange and its components are built for Lightning Experience. They can be added to Lightning record pages and to Screen Flows.

Go to Setup → Installed Packages and look for Data8 Data Enhancement App. The version number is shown next to it. See our release notes for what changed in each version.

You can create API keys on the Data8 dashboard. In Salesforce, open Data8 Configuration → Settings, click Edit API Keys and enter both keys:

  • Client-Side API Key: used by the on-screen components.
  • Server-Side API Key: used by server-side processes and flows.

A common cause of errors is pasting a key into the wrong box.

Check that the installation has finished (Setup → Installed Packages) and that your user has been assigned the Data8 User permission set. Without the permission set, the Data8 Configuration app and components aren’t visible.

No. Every field you enter in a component’s settings, including Validation Result and Last Validated fields, must already exist on the object. Create the fields first, then add the component and enter their API names. Remember that custom fields end in __c. The User Guide lists the fields for each component.

This is usually because a field doesn’t exist, its API name was entered incorrectly (often missing __c), or the user doesn’t have Read and Edit access to the field. Check the field in Object Manager and the user’s profile or permission sets.

The package includes a Remote Site Setting and a CSP Trusted Site for https://webservices.data-8.co.uk, both named Data8. Make sure both are present and active under Setup → Remote Site Settings and Setup → CSP Trusted Sites.

The service may not be enabled on your Data8 subscription, you may have run out of credits, or the check may be turned off in the component (for example Enable Validation or Enable TPS Screening). A “This service is unavailable” (HTTP 403) message usually means the API key is wrong or the service isn’t on your subscription. Your credit balance for each service is shown on the Settings page.

From version 2.0, Field Validation has been replaced by the separate Data8 Email Validation and Data8 Phone Validation components. The old component is still installed as Data8 Field Validation (Deprecated) so existing pages keep working, but we recommend replacing it with the new components when you can.

Either both UDPRN and UPRN fields are mapped (Data8 returns only one property reference per address, so map one or the other), or an Organisation field is mapped while organisation handling is set to “Ignore it”.

Map the optional Checked Address field on the PredictiveAddress component. It stores a fingerprint of the confirmed address, so the component can detect changes made outside it (for example by a Data Loader import) and reset the validation status.

Block Saving Unvalidated Addresses is turned on in Data8 Configuration → Settings. With this option on, an address must be confirmed by a PredictiveAddress lookup before the record can be saved.

Yes. Email Validation, Phone Validation, PredictiveAddress and Bank Account Validation can all be added to a Screen Flow screen. The components don’t save to the record themselves in a flow, so add an Update Records or Create Records element after the screen. See Using the components in a Screen Flow.

Add the Data8 Business Insights Refresh quick action to the record page or Company page and run it, or tick Refresh Now on the Company record.

Data8
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.