You are here:
Work.com vs. HR Service Data Model
Review the differences between the Work.com and HR Service data models.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Review the differences between the Work.com and HR Service data models.
| View supported editions. |
The Employee object is at the heart of the Work.com data model. Most functionalities are built around the Employee object. See Understand the Work.com Data Model.
However, the HR Service data model uses a combination of the Person Account and Employee objects. The developer name of the Employee object in HR Service is Employee2. In the new data model, Person Account is the primary object for storing an employee’s data. All functionalities rely on the Person Account object. See HR Service Data Model.

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.