mibuso.com
Home› NAV Three Tier

Change Log Entries on BC19

RodtmcleanRodtmclean Member Posts: 89
in NAV Three Tier
Hi,

Are there any known weaknesses with the change log?

I have a client that has indicated some fields are blank when they have completed them, these fields are set up to record in the change log. When I check the change log entries they fields have not been logged - apart from the correcting entries they keyed in later on.

The only way I can reproduce this is by terminating the web page after typing in the values (they sent a screen shot with the completed values) and then the change log doesn't record and the fields are blank.

I'm putting it down to user error for now, they are reporting it frequently so following uop.

Regards and Thanks
Roddy

Answers

  • Developer101Developer101 Member Posts: 565
    What is the page they getting this issue with?
    Is it random or one specific page?
    Change log only logs change in fields where data is entered and saved. If data is not saved in the fields then it wont record anything.
    United Kingdom
  • vaprogvaprog Member Posts: 1,144
    edited 2024-12-09
    I don't understand what @Developer101 is saying.

    Change log used to be triggered by the OnGlobal<Trigger> events (formerly procedures with pre-defined IDs in Codeunit 1. Those get triggered by user interactions in pages only. Modifications in code had to be logged by calling functions from within that code.

    But after the OnDatabase<Trigger> events were introduced, any database operation which causes any record in the database to be changed triggers the logging.

    Gotchas I am aware of:
    • inserts for records with autoincrement fields do not record the correct value for that field, because the event is called with data from before the database insert operation (Edit: actually, I believe, before the database insert actually occurred. I could not find any way to find the missing value from within OnGlobalInsert (Auto increment fields are typically used as primary key)). I assume the same will be true for Timestamp fields, but I have not checked this out.
    • the first updating database operation on a table triggers the event GetDatabaseTableTriggerSetup. Changes to the Change Log setup after this point will get active only after you start a new session. Changing the fields to be logged is not affected by this restriction.

    I do have no experience with change log for fields defined in table extensions.
  • RodtmcleanRodtmclean Member Posts: 89
    Thankyou all. I think it is a problem with middleware, network or web pages rather than BC
  • Developer101Developer101 Member Posts: 565
    @vaprog apologies if my response wasn't clear. I was simply trying to answer based on my understanding of the question.
    Looks like it bas been sorted thanks for the feedback @Rodtmclean
    United Kingdom
Sign In or Register to comment.