We have observed that the RecIds of GeneralJournalAccountEntry table which is a standard table for posted entries in D365F&O is getting skipped few places which is a strange behaviour and in audit point of view it is a risk. So this should be mitigated to have a sequencial and consecutive recIds for teh posted entries in GeneralJournalAccountEntry table.
Comments
Agree, it should be enhanced.
Category: General
This behavior is strange. For a posted transaction table the rec id are expected to be in sequence unless there is a logical explanation for not to have it. The auditors can take it as data manipulation. We had a long 1 month discussion with Microsoft but the product team is not ready to accept it as a bug and instead asked us to route it via idea. Not sure I would still agree if this is classified as new idea.
Category: General