I am trying to build an Authorization object where the primary key should be an unspecified length alphanumeric string (authorization numbers can originate from different sources hence they can come in multiple formats).
In Schema Builder if I go to
Edit Object Properties, the
Record Name can only be
Auto Number type. The latter will always be unique (if one is not messing with the object) but I need the former because a record should be identified or referenced by this unique authorization number. With an
Auto Number, this would create another layer of indirection, such as referencing files in templates by inode number.
This constraint cannot be imposed on it on the object level (as far as I know) so my next thought was to build this into the layout.
If I create a custom text field, disallow duplicates, and copy the authorization number into both fields (into
Name that refers to the primary key
Record Name in the object properties, and into
Authorization Number text field) then it works, and I have a unique reference for each record in the Authorization object.
My question is, is there a way to implement this without copying the same data twice?
Reasons why I need this:
- It is 2016 and this is implemented in any basic RDBMS for decades. This has been an ongoing issue for at least 7 years.
- Most of the users where I work are blind. (Although this solution would raise questions among sighted users.)