Sync an entity between Human Resources and Common Data Service
- Changes from Common Data Service take too long to appear in Human Resources.
- You must refresh the tracking table after clearing the tracking.
Enable the integration
- On the System administration page, select Integration configuration .
- Enter the secure File Transfer Protocol (FTP) endpoint and the secure FTP folder path.
- Enter the user name and password of the user who will access the secure FTP endpoint and folder path.
- Test the connection, as required, and set the Enable payroll integration option to Yes .
Configure your data
- Plan (required)
- Type (required)
- Payroll impact (required)
- Recover arrears
- Deduction method
- Deduction priority
- Limit period
- Limit amount
Configure your data to generate payroll in United States and Canada
- Departments are required on positions.
- Cost centers must be set as financial dimensions and must be the first element in the default financial dimension string.
Configure your data to generate payroll in Mexico
- Departments are required on positions.
- Cost centers must be set as financial dimensions and must be the first element in the Default Financial Dimension string.
System requirements for Human Resources
- Dynamics 365 Human Resources on Common Data Service
- Dynamics 365 Finance version 7.2 and later
Enable or disable preview features
- In Human Resources, select System administration .
- Select the Feature management tile.
- To enable a preview feature, select it from the list, and then select Enable . To disable a preview feature, select it from the list, and then select Disable .
Enable or disable Benefits management
- Benefits
- Benefit elements
- Contribution calculation rates
- Benefit enrollment results
- Benefit expiration and extension results
- Benefit eligibility policy rule types
- Benefit eligibility policies
- Eligibility events
Effects of copying a Human Resources database
- The copy process erases the existing database in the target environment. After the copy process is completed, you can't recover the existing database.
- The target environment will be unavailable until the copy process is completed.
- Documents in Microsoft Azure Blob storage aren't copied from one environment to another. Therefore, any documents and templates that are attached won't be copied and will remain in the source environment.
- All users except the Admin user and other internal service user accounts will be unavailable. Therefore, the Admin user can delete or obfuscate data before other users are allowed back into the system.
- The Admin user must make required configuration changes, such as reconnecting integration endpoints to specific services or URLs.
Data elements and statuses
- Email addresses in the LogisticsElectronicAddress table
- The batch job history in the BatchJobHistory , BatchHistory , and BatchConstraintHistory tables
- The Simple Mail Transfer Protocol (SMTP) password in the SysEmailSMTPPassword table
- The SMTP Relay server in the SysEmailParameters table
- Print Management settings in the PrintMgmtSettings and PrintMgmtDocInstance tables
- Environment-specific records in the SysServerConfig , SysServerSessions , SysCorpNetPrinters , SysClientSessions , BatchServerConfig , and BatchServerGroup tables
- Document attachments in the DocuValue table. These attachments include any Microsoft Office templates that were overwritten in the source environment
- The connection string in the PersonnelIntegrationConfiguration table