Workflow: Target date not found in work calendar

(0) Share

Report

Posted on by Community Member Microsoft Employee

Hello all,

For one of our entities, the journal workflow is giving this error. Stopped (error): X++ Exception: Target date not found in work calendar
at SysWorkflowDueDateProvider-resolve
SysWorkflowDueDateProvider-resolveDueDate
SysWorkflowQueue-resume

The General journal was created on 12/31/2019 as we upgraded to dynamics 365 from AX 2012 this month, the user is not able to post the journal now as it's giving the above error. I checked the Calendar settings under the organization admin and the 2020 calendar is already setup for the whole 2020 year. The ledger calendar under GL is open for that specific entity right which is 12/31/2019 until now.

Where else I should be looking? Let me know.

Thank you.

All responses (17)

Answers (1)

Verified answer

Community Member Microsoft Employee on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

Hi Ludwig,

My issue was resolved by changing the workflow configuration for that journal until it is posted and then reverting it back. We don't have any working times setup for calendar so that was not an option to reoslve.

Thanks for the help!
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

Hello BRaza,

There have been a number of replies and feedback provided for this thread?

Have you been able to setup your working time templates and created the working times for the calendar(s) used?

Has your issue been resolved then?

Best regards,

Ludwig
Community Member Microsoft Employee on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

Unfortunately the working time template was not steup in AX 2012 and same is the case in D365.

Thanks.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

I changed the configuration under journal workflow to Non-calendar for now. Resumed the workflow and it went through.

Once, this old journal is posted, we will change it back to work calendar due date under workflow configuration.

Thank you for your help!
Suggested answer

TracyXing on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

when you create compose working times, if you don't set working time template, the new created working times will be created as closed. If you setup working time template, it will be created as opening.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

I did not try opening all of them like for the entire calendar, but I did try opening two days on which the journal was submitted into workflow.

No idea why the work calendar is kept to closed.

Thanks!
Suggested answer

SouravDam 11,721 on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

Hello BRaza,

Have you tried by opening these if you are facing same issue or not?

Also, any specific reason to set it as 'Closed' ?

Best regards,
Sourav Dam

Kindly mark this thread 'Yes' if this is answered your query which may help other community members in this forum.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

This is the screenshot for work calendar starting from May 1, 2020.

Thank you!

Razab
Suggested answer

SouravDam 11,721 on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

Hello BRaza,

Yes this could be a reason. Let's set that open and see if now you are able to proceed.

However; appreciate if you can share a screen shot to look into this more precisely before coming to any conclusion.

Best regards,
Sourav Dam

Kindly mark this thread 'Yes' if this is answered your query which may help other community members in this forum.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Workflow: Target date not found in work calendar

Also, I noticed all months under work calendar are set to closed. Do you think, it might be causing the issue?