Running Consistency Check in Dynamics 365 for Finance and Operations
Posted on: August 27, 2018 | By: Jarrod Kraemer | Microsoft Dynamics AX/365
Authored by: Chris Rusing
If you are a long time AX user, you may be familiar with the consistency check process. This functionality has been available since AX 2009, in AX 2012 and it is still available in Dynamics 365 for Finance and Operations. This tool is used as way for a user to check/fix the system for orphan records. Orphan records are created because data was deleted, but the transaction still exists in a related table. These records can cause performance issues and, in some cases, prevent a user from completing their business processes.
A situation related to the latter came up recently with one of our clients that when a user was trying to pay an AP invoice, they were getting the error message below.
However, when we checked the invoice, it was not marked for settlement by another user. Despite this, the client couldn’t settle the invoice, which was extremely frustrating! Fortunately, there was an easy fix to resolve the issue.
You must go to System administration> Periodic tasks> Database> Consistency check. Please note that you most likely need the System administrator security role to perform this task.
If you want to run a check for all modules, then I would suggest running this as a batch and/or after hours because it will take some time to complete. Alternatively, you can select individual modules that you want to check for consistency issues. However, for our purposes, we know that we want to address the invoice that couldn’t be settled because of the incorrect error. Choose Payments as your Module and choose Fix error so the system can address the issue.
Once this process is complete, the invoice will be available to be marked for settlement. For additional information please feel free to reach out to us at info@loganconsulting.com or (312) 345-8817.
All the best!
Logan Consulting
www.loganconsulting.com