More info on
https://github.com/Microsoft/AL/issues/1757
https://github.com/Microsoft/AL/issues/1552
Comments
SystemId is not the same.
Records can be deleted and recreated with the same primary key but different SystemId - or renamed from another record which keeps it SystemId.
What worries me more is that it would be required that the RecordIds are taken into account when renaming records and update all record ids pointing to the old record automatically.
Category: Development
This would be nice. I'd note it's theoretically less important now that all tables have `SystemId` identifying each record/row, so that can be used in links. True, one then still has to hard-code the table number to filter in the target as a `const`, wihch is error-prone due to not showing the table name and susceptible to copy-paste-os.... and, of course, the target table might only have a RecordId of the related record, and adding/using TableNo and SystemId instead may be a lot of work or even breaking. So allowing to use current RecordId would be a welcome alternative
Category: Development
Same issue, do we need more votes to put it on roadmap?
I think this is a very important and obvious idea.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.
Best regards,
Business Central Team