web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Unable to future enroll an employee in the leave plan of the same type

(0) ShareShare
ReportReport
Posted on by
I have the same error as in here:

Unable to future enroll an employee in the leave plan of the same type

When trying to future enrol an employee to a new type of annual leave ( due to changing work pattern from 1.04) 

All plans expired with 31.03:



When trying to enroll to new one from 1.04 below error message:




When doing exactly the same exercise but with dates in past ( expired on 28.02 and enrolled in a new one on 1.03 ) - it all works.

Anyone can help, please? 
I have the same question (0)
  • Suggested answer
    Assisted by AI
    ANInnoSolutions Profile Picture
    446 on at
    Hi MK-05031143-0,
     
    1) Issue
    - Unable to future enroll an employee into a new leave plan of the same leave type in D365 Human Resources
    - Error message states that a worker can only be enrolled in one plan of leave type "Annual Leave"
    - Existing plan is already set with an end date (31.03.2026)
    - New enrollment is being created starting 01.04.2026
    - The same process works correctly when using past dates but fails for future-dated changes
     
    2) Reason
    - The issue is caused by how D365 Human Resources validates leave plan overlaps based on system date and active enrollments
    - The validation logic checks current and future enrollments and does not allow overlapping plans of the same leave type even if end and start dates are consecutive
    - The system still considers the existing plan as active until the end date is reached in real time (today’s date perspective), not only based on effective dates
    - This leads to a conflict when attempting future enrollment because the existing plan has not yet expired in system context
     
    In your screenshots:
    - Existing plan ends on 31.03.2026 and is still considered active today
    - New plan starts on 01.04.2026 (future)
    - The system blocks this because it evaluates overlap in the future timeline
    - It works in the past scenario because the system treats past enrollments as closed and no longer active
    - This can happen due to strict enforcement of one active plan per leave type across the entire timeline (current + future), not just overlap at a specific date
     
    3) Resolution
    - Ensure no overlap exists across the entire timeline for the same leave type
     
    Option 1 (Recommended standard approach)
    - Update the existing enrollment first:
    - Set End date = 31.03.2026 (already done)
    - Save and confirm it is fully committed
    - Then create the new enrollment starting 01.04.2026
    - If still blocked Temporarily set End date to one day earlier (30.03.2026) and create the new plan then adjust dates back if needed
     
    Option 2
    - Use "Maintain employee eligibility" or mass update processes
    - These processes handle timeline transitions better than manual enrollment forms
     
    Option 3
    - Temporarily unenroll or remove the existing plan
    - Add the new plan with correct future dates
    - Reinsert the original plan with correct historic dates if needed
     
    Option 4 (Configuration check)
    - Review Leave plan type configuration: Ensure no strict overlap rules or validations are enforced via parameters and check if multiple enrollments are restricted strictly per leave type
     
    Option 5 (Data validation)
    - Check for hidden overlapping records: Look for other enrollments (even future drafts or expired records) and verify no duplicate Annual Leave enrollment exists without end date
     
    Technical explanation
    - The system enforces: Only one enrollment per leave type at any time across timeline and Future-dated validation considers both current and future records such as Validation is stricter than simple date boundary logic
     
    Best practice
    - Always perform leave plan transitions using: Exact end date = old plan + Start date = next day and Ensure changes are committed sequentially and validated before creating new records
     
    Key takeaway
    - This is standard system behavior in D365 HR
    - The system blocks future enrollments when it detects another active or future plan of the same type
    - The workaround is to ensure a clear, non-overlapping timeline that the system can validate without ambiguity
     
    For a more detailed answer, please provide more information.
     

    Rg,

    Alexander

    *Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

    *The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

    References:

    1. Microsoft Licensing Guide
    2. Microsoft Doc`s/Learn

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 622

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 553 Super User 2026 Season 1

#3
CP04-islander Profile Picture

CP04-islander 430

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans