74
We often create generic functionalities (linking attachments, notes, comments, ...) that use 'RecordID' as a means to link data between master/detail record. On the master record, flowfields are added to show the no. of linked records, ... On the master pages, generic factboxes are added to show the linked records (see #1552). The above is always coded, since there's no native support for the 'RecordID' integration inside the FlowField definition or the SubPageLink property. Adding support for the RECORDID function (or an alternative to it) in various field/page properties would ease the integration of application-wide / generic features.

More info on
https://github.com/Microsoft/AL/issues/1757
https://github.com/Microsoft/AL/issues/1552
Category: Development
STATUS DETAILS
Needs Votes
Ideas 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

Comments

F

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

F

Same issue, do we need more votes to put it on roadmap?
I think this is a very important and obvious idea.

Category: Development