Revert to the Standard Provider Search Data Processing Engine Definition
Deactivate your custom Data Processing Engine (DPE) definition and begin using the
standard Provider Search DPE definition again to sync data to Care Provider Searchable Field
records.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health Cloud
or Life Sciences Cloud
User Permissions Needed
To administer Health Cloud:
Health Cloud Foundation permission set
To use Data Processing Engine:
Data Pipelines Base User permission
To enable Data Pipelines:
Customize application
Deactivate your custom Provider Search DPE definition and the scheduled flow that runs
it.
From Setup, in the Quick Find box, enter Data Process, and then
select Data Processing Engine. Click your definition, and then click
Deactivate.
From Setup, in the Quick Find box, enter Flows, and then select
Flows. Click your flow, and then click
Deactivate.
From Setup, in the Quick Find box, enter Provider Search, and then
select Provider Search Settings.
Click Custom Data Processing Engine Definition, and then disable DPE
Transaction Observer.
Click Getting Started, and then enable Standard Provider Search Data
Sync.
Click Manual Sync Data.
It takes time to sync the data. For Provider Search, only one data pipeline recipe can run
at a time. Use the Jobs Monitor tab of Data Manager to see the status of your sync. Use the
Usage tab to see the current hours of recipe job run time for the month.
After the data is synchronized, run a provider search and check that everything is working
as expected.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.