You are a Dynamics 365 Finance systems analyst.
A user configures an alert for purchase orders that have a delivery date of two weeks away.
However, batch alerts are not being sent.
You need to troubleshoot why alerts are not processing.
What two actions may be the cause for alerts not being sent? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Click on the arrows to vote for the correct answer
A. B. C. D.CD.
https://community.dynamics.com/ax/b/shafeealabadiaxtutorials/posts/ax-2012-alert-management-part-ii-due-date-alertsSure, I can explain the possible causes of why batch alerts are not being sent in Dynamics 365 Finance.
A. A batch processing window may be set up for that batch job: In Dynamics 365 Finance, batch jobs are scheduled to run within a defined batch processing window. If the batch job for sending alerts is not scheduled to run within the processing window, the alerts will not be sent. You can check the batch processing window for the batch job by going to the Batch processing job page and selecting the relevant batch job. From there, you can check the processing window settings and adjust them if necessary.
D. There may not be a batch server assigned to the batch job: Another possible cause for the alerts not being sent is that the batch job for sending alerts may not have a batch server assigned to it. Batch servers are responsible for running batch jobs, and if a batch job does not have a batch server assigned, it will not run. To check whether the batch job has a batch server assigned to it, go to the Batch processing job page and select the relevant batch job. From there, you can check the batch server settings and assign a batch server if necessary.
B. The date format in the Dynamics 365 tenant does not match the format in the client device: This is not a likely cause for alerts not being sent, as alerts are based on the date format in the Dynamics 365 Finance system, not the client device. The date format in Dynamics 365 Finance is standardized and should not be changed without careful consideration of the implications.
C. The change-based alert has expired: This is also not a likely cause for alerts not being sent, as change-based alerts are based on changes to specific records and do not have an expiration date. However, if the alert was set up as a timed alert rather than a change-based alert, it may have expired. In this case, you can check the alert expiration date and modify it if necessary.
Overall, the most likely causes for the alerts not being sent are A (batch processing window not set up correctly) and D (batch server not assigned to the batch job).