What's new or changed in Dynamics 365 Human Resources (March 24, 2020)
Effective November 2020:
- Common Data Service has been renamed to Microsoft Dataverse. For more information, see Power Automate Blog.
- Some terminology in Microsoft Dataverse has been updated. For example, entity is now table and field is now column. For more information, see Terminology updates.
This topic will be updated soon to reflect the latest terminology.
This article describes features that are either new or changed in Dynamics 365 Human Resources. Changes apply to build number 8.1.3073. The numbers in parentheses in some headings refer to Lifecycle Services (LCS) support numbers for reference.
Human Resources environment limits are now based on updated licensing (394595)
The limit on the number of environments per project in Lifecycle Services (LCS) has changed. The previous limit was two environments. The limit on the number of production and sandbox environments you can create for Human Resources in LCS is now based on updated licensing. You can now create as many environments as needed per LCS project, depending on the number of licenses purchased. The new licensing, updated on February 1, 2020, allows customers to purchase additional environments. For more information about licensing requirements for additional environments, see Dynamics 365 Licensing Guide.
Full page apps (Preview) - This preview feature, which requires you to enable the Saved views feature, allows Power Apps and third-party apps to be added as full-page experiences via the dashboard.
Saved views (Preview) - This preview feature enables saved views, which provide a significant enhancement to the personalization subsystem. This feature allows users to have multiple named sets of personalizations per page. You can also publish views to security roles.
Optimized "is one of" filtering experience - This feature enables an optimized "is one of" filtering experience that makes it easier to enter multiple filter values, has a simpler mechanism to remove individual or all filter values, and has a more compact and intuitive visualization of filter values.
Recommended fields - Users often need to add fields to a grid or page. This can be difficult with so many available fields. Instead of having to search through a large list, this feature enables the system to surface a set of recommended fields based on what other users most often add in similar scenarios.
Sticky default actions in grids - This feature ensures that the default action in a grid is linked to a specific column in a grid, regardless of whether that column is moved or hidden.
Unable to adjust leave balance for a plan with no accruals that was created with "multiple leave type" feature on (419635)
With this change, you can adjust balances for leave plans that have been created with the Multiple leave type (Preview) feature enabled in feature management.
The following preview features became available on February 3, 2020:
Leave and absence preview features - For more information, see Leave and absence preview features.
Benefits management preview feature - For more information, including known issues, see Benefits management overview.
Common Data Service solution is now available with the following changes:
|Job/Position entity changes||
|Job position dimension entity added||
|Worker entity changes||
|Employment entity changes||
|Worker address entity changes||
|New variable compensation setup entities||
|New Worker calendar employment entity||
|New Payroll position detail entity||
|New Title entity||
Financial dimensions for both positions and employment provide one-direction integration for updates from Human Resources to Common Data Service. Financial dimensions updates don't currently synchronize from Common Data Service to Human Resources.
Over the next few weeks, these entity changes will be available in all environments. To manually install the latest Common Data Service solution for Human Resources:
Go to the Power Platform Admin Center.
Find the environment you want to upgrade. The environment should correspond to Environment name in the Common Data Service information section in the About form in Human Resources.
Select the environment to view the environment details.
In the action bar at the top, select Manage Solutions. A new browser window will open and navigate to Dynamics 365 Administration Center in the context of your environment.
In the Solution list, select Dynamics 365 Human Resources Anchor.
Select Upgrade to apply the latest solution.
SharePoint preview doesn't work in some environments
If document preview for documents stored in SharePoint doesn't work, try the following procedure:
Verify the Admin user account has an email associated with the user record. You can view this information in the User page. If email isn't set up, you need to add the email and provider with the OData Excel add-in. By default, the email address isn't present in the Excel design. You'll need to edit the Excel design, add all fields, apply, and refresh. Once you've completed those steps, you can update the admin account.
After the Admin account has an associated email account, sign in to Human Resources with Admin credentials.
Access an attachment in SharePoint to start the document preview.
Sign in with another user account that has access to attachments and verify that the preview works as expected.
New production release cadence
Beginning in April, the release cadence for Human Resources will shift from a weekly update to a bi-weekly update. To ensure alignment with safe deployment practices, and maintain high standards of stability and reliability in the service, the process of deploying service updates to all regions will be a two-week rollout. Additional testing and monitors will be in place to verify successful deployment at each stage of the process. For more information on the release cadence, see Update process.
Employment Detail entity
The Employment Detail entity has been updated with the following fields: PayFrequency, Employment Category ID, Employment Type, EmploymentType ID, and Benefit Employment Status. The setup data for these fields rely on benefits management being enabled in Feature management. These fields shouldn't be populated or updated in the Employment Detail entity, because it will result in errors during import.