gabriel Thank you for your response! Just to clarify, I would only present the record ID as a read-only attribute. So the risks related with changing the ID should be avoided.
As to the question of why... I am working on replacing an older, non-supported system. So my first answer is: The old system showed the record ID, and they want to mimic the old system as much as possible. 😀
But more seriously... The information in this system is currently used along with another application in the business process. There have been times that names or other attributes were changed without noting the change, and it was helpful to have the record ID visible as a way to confirm that this was the same record, with a new "name".
I understand the logic behind the decision to not expose it. And it is not something that will keep REI3 from working for us. I can work around it with either a second attribute, or simply relying on a List view which does allow to see the record ID. I'll just have to see what they prefer. I just thought I'd ask because I might be missing something since I'm so new to the system.
Thanks again for the information! I'm learning more each day from the forums here. I really appreciate all you do!