Timestamp field Sync with Posted Primary Key

Business Central/NAV User Forum
1

As per our understanding, Entry No in GL Entry table is sequentially increasing and there will be no update on records after posted. It means timestamp and EntryNo fields should be incremented in ascending order but we have many records which are out of sync between timestamp and Entry No fields.

SELECT

CONVERT(bigint,timestamp) as RecID,* FROM dbo."*******$G_L Entry" WHERE “Entry No_” IN (202,203,204,205)

RecID timestamp Entry No_
2056433 0x00000000001F60F1 202
2056434 0x00000000001F60F2 203
2116148 0x0000000000204A34 204
2056436 0x00000000001F60F4 205

Check above Entry No ‘204’ the RecID(Timestamp) is 2116148 which is greater than 205 ( RecID is 2056436), in this case, we consider this as Delta record which is wrong by entry no. Please guide me on this scenario.

2

As I would think the “Entry No.” in GL Entry should always be correct I would tend to think there is something wrong with the timestamp. An error in the “Entry No.” field would cause a lot of problems within the database.

3

Thanks for the reply Andre.

For my DataMart,I am trying to fetch incremental data using timestamp field from Navision tables.

Due to these data Quality Issues, I could not use this timestamp field for other tables as well ( Sales etc).

Is there any hunch why might be the issue with timestamp field? ( I have access only to backend Navision tables).

Also For Sales tables, Which key should i use to fetch the data incrementally for our ETL Load ( Note: primary key in sales tables are varchar fields) ?

Thanks in advance.