BYOD ( Bring Your Own Database in Dynamics 365 Finance & Operations) : Part 3

This is part third of a three-part series, In first part I talked about Data base type and the idea behind BYOD (Bring Your Own Database) , In second part, I will set up BYOD (Bring Your Own Database), and in this part We will check some system logs for error messages as a result of BYOD (Bring Your Own Database) runs.

How-to search system logs for BYOD and other errors in Dynamics 365 Finance & Operations

In this article I will show how to search the Execution log for errors in the running of BYOD jobs. The obvious place to look for error messages is in the Execution log of the BYOD job, but sometimes the message there is not detailed enough to understand what caused your job to fail. For detailed information you need to check system log in Event Viewer in your system.

Let’s begin. We will walk through the steps to search the Execution log for errors in the running of BYOD ( Bring Your Own Database in Dynamics 365 Finance & Operations) jobs:

Here, I have a BYODW job containing some entities, one of which failed due to some run time error. In order to see the error message, Go to System administration >> Data management >> click on “Execution details” in the Job history of your BYODW group and click “View execution log”:

In the execution log, there are some things to look for, the first thing being the error message itself. However, the error message may be too generic or even non-existent after that Staging status, Target status and Log text. first you have to notice that the Staging status is ‘Ended’ meaning that the data is imported in staging table in the BYOD job ran without issue, but the Target status is in ‘Error’. This means that the writing of the data into the destination caused the job to error out. The Log text for the Source (i.e. staging) is displayed and tells us that “'Product attribute values' record(s) inserted in staging”

After selecting the Target, you can see the Log text and got error related details sometimes it is not in details but in my scenario i got some data duplicate error you have to understand Log Text in details:

If it is not in details So, what do we do to resolve the issue? It is apparent that the Job history does not give us enough details and we simply cannot do nothing because the error will occur again in the next run of the BYOD job. For detailed information you need to check system log in Event Viewer in your system. 

When finished, click the X in the top right corner to close this search.

Congratulations, you have searched event logs for BYOD (and other) errors. we created BYOD ( Bring Your Own Database in Dynamics 365 Finance & Operations).