A user with minimal privileges forgets to enter customer payments for the previous 15 days.
The user needs to enter all the payments using a previous date instead of the current date.
What should the user do?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
References: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/organization-administration/tasks/change-date-session.
Option A: Change the date of the user session in the session date form. This option is a valid solution for the scenario described in the question. By changing the date of the user session in the session date form, the user can enter customer payments using a previous date instead of the current date. The session date form allows users to specify a different date for their transactions, and it is commonly used in Dynamics 365 to handle backdated transactions. However, it's worth noting that this solution is only applicable to the current user session and does not change the actual transaction date in the system.
Option B: Change the system date on the user's operating system and restart the browser. This option is not a recommended solution for the scenario described in the question. Changing the system date on the user's operating system can cause synchronization issues and affect the system's functionality. Moreover, restarting the browser will not reset the Dynamics 365 session, and the user will still be working with the current date.
Option C: Change the date of the customer payment journal header. This option is a valid solution, but it's not the most appropriate for the scenario described in the question. Changing the date of the customer payment journal header will allow the user to enter customer payments with a previous date, but it's only applicable to the specific journal. If the user needs to enter payments in other journals, they would need to repeat the process for each one. Furthermore, this option does not address the issue of the user's minimal privileges.
Option D: Change the system date of the Application Object Server (AOS) in system administration. This option is not a recommended solution for the scenario described in the question. Changing the system date of the AOS can cause synchronization issues and affect the system's functionality. Moreover, it would affect all users and transactions, not just the ones for the specific user who forgot to enter customer payments.
In summary, the best option for the scenario described in the question is Option A: Change the date of the user session in the session date form. This solution is a standard approach for handling backdated transactions in Dynamics 365 and ensures that the user can enter customer payments with a previous date without affecting the system's functionality.