140
F

'RECORDID' integration in field/page properties to ease the build of generic features

Frédéric Vercaemst on 4/29/2019 6:16:51 PM
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

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

Comments

F

F

RE: 'RECORDID' integration in field/page properties to ease the build of generic features

Aidan Harper on 4/10/2025 10:07:35 AM

This change would be especially useful when considering the standard Error Message table, which has a Context Record ID field.Consider the following use-case for a FlowField:CalcFormula = count("Error Message" where(Context = const(true), "Context Record ID" = Rec.RecordId()));Obviously this is pseudo and wouldn't compile, but the Context Record ID is a standard field (ID 10) on the standard table Error Message (ID 700), so improved support for the built in error handling system would be an immediate benefit of introducing Record ID as valid content for FlowFields.

Category: Development

F

F

RE: 'RECORDID' integration in field/page properties to ease the build of generic features

Damjan Zakojc on 12/17/2024 7:16:49 PM

Hi, this is critical issue and needs to be supported ASAP.Customers are complaining that they cannot use simple solutions as they worked in the "old" NAV.I have some customers who do not wish to go to the cloud, due to several limitations and are rether staying on BC onPrem.Please hear us out.Thanks Damjan

Category: Development

F

F

RE: 'RECORDID' integration in field/page properties to ease the build of generic features

Thomas Brodkorb on 10/24/2022 10:34:27 AM

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

F

F

RE: 'RECORDID' integration in field/page properties to ease the build of generic features

D B on 8/6/2021 11:37:23 AM

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

F

RE: 'RECORDID' integration in field/page properties to ease the build of generic features

Volodymyr Dvernytskyi on 1/27/2021 4:03:49 PM

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

Category: Development